Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By Tromml
Transform vague feature ideas into validated standalone task beads for multi-agent execution using a 6-stage planning pipeline: clarify requirements, research codebase, generate plans, cross-model reviews, synthesize finals, and validate beads with TDD enforcement, simplicity checks, and self-improvement.
npx claudepluginhub tromml/kimchi --plugin kimchiConverts plan tasks into standalone bead YAML files with full context, deliverables, and test specifications
Analyzes initial feature description and generates structured clarification questions across 5 categories
Analyzes codebase to discover patterns, conventions, and reference implementations relevant to the planned feature
Reviews plans to identify unnecessary complexity, over-engineering, and premature abstractions
Reviews plans to identify non-essential features that should be cut or deferred to v2
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 extract complete understanding of a feature idea through structured clarification questions. First stage of the Kimchi planning pipeline. Produces .kimchi/CONTEXT.md.
Convert the kimchi plugin into OpenCode and Codex compatible formats using the bundled converter CLI. Requires bun runtime.
Custom skill
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Plan and autonomously build a software task end-to-end. Recons the codebase, applies preloaded memory, decomposes into the right number of phases, gets one confirmation, then prepares a single ready-to-paste /goal command — one paste between you and done — that drives execution to completion with built-in retry, fix-spec recovery, and per-phase memory writeback. Works on Claude Code and Codex.
AI-powered cascading development framework with design document system and multi-agent collaboration. Breaks down projects into Features (Mega Plan), Features into Stories (Hybrid Ralph), with auto-generated technical design docs, dependency-driven batch execution, Git Worktree isolation, and support for multiple AI agents (Codex, Amp, Aider, etc.).
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
Iterative plan review and execution workflow for Claude Code
Specification-driven development workflow: specify → plan → tasks → implement
AI-assisted deep planning with research, interview, external LLM review, and TDD approach
A Claude Code plugin that transforms vague ideas into validated, standalone task specifications (beads) for multi-agent execution.
Kimchi is prompt-native — all logic lives in markdown files. No TypeScript, no build step. Skills, agents, and personas work together through a 10-stage planning pipeline that produces self-contained task specs any agent can pick up and execute independently.
claude plugin add https://github.com/Tromml/kimchi
/kimchi:plan "Add user authentication with magic links"
This runs the full pipeline through refinement: clarify, requirements, research, generate, review, refine. The output is a draft plan in .kimchi/PLAN-DRAFT.md.
For fully automated end-to-end (plan through bead generation):
/kimchi:plan "Add user authentication with magic links" --full-auto
Kimchi breaks planning into discrete stages, each producing a markdown artifact:
idea
|
v
clarify Extract understanding through structured questions -> CONTEXT.md
|
requirements Categorize into v1 (must), v2 (next), out of scope -> REQUIREMENTS.md
|
research Investigate codebase patterns and frameworks -> RESEARCH.md
|
generate Create plan with tasks, deps, complexity estimates -> PLAN.md
|
review 5 personas critique for scope creep, complexity, etc -> PLAN-REVIEWED.md
|
refine Iterate until quality threshold or diminishing returns -> PLAN-DRAFT.md
|
plan-revise Fresh-eyes cross-model review (run per model) -> PLAN-REVISED-{model}.md
|
plan-synthesize Merge cross-model revisions into hybrid plan -> PLAN-SYNTHESIZED.md
|
beads Convert to standalone YAML task specs -> .beads/
|
validate 4 validators check standalone executability -> enriched beads
Each stage can be run independently. The pipeline writes everything to .kimchi/ in your project root.
"Taste, adjust, remember. Each batch teaches the next."
Halmoni is Kimchi's self-improvement system. Like a Korean grandmother who tastes her kimchi and adjusts the recipe each time, Halmoni observes what happened during execution, proposes improvements to skills and validators, validates them against history, and applies them with versioning.
/kimchi:halmoni --from-bead 008
/kimchi:halmoni --from-feedback "the review stage missed the N+1 query"
/kimchi:halmoni --taste-only
| Skill | Description |
|---|---|
kimchi:plan | Full pipeline orchestrator (clarify through refine) |
kimchi:clarify | Extract understanding through structured questions |
kimchi:requirements | Categorize requirements into v1, v2, out of scope |
kimchi:research | Investigate codebase patterns and frameworks |
kimchi:generate | Generate plan with tasks, deps, complexity |
kimchi:review | Multi-persona plan critique |
kimchi:refine | Iterative improvement until quality threshold |
kimchi:plan-revise | Cross-model fresh-eyes review |
kimchi:plan-synthesize | Synthesize cross-model revisions |
kimchi:beads | Convert plan to standalone bead YAML specs |
kimchi:validate | Validate beads for standalone executability |
| Skill | Description |
|---|---|
kimchi:tdd | RED-GREEN-REFACTOR cycle enforcement |
kimchi:systematic-debugging | 4-phase root cause analysis before proposing fixes |
kimchi:simplicity-enforcement | YAGNI, minimal code, duplication over wrong abstraction |
kimchi:verification-before-completion | Evidence before assertions, always |
kimchi:bead-protocol | Multi-agent bead execution coordination |
| Agent | Description |
|---|---|
kimchi:pipeline:clarifier | Generates structured clarification questions |
kimchi:pipeline:researcher | Discovers codebase patterns and conventions |
kimchi:pipeline:bead-converter | Converts plan tasks into standalone bead YAML |
| Agent | Description |
|---|---|
kimchi:review:complexity-detector | Identifies unnecessary complexity and over-engineering |
kimchi:review:feature-trimmer | Identifies non-essential features to cut or defer |
kimchi:review:scope-guardian | Catches scope creep and vague acceptance criteria |
kimchi:review:test-coverage-advocate | Identifies missing or insufficient test specs |
kimchi:review:premature-optimization-detector | Identifies optimizations not yet needed |