gitadmin
c92ee69440
- New common/misc/tmux-launch-agent skill with detect-agent script and agents-seed.md (moved from engineering/setup-skills) - implement-issue simplified: delegates agent dispatch to tmux-launch-agent instead of inlining it - setup-skills stripped of Section E (agent CLI config) - New in-progress/agent-handoff skill using tmux-launch-agent - PKM skills simplified: conversation-summary and pkm-curation rewritten with leaner process, crit streamlined - knowledge-gardener removed (moved to common/in-progress/) - All READMEs updated to match
91 lines
3.0 KiB
Markdown
91 lines
3.0 KiB
Markdown
---
|
|
name: crit
|
|
description: brainstorm with AI using the CRIT framework to generate and evaluate ideas.
|
|
disable-model-invocation: true
|
|
---
|
|
|
|
## Purpose
|
|
|
|
This skill implements the CRIT (Context-Request-Ideation-Tone) framework for structured brainstorming and idea evaluation.
|
|
|
|
## Core Workflow
|
|
|
|
### Step 1: Context Analysis
|
|
Before generating ideas, establish the foundation:
|
|
|
|
1. **Identify the Core Domain**
|
|
- What field, industry, or subject area?
|
|
- What are the key constraints (time, resources, technical limitations)?
|
|
- Who is the target audience and their expertise level?
|
|
|
|
2. **Assess Current State**
|
|
- What problems or opportunities exist?
|
|
- What has been tried before (if applicable)?
|
|
- What resources are available?
|
|
|
|
**Completion Criterion**: Domain, constraints, and current state captured in a compact summary (3-5 sentences).
|
|
|
|
### Step 2: Request Clarification
|
|
Structure the brainstorming request:
|
|
|
|
1. **Define the Specific Goal**
|
|
- What concrete outcome do you want?
|
|
- What success criteria will be used?
|
|
- What is the expected timeline?
|
|
|
|
2. **Gather Input Requirements**
|
|
- What information is needed to proceed?
|
|
- What assumptions should be validated?
|
|
- What data or resources are required?
|
|
|
|
**Completion Criterion**: Goal and input requirements captured as 1-3 concrete statements, each with a checkable success criterion.
|
|
|
|
### Step 3: Ideation
|
|
Generate diverse, high-quality ideas:
|
|
|
|
1. **Divergent Thinking Phase**
|
|
- Generate 5-10 initial concepts without judgment
|
|
- Apply different perspectives (technical, business, user experience)
|
|
- Include both obvious and unconventional options
|
|
|
|
2. **Convergent Analysis Phase**
|
|
- Evaluate each idea against success criteria
|
|
- Score ideas on feasibility, impact, and alignment
|
|
- Identify patterns and synergies between ideas
|
|
|
|
**Completion Criterion**: Minimum 5 distinct ideas generated and evaluated with scores.
|
|
|
|
### Step 4: Iterative Refinement
|
|
Improve selected ideas:
|
|
|
|
1. **Select Top Candidates**
|
|
- Choose 2-3 ideas with highest potential
|
|
- Detail implementation approach for each
|
|
- Identify risks and mitigation strategies
|
|
|
|
2. **Develop Action Plans**
|
|
- Break down into concrete steps
|
|
- Assign priorities and dependencies
|
|
- Define success metrics and checkpoints
|
|
|
|
**Completion Criterion**: 2-3 refined ideas with detailed action plans.
|
|
|
|
### Step 5: Tone & Delivery
|
|
Adapt communication to the audience:
|
|
|
|
1. **Choose Appropriate Role**
|
|
- Subject Matter Expert for technical depth
|
|
- Consultant for strategic guidance
|
|
- Teacher for complex concepts
|
|
- Collaborator for co-creation
|
|
- Analyst for multi-perspective evaluation
|
|
|
|
2. **Structure Response**
|
|
- Lead with clear, actionable solutions
|
|
- Organize information logically and concisely
|
|
- Include examples or analogies for clarity
|
|
- Suggest next steps and follow-up questions
|
|
|
|
**Completion Criterion**: Response delivered in chosen role with sections clearly labeled (Context, Request, Ideation, Refinement, Next Steps).
|
|
|