git-learn/openspec/changes/sm-flow-execution-hardening/tasks.md

1. OpenSpec artifacts

• 1.1 Write proposal for sm-flow-execution-hardening
• 1.2 Write design for execution hardening rules
• 1.3 Add specs for checkpoints, question pool, cross-artifact alignment, and micro gate preservation

2. Protocol hardening

• 2.1 Update .agents/skills/sm-flow/SKILL.md with explicit phase checkpoint and stage-completion rules
• 2.2 Update .agents/skills/sm-flow/references/phase-contracts.md with question pool, cross-artifact alignment, and micro gate preservation rules
• 2.3 Update .agents/skills/sm-flow/references/fallbacks.md so fallback declaration is mandatory and recorded
• 2.4 Keep templates optional; only adjust them if existing references need minimal field hints rather than mandatory fixed formats

3. Workflow documentation

• 3.1 Update skill-workbench/docs/sm-flow/workflow.md with the execution-hardening model
• 3.2 Ensure retrospective learnings are reflected as protocol rules rather than only narrative notes

4. Validation

• 4.1 Validate the OpenSpec change
• 4.2 Verify key terms are consistently documented across skill, references, and workflow docs
• 4.3 Backfill devflow records after implementation if the change proceeds beyond Draft
• 4.4 Verify acceptance is satisfied by protocol/document changes alone, without requiring a standardized phase-report output format