Workflows
Command surface

Use the workflow that matches the risk.

CafeKit ships more than the happy path. It includes ideation, implementation, debugging, hotfixing, docs, review, sync, git, and visual diagram workflows.

Spec-driven delivery path

The docs should always point back to this contract loop.

/hapo:specs

Turn intent into scope, evidence, requirements, design, and task packets.

/hapo:develop

Implement one approved task packet, not the whole chat memory.

/hapo:test

Run exact evidence commands and runtime checks.

/hapo:code-review

Review for spec compliance, regressions, security, and drift.

/hapo:sync

Update task_registry and task markdown 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#

CommandUse when
/hapo:specsYou need requirements, research, design, tasks, and validation.
/hapo:developA spec or task file is approved and ready for implementation.
/hapo:testYou need evidence from exact commands, build checks, tests, UI checks, or runtime reachability.
/hapo:code-reviewYou need adversarial review for bugs, security, scope drift, and missing proof.
/hapo:syncTask status, task_registry, and task markdown must move after proof, or drift needs audit.

Use /hapo:brainstorm before this path only when the idea is unclear, architectural choices are open, or scope needs pressure-testing.

Bug and incident workflow#

CommandUse when
/hapo:debugRoot cause is unknown. It is diagnostic-first and should produce evidence before code changes.
/hapo:hotfixA bug must be fixed after diagnosis, with smallest safe change and regression checks.

Documentation and artifacts#

CommandUse when
/hapo:docs --initProject docs are missing.
/hapo:docs --updateSource changed enough that broader docs should refresh.
/hapo:docs --reconstruct <scope>You need source-backed as-is docs for an existing system.
/hapo:generate-graph <request>Architecture, flow, sequence, or state diagrams would help.

Release workflow#

CommandUse when
/hapo:git commitVerified changes are ready for a focused conventional commit.
/hapo:git pushTests and review are clean enough to publish the branch.

OpenCode installs equivalent prefix-free commands such as /specs, /develop, /test, and /code-review.