Skill

flow-execution

Executes Flow tasks from Beads or spec.md: claim ready work via bd ready, apply TDD red-green-refactor, record notes with bd note, commit changes, close tasks, sync markdown.

Git

Markdown

git-workflow

testing

npx claudepluginhub cofin/flow --plugin flow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

Supporting Assets

agents/openai.yaml

SKILL.md

Similar Skills

flow-code

Executes flow plan tasks one-by-one with TDD: reviews diffs before commits, requires bin/flow ci to pass, enforces project architecture standards.

flow

workflow-patterns

682

Guides task implementation using Conductor's TDD workflow, phase checkpoints, git commits, and verification protocols.

1 file

rmyndharis-antigravity-skills

unified-workflow

Enforces structured dev workflow using Beads for task tracking/dependencies, Superpowers for brainstorm/plan/TDD/review, git worktrees for isolation. Triggers at session start, before tasks, or unclear workflow.

template-bridge

Stats

Stars11

Forks4

Last CommitApr 26, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Flow Execution

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

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.

Flow Execution

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

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.