Task

Orchestrate one verifiable outcome end to end. Plans stay inline in chat unless the user requests a saved artifact and approves its destination.

Read when

Starting web services or debugging a browser preview? Open development-server logs before launch; reuse running services.
About to search the codebase, read a large file, or wade through long output? Open main-context.md.
About to grill? Open doctrine.md and the execution context.
About to grill or plan a Feature? Open strong-foundation.md. Skip it and the first provider is hardcoded into every caller, so the next ticket is a rewrite.
At a step that names a section? Open reference.md (lifecycle, plan contract, ship offer).
About to ask the user anything? Open Asking the user.
About to report progress or completion? Open Plain language.
About to commit, push, or open a PR from this chat? Open shipping.md. Skip it and you push to main, open a PR nobody approved, or track origin/main.