cofin/flow-execution
skills/flow-execution/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add cofin/flow flow-executionInstall 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 30, 2026, 4:48 PM5.5s1 file scanned
SKILL.md
- name:
- flow-execution
- description:
- 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.
Flow Execution
Use this lifecycle skill when implementation starts after a Flow plan or ready Beads task exists.
Workflow
- Select ready work from
bd readyand claim it before editing. - Read the relevant spec, notes, patterns, affected files, and validation commands.
- Record investigation findings with
bd note. - Follow red-green-refactor: write the failing test, verify the failure, implement minimally, verify green, then refactor.
- Commit targeted changes, close the Beads task with evidence, and sync markdown when policy requires it.
Guardrails
- Do not manually edit task status markers in markdown.
- Do not skip failing-test evidence for behavior changes.
- Do not silently descope messy tasks; refine or ask how to prioritize.
- Preserve unrelated user changes and keep edits scoped to the claimed task.
Validation
- Verify the new test failed for the intended reason before implementation.
- Run focused tests after each task and the repo’s aggregate verification before phase completion.
- Record test output, commit reference, and closure reason in Beads.
References Index
- Implement
- Discipline
Example
User: "Implement auth flow."
Action: claim the next ready Beads task, add code-path notes, write a failing auth test, implement the minimal behavior, verify, commit, close the task, and sync.
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-completion
tools
VerifiedTrustedCommunity
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
11SKILL.mdUpdated Apr 27, 2026