/hapo:develop#

/hapo:develop implements work from an approved spec.

Usage#

/hapo:develop <feature-name>
/hapo:develop <feature-name> <task-file>

Recommended:

/hapo:develop meet-transcript-mvp task-R0-02-auth-setup-dual-mode.md

Two Modes#

Specific-task mode#

When you pass a task file, CafeKit should:

1. load exactly one task packet
2. implement only that task
3. run verification
4. sync state
5. stop

Full-spec mode#

When you pass only a feature name, CafeKit should:

1. read task_registry
2. select the next unblocked task
3. execute one task loop
4. sync state
5. continue only after that task is verified

Quality Gate Rules#

CafeKit should not mark a task complete unless:

• preflight compile/typecheck/build health is acceptable
• exact required commands have been executed
• evidence matches the task's completion criteria
• review passes

Important semantics:

• PRECHECK_FAIL outranks NO_TESTS
• NO_TESTS is not automatic success
• placeholders do not count as end-to-end proof

Docs Checkpoint#

After a verified task completes, CafeKit runs a task-level docs checkpoint:

• Docs impact: none
• Docs impact: minor
• Docs impact: major

Only affected docs should be updated. This is intentionally lighter than a full project-wide docs regeneration.

Best Practice#

Prefer task-by-task runs over one-shot feature implementation. It keeps diffs smaller and makes task_registry trustworthy.