cofin/flow-completion
skills/flow-completion/SKILL.md
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
$ install --global
skillsauthnpx skillsauth add cofin/flow flow-completionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 5:25 AM55.9s2 files scanned
SKILL.md
- name:
- flow-completion
- description:
- Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
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
- Review
- Finish
- Archive
- Revert
- Docs
- Validate
- Cleanup
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.
Related Skills
cofin/flow-sync-status
testing
VerifiedTrustedCommunity
Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.
11SKILL.mdUpdated Apr 27, 2026
cofin/flow-setup
testing
VerifiedTrustedCommunity
Use when initializing Flow in a repo, configuring .agents, installing or checking Beads bd, setting local-only sync policy, or creating first project context files.
11SKILL.mdUpdated Apr 27, 2026
cofin/flow-planning
data-ai
VerifiedTrustedCommunity
Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
11SKILL.mdUpdated Apr 27, 2026
cofin/flow-execution
testing
VerifiedTrustedCommunity
Use when implementing Flow tasks from Beads or spec.md, claiming ready work, applying TDD, recording task notes, committing, and syncing after task state changes.
11SKILL.mdUpdated Apr 27, 2026