Use the workflow that matches the risk.
CafeKit ships more than the happy path. It includes ideation, implementation, debugging, fixing, docs, review, sync, git, and visual diagram workflows.
The docs should always point back to this contract loop.
Turn intent into scope, evidence, requirements, design, and task packets.
Implement one approved task packet, not the whole chat memory.
Run exact evidence commands and runtime checks.
Review for spec compliance, regressions, security, and drift.
Update process-first Status and inline Receipt only after proof, or audit drift.
The main delivery path is explained in depth in Core workflow. Use this page as the command selector when the work is not the standard feature path.
Core feature workflow#
| Command | Use when |
|---|---|
/cf:specs | You need C1 scope, a reviewed plan, flat executable tasks, and a C2 decision. |
/cf:develop | A spec or task file is approved and ready for implementation. |
/cf:test | You need evidence from exact commands, build checks, tests, UI checks, or runtime reachability. |
/cf:code-review | You need adversarial review for bugs, security, scope drift, and missing proof. |
/cf:sync | Observed task Status or the final inline Receipt must be synchronized without inventing proof. |
Use /cf:brainstorm before this path only when the idea is unclear, architectural choices are open, or scope needs pressure-testing.
Bug and incident workflow#
| Command | Use when |
|---|---|
/cf:debug | Root cause is unknown. It is diagnostic-first and should produce evidence before code changes. |
/cf:fix | A bug must be fixed after diagnosis, with smallest safe change and regression checks. |
Documentation and artifacts#
| Command | Use when |
|---|---|
/cf:docs --init | Project docs are missing. |
/cf:docs --update | Source changed enough that broader docs should refresh. |
/cf:docs --reconstruct <scope> | You need source-backed as-is docs for an existing system. |
Release workflow#
| Command | Use when |
|---|---|
/cf:git commit | Verified changes are ready for a focused conventional commit. |
/cf:git push | Tests and review are clean enough to publish the branch. |
Codex CLI exposes the same public workflow as native $cf-* skills.