develop

A plan-before-build workflow enforces planning, dependency research, spec generation, and approval gating before any code dispatch occurs. It mandates an initial todo_write call to capture the build steps, preventing agents from skipping required structural phases.

Yes, approval gating pauses execution after spec generation and before implementation. The agent writes the build spec, then explicitly waits for your next message to proceed, preventing silent drift from your intended canvas card design.

Verify build correctness by requiring render_capture or equivalent testing verification after dispatch. You maintain doc consistency by mandating document reconciliation steps alongside the render verification to ensure outputs match the original spec.

Yes, build orchestration applies universally to canvas cards, standalone programs, and doc-only artifacts. It routes build-shaped requests through dependency research, decomposition, and verification invariants regardless of the artifact type.

Agents skip dependency research when a workflow lacks explicit grounding triggers. Enforcing a universal build flow gate triggers research for non-trivial domain work and loads the card-class-handbook for canvas builds to reduce wrong API usage.

You need spec generation and approval gating whenever a build-shaped request requires decomposition and dispatch. This process ensures the agent writes a spec, pauses for your review, and only then proceeds to implementation to avoid incorrect outputs.