25 lines
1.4 KiB
Markdown
25 lines
1.4 KiB
Markdown
## 1. OpenSpec artifacts
|
|
|
|
- [x] 1.1 Write proposal for `sm-flow-execution-hardening`
|
|
- [x] 1.2 Write design for execution hardening rules
|
|
- [x] 1.3 Add specs for checkpoints, question pool, cross-artifact alignment, and micro gate preservation
|
|
|
|
## 2. Protocol hardening
|
|
|
|
- [x] 2.1 Update `.agents/skills/sm-flow/SKILL.md` with explicit phase checkpoint and stage-completion rules
|
|
- [x] 2.2 Update `.agents/skills/sm-flow/references/phase-contracts.md` with question pool, cross-artifact alignment, and micro gate preservation rules
|
|
- [x] 2.3 Update `.agents/skills/sm-flow/references/fallbacks.md` so fallback declaration is mandatory and recorded
|
|
- [x] 2.4 Keep templates optional; only adjust them if existing references need minimal field hints rather than mandatory fixed formats
|
|
|
|
## 3. Workflow documentation
|
|
|
|
- [x] 3.1 Update `skill-workbench/docs/sm-flow/workflow.md` with the execution-hardening model
|
|
- [x] 3.2 Ensure retrospective learnings are reflected as protocol rules rather than only narrative notes
|
|
|
|
## 4. Validation
|
|
|
|
- [x] 4.1 Validate the OpenSpec change
|
|
- [x] 4.2 Verify key terms are consistently documented across skill, references, and workflow docs
|
|
- [x] 4.3 Backfill devflow records after implementation if the change proceeds beyond Draft
|
|
- [x] 4.4 Verify acceptance is satisfied by protocol/document changes alone, without requiring a standardized phase-report output format
|