17 Retrospective
Use this when the process itself needs improvement.
Review
- What caused delay, confusion, or repeated tool failures?
- Did a workflow ship in
main.nfwithout launcher/CI parity? If yes, updatepipeline, grill template, orscripts/ci/check_workflow_parity.sh. - Which DSL2/template/parity rules should become persistent guidance?
- Were hooks too noisy or too weak?
- Did state accurately reflect work and verification?
- Did docs or memory-bank drift from code?
Update Targets
.cursor/skills/.cursor/rules/.cursor/hooks/.cursor/agents/workflow-state.yamlmemory-bank/session-notes.mdandmemory-bank/todos.md
Output
Record process changes and update routing docs if future agents should behave differently.
Source: GWMcElfresh/GoodWorkflows — distributed by TomeVault.