Help us improve
Share bugs, ideas, or general feedback.
From kimchi
Asks structured, iterative clarification questions on feature ideas across functional, data, integration, constraint, and scope categories, producing .kimchi/CONTEXT.md for Kimchi planning.
npx claudepluginhub tromml/kimchi --plugin kimchiHow this skill is triggered — by the user, by Claude, or both
Slash command
/kimchi:clarifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<command_purpose>
Clarifies feature requests via targeted questions on problems, users, outcomes, and detects contradictions in proposed requirements.
Plans single features, endpoints, or infrastructure via Socratic conversation to uncover requirements, edge cases, failure modes, and constraints; outputs markdown feature plan artifact before coding.
Collaboratively explores feature requirements and options through dialogue, producing a right-sized requirements document for implementation planning. Use for vague ideas, brainstorming, or scoping ambitious requests.
Share bugs, ideas, or general feedback.
<command_purpose> Extract complete understanding of a feature idea through structured, iterative clarification questions. Output a CONTEXT.md that captures all decisions so downstream stages never need to ask the user again. </command_purpose>
Feature idea from $ARGUMENTS. If empty, ask: "What feature or change would you like to plan?"
Analyze the idea for:
Ask questions in focused batches (3-5 at a time) using the AskUserQuestion tool. Draw from these categories but only ask what's relevant:
Functional Questions:
Data Questions:
Integration Questions:
Constraint Questions:
Scope Questions:
Create .kimchi/ directory if it doesn't exist, then write .kimchi/CONTEXT.md:
# Feature: [Feature Name]
**Gathered:** [today's date]
**Status:** Ready for requirements extraction
<domain>
## Feature Boundary
[Clear statement of what this feature delivers. The scope anchor.]
</domain>
<decisions>
## Implementation Decisions
### [Area 1 discussed]
- [Specific decision made]
- [Another decision]
### [Area 2 discussed]
- [Specific decision made]
### Claude's Discretion
[Areas where user said "you decide" or didn't express preference — Claude has flexibility here]
</decisions>
<specifics>
## Specific Ideas
[Any "I want it like X" references, particular behaviors, interaction patterns mentioned]
[If none: "No specific requirements — open to standard approaches"]
</specifics>
<deferred>
## Deferred Ideas
[Ideas that came up but belong in future work. Captured so they're not lost.]
[If none: "None — discussion stayed within feature scope"]
</deferred>
Show the user a summary of CONTEXT.md and ask: "Does this capture your intent? Anything to add or correct?"
If corrections needed, update CONTEXT.md and confirm again.
Report: "Clarification complete. Saved to .kimchi/CONTEXT.md"
Suggest: "Run /kimchi:requirements to extract and categorize requirements."