flow-work_skill

Overview

This skill executes a plan file or Beads epic systematically with a git-first, test-driven workflow. It acts as an execution lead: setting up branch context, running each phase in order, enforcing tests and quality gates, and committing work incrementally. Use it when you need reliable, repeatable implementation of a spec or Beads issue.

How this skill works

First it prompts required setup questions about where to work (branch/new branch/worktree) and whether to run a post-implementation review. After you respond, it reads phases.md and executes each phase in sequence: apply changes, run tests, perform quality checks, and create focused commits. If review was requested, it runs the chosen review flow (RepoPrompt chat or export mode) after Phase 6 and fixes any issues until the gate passes.

When to use it

• Implement a documented plan file (plans/<slug>.md)
• Work an explicit Beads issue ID (e.g., bd-123, gno-45, app-12)
• Follow a multi-step spec or checklist reliably
• Enforce tests and review gates before merging
• Automate commit and task tracking while preserving plan fidelity

Best practices

• Always reply to the initial setup questions before any changes are made
• Prefer a new branch or isolated worktree for exploratory or risky changes
• Run the Carmack-level review option for high-risk or public-facing code
• Keep test coverage and CI green; do not skip tests
• Use chained instructions (e.g., then review with /flow:impl-review) to express follow-ups

Example use cases

• /flow:work plans/oauth.md — implement OAuth plan step-by-step with tests and commits
• /flow:work gno-40i then review via /flow:impl-review — execute Beads epic then run RepoPrompt review
• Start work on a new feature by answering setup, selecting a new branch, and walking through phases.md phases
• Recover a half-finished task by re-anchoring to the original plan and finishing remaining phases