dod

Plans a feature, function, or product as a Definition of Done before any code is written: what the finished product must accomplish (outcomes, components, the design bar, completion limits), never how the code does it, at a depth sized to the work. Then tracks the build against the plan and closes it with evidence. Walks fifteen consideration layers, from purpose and permissions to failure handling and rollout, asks only about the gaps the codebase cannot answer, requires an independent review that blocks only on what would fail, stops planning when the build starts, and records every unplanned change as a typed amendment so the closing report shows how much of the design the plan foresaw. Use only when the user explicitly invokes /dod or asks for a definition of done, a DoD plan, DoD status, or to close or report a DoD item, or when the project's instructions file states that feature planning goes through dod. Do not use for ordinary plan requests, task tracking, or explaining the Scrum term.