praxis

Use at ship time to merge the spec into the living documentation, delete the staging spec and plan, and ask how to finish.

Use when taking over an existing codebase that has no living document. Produces a factual record of what already exists.

Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.

Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.

Use at session start to learn how Praxis skills are invoked and why triage runs before every task.

Use when the goal is vague or vision-level and can't be defined well enough for design questions.

Use after design approval for milestone plans with executable acceptance.

Use when the user asks to release, version, tag, or publish.

Use for non-trivial or parallel work that should happen in a separate git worktree.

Use when implementing or fixing production code with tests.

Use before merge, after subagents, or for spec/plan review.

Use when a plan has parallel tasks and the harness supports dispatching subagents.

Use for bugs, unexpected behavior, regressions, or failing tests you did not write.