kimchi:status
This command should be used to check the current state of the Kimchi planning pipeline, including which stages have completed, what artifacts exist, and bead validation status.
Best use case
kimchi:status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
This command should be used to check the current state of the Kimchi planning pipeline, including which stages have completed, what artifacts exist, and bead validation status.
Teams using kimchi:status should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/status/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How kimchi:status Compares
| Feature / Agent | kimchi:status | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This command should be used to check the current state of the Kimchi planning pipeline, including which stages have completed, what artifacts exist, and bead validation status.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Kimchi Status Check the current state of the planning pipeline. ## Process 1. Check if `.kimchi/` directory exists 2. If no `.kimchi/` directory: - Report: "No active plan. Run `/kimchi:plan [idea]` to start." - Check if `.beads/` exists and report bead count if so 3. If `.kimchi/` exists, list artifacts and their status: ``` Check for each file: - .kimchi/CONTEXT.md → Stage 1: Clarification - .kimchi/REQUIREMENTS.md → Stage 2: Requirements - .kimchi/RESEARCH.md → Stage 3: Research - .kimchi/PLAN.md → Stage 4: Generation - .kimchi/PLAN-REVIEWED.md → Stage 5: Review - .kimchi/PLAN-DRAFT.md → Stage 6: Refinement - .kimchi/PLAN-REVISED-*.md → Stage 7: Cross-Model Review (list which models) - .kimchi/PLAN-SYNTHESIZED.md → Stage 8: Synthesis - .beads/manifest.yaml → Stage 9: Bead Conversion - .kimchi/VALIDATION-REPORT.md → Stage 10: Validation ``` 4. Check `.beads/` directory: - Count `.yaml` files (excluding manifest) - Check if `manifest.yaml` exists - Report validation status from VALIDATION-REPORT.md if it exists 5. Format output: ``` Kimchi Pipeline Status ═══════════════════════ Stage 1: Clarification ✓ CONTEXT.md (modified: [date]) Stage 2: Requirements ✓ REQUIREMENTS.md (modified: [date]) Stage 3: Research ✗ Not started Stage 4: Generation ✗ Not started Stage 5: Review ✗ Not started Stage 6: Refinement ✗ Not started Stage 7: Cross-Model Review ✗ Not started (models: none) Stage 8: Synthesis ✗ Not started Stage 9: Bead Conversion ✗ Not started Stage 10: Validation ✗ Not started Beads: [N] files in .beads/ Next step: Run /kimchi:research to continue pipeline ``` Use `ls -la` on the `.kimchi/` and `.beads/` directories to check file existence and modification dates.
Related Skills
kimchi:verification-before-completion
Use when about to claim work is complete, fixed, or passing — before committing or creating PRs. Evidence before assertions, always.
kimchi:validate
This command should be used to validate bead YAML files for standalone executability. Runs 4 validators (context completeness, deliverables clarity, test specification, isolation) and enriches failing beads. Eighth stage of the Kimchi planning pipeline.
kimchi:tdd
Use when implementing any feature, bugfix, or behavior change — before writing implementation code. Enforces RED-GREEN-REFACTOR cycle.
kimchi:systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior — before proposing fixes. Enforces 4-phase root cause analysis.
kimchi:simplicity-enforcement
Use when designing solutions, implementing features, or considering abstractions. Enforces YAGNI, minimal code, and preferring duplication over wrong abstraction.
kimchi:review
This command should be used to run multi-persona review of the implementation plan. Five specialized personas critique the plan for scope creep, complexity, premature optimization, and test coverage. Fifth stage of the Kimchi planning pipeline. Produces .kimchi/PLAN-REVIEWED.md.
kimchi:reset
This command should be used to clear the Kimchi working directory (.kimchi/) and start fresh. Preserves .beads/ directory. Use when starting a new planning session or recovering from a bad state.
kimchi:research
This command should be used to investigate codebase patterns, frameworks, and existing implementations before planning. Third stage of the Kimchi planning pipeline. Produces .kimchi/RESEARCH.md.
kimchi:requirements
This command should be used to extract and categorize requirements from CONTEXT.md into v1 (must have), v2 (next iteration), and out of scope. Second stage of the Kimchi planning pipeline. Produces .kimchi/REQUIREMENTS.md.
kimchi:refine
This command should be used to iteratively improve the plan until quality threshold is reached or diminishing returns detected. Sixth stage of the Kimchi planning pipeline. Produces .kimchi/PLAN-DRAFT.md.
kimchi:plan
This command should be used to run the Kimchi planning pipeline through refinement, transforming a vague idea into a draft plan ready for cross-model analysis. Orchestrates 6 stages: clarify, requirements, research, generate, review, refine. Use --full-auto to also run beads + validate after manual revise/synthesize.
kimchi:plan-synthesize
This command should be used to synthesize multiple cross-model plan revisions into a superior hybrid plan. Eighth stage of the Kimchi planning pipeline. Reads PLAN-REVISED-*.md files and outputs PLAN-SYNTHESIZED.md — the TRUE final plan.