Why
SpecFact CLI has Definition of Ready (DoR) for backlog refinement. Teams also need Definition of Done (DoD) to ensure items moved to "Done" meet completion criteria. DoD is not modeled or validated today; there is no way to define team DoD rules (e.g. checklist: tests pass, docs updated, code reviewed) and run them against items in Done state.
What Changes
- NEW: Model DoD as a checklist or rule set (similar to DoR but for completion). Store DoD config per project (e.g.
.specfact/dod.yaml).
- NEW: When listing or exporting backlog items in "Done" state, optionally run DoD validation and attach DoD status (pass/fail + which criteria failed).
- EXTEND: Integrate into the backlog command group (e.g.
specfact backlog list, specfact backlog refine, or specfact backlog dod): for items in done state, show DoD status in output and export. No top-level DoD command.
- EXTEND: Documentation (agile-scrum-workflows, backlog-refinement) for DoD workflow.
Acceptance Criteria
- DoD can be configured (e.g. checklist); validator runs against items in Done state.
- DoD status (pass/fail, criteria) is visible in CLI/export for done items when enabled.
- Spec and tests first; implementation satisfies spec and tests.
- Documentation updated for DoD workflow.
OpenSpec Change Proposal: definition-of-done-support
Why
SpecFact CLI has Definition of Ready (DoR) for backlog refinement. Teams also need Definition of Done (DoD) to ensure items moved to "Done" meet completion criteria. DoD is not modeled or validated today; there is no way to define team DoD rules (e.g. checklist: tests pass, docs updated, code reviewed) and run them against items in Done state.
What Changes
.specfact/dod.yaml).specfact backlog list,specfact backlog refine, orspecfact backlog dod): for items in done state, show DoD status in output and export. No top-level DoD command.Acceptance Criteria
OpenSpec Change Proposal: definition-of-done-support