work-step

Work Step

Use this when the user says to continue, work the next step, or implement the approved plan.

Workflow

1. Find the active plan in the relevant docs/features/*.md or docs/concepts/*.md.
2. Confirm the plan status is approved.
3. Pick the first unchecked delivery-plan step.
4. Surface the checklist in the live view (see Plan Checklist Mirror below): mirror the plan's steps into your host's native to-do panel with the step you are about to implement marked in progress, and run codument steps --emit so codument watch shows the active step. Post that checklist inline in the chat as well — the step just completed, the step now starting, and what remains — because the native to-do panel and the watch tape are not the chat transcript, and a run that does not wait between steps otherwise advances with no in-chat marker.
5. Read docs/.registry.json before touching source files — codument context --plan <active-plan> pulls the grounded working set for every feature the plan routes to (owning docs, invariants with their test pointers, primary sources, one-hop deps) in one deterministic command, and --feature <slug> / --file <path> narrows it to the slice this step touches. When the question is only which doc owns this file — the one fact you need before editing it — --file <path> --owner answers in a line instead of a pack, so the lookup is cheap enough to actually run rather than guess. Fall back to reading the registry directly if the CLI is unavailable.
6. Implement only that step.
7. Use tdd or the strongest practical verification loop.
8. Register each NEW source file by running codument map materialize <file> (see Feature Map Materialization), then update the mapped docs + registry as part of the same step.
9. Mark the step complete — in the plan doc, and in the mirrored native to-do list — only after verification passes. If this was the final step, compact the ## Delivery Plan block per plan-with-docs (Compaction on ship): lift surviving decisions into ## Decisions/ADRs and any newly-true constraint into ## Invariants & boundaries, then delete the delivery scaffolding so the durable doc is left in the standard's layers.
10. Proceed directly to review-work for this step without waiting. Never start the next delivery-plan step from here — review and commit come first, in either mode.
11. In gated mode, stop instead and present the user with end-of-step options:
    • Run review-work now (recommended)
    • Make a specific correction to this step
    • Pause here