Flow execution

Context-Driven Development toolkit for AI agents — spec-first planning, TDD workflow, and Beads integration.

Install

npx -y skills add cofin/flow --skill flow-execution

Assembled 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 implementing Flow tasks from Beads or spec.md, claiming ready work, applying TDD, recording task notes, committing, and syncing after task state changes.

SKILL.md

1.9 KB, as published. Nobody here has run it

Flow Execution

Use this lifecycle skill when implementation starts after a Flow plan or ready Beads task exists.

Beads mode: Skip every bd invocation when the SessionStart hook reports Beads Backend: Missing (None) or Disabled via plugin config (useBeads=false). Treat spec.md markers as fallback source of truth and skip /flow:sync. Never halt for missing Beads. See ../flow/references/discipline.md.

Workflow

Select ready work from bd ready and 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

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.