Flow completion
Context-Driven Development toolkit for AI agents — spec-first planning, TDD workflow, and Beads integration.
npx -y skills add cofin/flow --skill flow-completionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
SKILL.md
1.7 KB, as published. Nobody here has run it
Flow Completion
Use this lifecycle skill for review, finish, archive, revert, docs, validation, and final cleanup work.
Workflow
- Run fresh verification before claiming a phase or flow is complete.
- Review implementation against the spec, tests, patterns, security, architecture, and performance risks as appropriate.
- Capture reusable learnings and elevate patterns into project knowledge.
- Archive completed flows and preserve current-state guidance.
- For reverts, identify the logical Flow scope and avoid unrelated user changes.
Guardrails
- No completion claim without fresh verification evidence.
- Do not archive flows whose code, tests, Beads tasks, and markdown views disagree.
- Do not revert unrelated files or user changes.
- Keep knowledge chapters current-state oriented; avoid historical logs outside learnings.
Validation
- Run full relevant test and validation commands before finish/archive.
- Confirm Beads tasks are closed or intentionally blocked/deferred.
- Confirm
spec.md, learnings, patterns, and knowledge chapters reflect the current state.
References Index
Example
User: "Finish this flow."
Action: run verification, review against the spec, close or explain remaining tasks, sync markdown, elevate reusable patterns, and present finish options.