How do I install the Flow Work skill?

Run npx skillmds add tools-only/flow-work in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flow Work safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flow Work?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flow Work free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flow Work?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flow Work by tools-only — Agent Skill

Name: Flow Work
Rating: 4.2 (5 reviews)
Author: tools-only

Flow Work

Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).

tools-only 3e800c5 3 files · 5.1 KB Updated Sep 9, 2026 7 repo stars

File contents

Flow work

Execute a plan systematically. Focus on finishing.

Role: execution lead, plan fidelity first. Goal: complete every plan step in order with tests.

Input

Full request: #$ARGUMENTS

Accepts:

Plan file: plans/<slug>.md
Beads ID(s) or title(s) directly
Chained instructions like "then review with /flow:impl-review"

Examples:

/flow:work plans/oauth.md
/flow:work gno-40i
/flow:work gno-40i then review via /flow:impl-review and fix issues

If no plan/ID provided, ask for it.

FIRST: Setup Questions (REQUIRED)

Before doing anything else, output these questions as text (do NOT use AskUserQuestion tool):

Check if rp-cli available: which rp-cli >/dev/null 2>&1

If rp-cli available, ask both:

Quick setup before starting:

1. **Branch** — Where to work?
   a) Current branch
   b) New branch
   c) Isolated worktree

2. **Review** — Run Carmack-level review after?
   a) Yes, RepoPrompt chat
   b) Yes, export for external LLM (ChatGPT, Claude web)
   c) No

(Reply: "1a 2a", "current branch, export review", or just tell me naturally)

If rp-cli NOT available, ask only branch:

Quick setup: Where to work?
a) Current branch  b) New branch  c) Isolated worktree

(Reply: "a", "current", or just tell me)

Wait for response. Parse naturally — user may reply terse or ramble via voice. Do NOT read files or write code until user responds.

Workflow

After setup questions answered, read phases.md and execute each phase in order. If user chose review:

Option 2a: run /flow:impl-review after Phase 6, fix issues until it passes
Option 2b: run /flow:impl-review with export mode after Phase 6

Guardrails

Don't start without asking branch question
Don't start without plan
Don't skip tests
Don't leave tasks half-done

---name: flow-workdescription: Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).--- # Flow work Execute a plan systematically. Focus on finishing. **Role**: execution lead, plan fidelity first. **Goal**: complete every plan step in order with tests. ## Input Full request: #$ARGUMENTS Accepts: - Plan file: `plans/<slug>.md` - Beads ID(s) or title(s) directly - Chained instructions like "then review with /flow:impl-review" Examples: - `/flow:work plans/oauth.md` - `/flow:work gno-40i` - `/flow:work gno-40i then review via /flow:impl-review and fix issues` If no plan/ID provided, ask for it. ## FIRST: Setup Questions (REQUIRED) **Before doing anything else**, output these questions as text (do NOT use AskUserQuestion tool): Check if rp-cli available: `which rp-cli >/dev/null 2>&1` If rp-cli available, ask both: ``` Quick setup before starting: 1. **Branch** — Where to work? a) Current branch b) New branch c) Isolated worktree 2. **Review** — Run Carmack-level review after? a) Yes, RepoPrompt chat b) Yes, export for external LLM (ChatGPT, Claude web) c) No (Reply: "1a 2a", "current branch, export review", or just tell me naturally) ``` If rp-cli NOT available, ask only branch: ``` Quick setup: Where to work? a) Current branch b) New branch c) Isolated worktree (Reply: "a", "current", or just tell me) ``` Wait for response. Parse naturally — user may reply terse or ramble via voice. **Do NOT read files or write code until user responds.** ## Workflow After setup questions answered, read [phases.md](phases.md) and execute each phase in order. If user chose review: - Option 2a: run `/flow:impl-review` after Phase 6, fix issues until it passes - Option 2b: run `/flow:impl-review` with export mode after Phase 6 ## Guardrails - Don't start without asking branch question - Don't start without plan - Don't skip tests - Don't leave tasks half-done

Frequently asked questions