Plugin Claude Code
Durable state, contract and evidence layer for multi-session feature work: contract-bounded planning, autonomous phase orchestration with evidence-based acceptance, and ledger-versus-implementation review.
Agent
Use this agent when a zforge phase has reported DONE and its evidence must be independently verified before the planner accepts it. Typical triggers include /zforge:feature-orchestrate accepting a REPORTED phase during a long chain, and any run where the planner's context is the constrained resource. It reconciles the…
Agent
Use this agent when a phase of a zforge feature plan is ready to implement and its work should run in its own context. Typical triggers include /zforge:feature-orchestrate spawning a READY phase, resuming a phase whose agent was interrupted mid-run, and re-running a phase after a decision was rejected in review. See…
Skill Claude CodeCodex
Use this agent when a zforge phase has reported DONE and its evidence must be independently verified before the planner accepts it. Typical triggers include $zforge:feature-orchestrate accepting a REPORTED phase during a long chain, and any run where the planner's context is the constrained resource. It reconciles the…
Skill Claude CodeCodex
Route a concrete reproducible failure through the installed debugging skills; not for open-ended exploration.
Skill Claude CodeCodex
Execute an existing zforge feature plan autonomously with phase subagents and evidence-based acceptance.
Skill Claude CodeCodex
Resume an existing zforge feature plan interactively, implementing and accepting one phase at a time.
Skill Claude CodeCodex
Use this agent when a phase of a zforge feature plan is ready to implement and its work should run in its own context. Typical triggers include $zforge:feature-orchestrate spawning a READY phase, resuming a phase whose agent was interrupted mid-run, and re-running a phase after a decision was rejected in review. See…
Skill Claude CodeCodex
Summarize all zforge feature plans, phase counts, and standing flags in the current workspace.
Skill Claude CodeCodex
Plan a feature with zforge's completeness contract and write the appropriate requirements or implementation artifact tree.
Skill Claude CodeCodex
Check implementation against an existing zforge feature ledger; not for general code review.
Skill Claude CodeCodex
Show one zforge feature's phase progress, evidence gaps, standing flags, and open decisions.
Command
Route a failure to the right debug methodology.
Command
Autonomous multi-phase feature execution.
Command
Resume implementation on an existing feature, interactively.
Command
Show feature plan status for the current workspace.
Command
Plan a feature and write its artifact tree.
Command
Score zforge's workflow performance on a feature.
Command
Check implementation against the feature ledger.
Command
Show progress, flags and open decisions.
Skill Claude CodeCodex
This skill should be used when implementing or designing code with async data flows — "state management design", "async data flow", "stale data", "cache invalidation", "optimistic update", "init order", "race condition", "write then read", "data not updating", "cache not refreshing", "UI shows old data after save"…
Skill Claude CodeCodex
This skill should be used when the user asks to "orchestrate the feature", "run the phases", "resume implementation", "continue the plan", "the phase agent died", "the agent stopped on its usage limit", "accept this phase", "can these phases run in parallel", "is this phase done", "does this shortfall matter", or…
Skill Claude CodeCodex
This skill should be used when the user asks to "retro", "evaluate zforge", "review plugin performance", "score this session", or wants to assess how well zforge's workflow served a feature. Evaluates zforge's workflow scaffolding, not the project's technical decisions or LLM reasoning quality.
Skill Claude CodeCodex
This skill should be used when the user asks to "plan a feature", "what goes in the phase file", "which file owns this", "what evidence class is this", "how do I verify a claim no test can settle", "where should this doc go", or when writing, reading or updating any zforge feature document under docs/{feature}/.…