القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Convert the kimchi plugin into OpenCode and Codex compatible formats using the bundled converter CLI. Requires bun runtime.
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.
Use when executing a bead task. Detects orchestration mode (ACFS or GasTown) from .beads/manifest.yaml and enforces the appropriate execution discipline.
This command should be used to convert the final plan into standalone bead YAML task specifications for multi-agent execution. Ninth stage of the Kimchi planning pipeline. Produces .beads/ directory. Supports both ACFS and GasTown orchestration modes.
This command should be used to run the Kimchi self-improvement system. Observes execution outcomes, proposes incremental improvements to skills/validators/personas, validates against history, and applies with versioning.
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.
| name | kimchi:status |
| description | 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. |
Check the current state of the planning pipeline.
Check if .kimchi/ directory exists
If no .kimchi/ directory:
/kimchi:plan [idea] to start.".beads/ exists and report bead count if soIf .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
Check .beads/ directory:
.yaml files (excluding manifest)manifest.yaml existsFormat 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.