Summary

Define a shared “Definition of Done” for plans, establishing what it means for a plan to be truly complete beyond its per-plan acceptance criteria.

Motivation

We researched Scrum’s Definition of Done but never created one. Individual plans have “Done when” sections but there’s no shared standard (e.g., “acceptance criteria met with evidence, log entry written, working notes updated, no new MUST errors introduced”).

Steps

  1. Draft shared Definition of Done as a section in the plans/index.md spec.
  2. Include: acceptance criteria met, evidence recorded in log, no regression in satisfaction deficit, working notes point to completion.
  3. Apply retroactively to completed plans as a check.

Done when

  • Definition of Done exists in plans/index.md
  • Applied to at least one plan completion

Dependencies

None.

Log

2026-03-07 — Created from gap analysis of 12 researched-but-unapplied PM practices.