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

1. Select ready work from bd ready and claim it before editing.
2. Read the relevant spec, notes, patterns, affected files, and validation commands.
3. Record investigation findings with bd note.
4. Follow red-green-refactor: write the failing test, verify the failure, implement minimally, verify green, then refactor.
5. Commit targeted changes, close the Beads task with evidence, and sync markdown when policy requires it.

Guardrails