docs(crit): rewrite skill description and simplify framework steps
This commit is contained in:
+1
-1
@@ -7,7 +7,7 @@ Skills that work in all CLI agents.
|
||||
- [agent-handoff](in-progress/agent-handoff/SKILL.md) — Hand the current conversation off to a fresh background agent that picks up the work immediately.
|
||||
- [commit-staged](engineering/commit-staged/SKILL.md) — Commit staged files with a conventional commit message.
|
||||
- [conversation-summary](pkm/conversation-summary/SKILL.md) — Save the current conversation as a comprehensive report note in your Obsidian vault, following OKF v0.1 conventions.
|
||||
- [crit](pkm/crit/SKILL.md) — Brainstorm with AI using the CRIT framework to generate and evaluate ideas.
|
||||
- [crit](pkm/crit/SKILL.md) — Run the CRIT framework — give the AI Context, assign it a Role, let it Interview you one question at a time, then issue the Task.
|
||||
- [implement-isolation](engineering/implement-isolation/SKILL.md) — Implement a piece of work based on a spec or set of tickets in isolation.
|
||||
- [implement-isolation-tmux](engineering/implement-isolation-tmux/SKILL.md) — Dispatch a child agent in an isolated git worktree to implement a piece of work based on a PRD or set of issues.
|
||||
- [knowledge-gardener](in-progress/knowledge-gardener/SKILL.md) — Run vault-aware semantic search, synthesis, note creation, linking, and Zettelkasten workflows for this Obsidian vault.
|
||||
|
||||
@@ -5,9 +5,9 @@ Daily code work.
|
||||
## User-invoked
|
||||
|
||||
- [commit-staged](commit-staged/SKILL.md) — Commit staged files with a conventional commit message.
|
||||
- [implement-isolation](implement-isolation/SKILL.md) — Implement work in an isolated git worktree via subagent with review.
|
||||
- [implement-isolation-tmux](implement-isolation-tmux/SKILL.md) — Dispatch a child agent into its own tmux window in an isolated git worktree for fire-and-forget implementation.
|
||||
- [project-context-pack](project-context-pack/SKILL.md) — Use when the user wants a bounded repo context pack, project map, codebase index, or cached memory file so later work uses fd/rg/tree-sitter/LSP instead of repeated browsing.
|
||||
- [implement-isolation](implement-isolation/SKILL.md) — Implement a piece of work based on a spec or set of tickets in isolation.
|
||||
- [implement-isolation-tmux](implement-isolation-tmux/SKILL.md) — Dispatch a child agent in an isolated git worktree to implement a piece of work based on a PRD or set of issues.
|
||||
- [project-context-pack](project-context-pack/SKILL.md) — Build a bounded repo context pack (project map, codebase index, cached memory file) so later work uses fd/rg/tree-sitter/LSP instead of repeated browsing.
|
||||
- [setup-skills](setup-skills/SKILL.md) — Configure this repo for the engineering skills, set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
|
||||
|
||||
## Model-invoked
|
||||
|
||||
@@ -5,7 +5,7 @@ Personal knowledge management.
|
||||
## User-invoked
|
||||
|
||||
- [conversation-summary](conversation-summary/SKILL.md) — Save the current conversation as a comprehensive report note in your Obsidian vault, following OKF v0.1 conventions.
|
||||
- [crit](crit/SKILL.md) — Brainstorm with AI using the CRIT framework to generate and evaluate ideas.
|
||||
- [crit](crit/SKILL.md) — Run the CRIT framework — give the AI Context, assign it a Role, let it Interview you one question at a time, then issue the Task.
|
||||
- [research-vault](research-vault/SKILL.md) — Research a topic through a one-question-at-a-time learning conversation, answer directly, share resources when useful, and save a linked OKF-conformant research packet in the Obsidian vault.
|
||||
- [youtube-video-capture](youtube-video-capture/SKILL.md) — Fetch subtitles from a YouTube video, summarize the content, and save both the summary and raw subtitles to the Video bundle in the Obsidian vault.
|
||||
|
||||
|
||||
+38
-61
@@ -1,90 +1,67 @@
|
||||
---
|
||||
name: crit
|
||||
description: brainstorm with AI using the CRIT framework to generate and evaluate ideas.
|
||||
description: Run the CRIT framework — give the AI Context, assign it a Role, let it Interview you one question at a time, then issue the Task.
|
||||
disable-model-invocation: true
|
||||
---
|
||||
|
||||
## Purpose
|
||||
|
||||
This skill implements the CRIT (Context-Request-Ideation-Tone) framework for structured brainstorming and idea evaluation.
|
||||
CRIT is a four-step prompt framework by Geoff Woods: **Context, Role, Interview,
|
||||
Task**. The sequence front-loads thinking before execution — the AI learns your
|
||||
world, takes a specific lens, interviews you to surface what matters, then acts.
|
||||
|
||||
## Core Workflow
|
||||
The insight: most people skip to Task and get generic output. The Interview
|
||||
step — one question at a time, max three — is where the signal lives.
|
||||
|
||||
### Step 1: Context Analysis
|
||||
Before generating ideas, establish the foundation:
|
||||
## Steps
|
||||
|
||||
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?
|
||||
Run these four steps in order when the user invokes `/crit`.
|
||||
|
||||
2. **Assess Current State**
|
||||
- What problems or opportunities exist?
|
||||
- What has been tried before (if applicable)?
|
||||
- What resources are available?
|
||||
### 1. Context — Give the AI your world
|
||||
|
||||
**Completion Criterion**: Domain, constraints, and current state captured in a compact summary (3-5 sentences).
|
||||
Ask the user: "What should I know about you, your goals, your audience, and any
|
||||
constraints?"
|
||||
|
||||
### Step 2: Request Clarification
|
||||
Structure the brainstorming request:
|
||||
Capture the answer in one paragraph. More detail is better.
|
||||
|
||||
1. **Define the Specific Goal**
|
||||
- What concrete outcome do you want?
|
||||
- What success criteria will be used?
|
||||
- What is the expected timeline?
|
||||
**Completion criterion**: One paragraph covering identity, goal, audience, and
|
||||
constraints — confirmed by the user.
|
||||
|
||||
2. **Gather Input Requirements**
|
||||
- What information is needed to proceed?
|
||||
- What assumptions should be validated?
|
||||
- What data or resources are required?
|
||||
### 2. Role — Assign a viewpoint
|
||||
|
||||
**Completion Criterion**: Goal and input requirements captured as 1-3 concrete statements, each with a checkable success criterion.
|
||||
Ask the user: "What role should I take?"
|
||||
|
||||
### Step 3: Ideation
|
||||
Generate diverse, high-quality ideas:
|
||||
Guide toward a specific lens — "strategy coach who uncovers blind spots,"
|
||||
"editor who cuts fluff," "architect who finds leverage points." Not "be
|
||||
helpful."
|
||||
|
||||
1. **Divergent Thinking Phase**
|
||||
- Generate 5-10 initial concepts without judgment
|
||||
- Apply different perspectives (technical, business, user experience)
|
||||
- Include both obvious and unconventional options
|
||||
**Completion criterion**: A single sentence assigning a named role that implies
|
||||
a specific viewpoint.
|
||||
|
||||
2. **Convergent Analysis Phase**
|
||||
- Evaluate each idea against success criteria
|
||||
- Score ideas on feasibility, impact, and alignment
|
||||
- Identify patterns and synergies between ideas
|
||||
### 3. Interview — One question at a time
|
||||
|
||||
**Completion Criterion**: Minimum 5 distinct ideas generated and evaluated with scores.
|
||||
Instruct yourself: "Ask me no more than three questions, one at a time, to
|
||||
clarify what I'm trying to achieve."
|
||||
|
||||
### Step 4: Iterative Refinement
|
||||
Improve selected ideas:
|
||||
Ask one question. Wait for the answer. Then ask the next. Max three. Do not
|
||||
batch them.
|
||||
|
||||
1. **Select Top Candidates**
|
||||
- Choose 2-3 ideas with highest potential
|
||||
- Detail implementation approach for each
|
||||
- Identify risks and mitigation strategies
|
||||
This step forces the user to slow down and think, and teaches the AI what
|
||||
actually matters.
|
||||
|
||||
2. **Develop Action Plans**
|
||||
- Break down into concrete steps
|
||||
- Assign priorities and dependencies
|
||||
- Define success metrics and checkpoints
|
||||
**Completion criterion**: 1-3 questions asked and answered, one at a time.
|
||||
Stop asking when the user signals readiness or you've asked three.
|
||||
|
||||
**Completion Criterion**: 2-3 refined ideas with detailed action plans.
|
||||
### 4. Task — Issue the assignment
|
||||
|
||||
### Step 5: Tone & Delivery
|
||||
Adapt communication to the audience:
|
||||
Ask the user: "What's the task?"
|
||||
|
||||
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
|
||||
Guide toward a short, clear, slightly uncomfortable prompt that asks the AI to
|
||||
*think*, not just write. Reference the preceding interview.
|
||||
|
||||
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
|
||||
> "Based on our conversation, give me three non-obvious actions I can take.
|
||||
> Make them surprising but realistic."
|
||||
|
||||
**Completion Criterion**: Response delivered in chosen role with sections clearly labeled (Context, Request, Ideation, Refinement, Next Steps).
|
||||
Execute the task.
|
||||
|
||||
**Completion criterion**: Task executed and result delivered to the user.
|
||||
|
||||
Reference in New Issue
Block a user