What inputs does flow-work accept?

It accepts a Plan file (plans/ .md), Beads IDs or titles directly, or chained instructions such as 'then review'.

What happens if rp-cli is not available?

You are prompted with a simplified setup asking only which branch to work on (current, new, or isolated worktree).

What guardrails does flow-work enforce?

It won't start without a plan, won't skip tests, and won't leave tasks half-done; it also requires completing a review cycle if chosen.

flow-work

Scanned

npx machina-cli add skill gmickel/gmickel-claude-marketplace/flow-work --openclaw

Files (1)

SKILL.md

2.1 KB

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

Source

git clone https://github.com/gmickel/gmickel-claude-marketplace/blob/main/plugins/flow/skills/flow-work/SKILL.mdView on GitHub

Overview

Flow-work provides a disciplined, git-backed workflow to execute a plan or Beads epic. It emphasizes finishing every plan step in order with task tracking, quality checks, and a structured commit flow. Use it when implementing a plan, working through a spec, or executing a Beads issue ID (bd-123, gno-45, app-12).

How This Skill Works

You provide a Plan file or Beads IDs, and the system first outputs required setup questions (about rp-cli and branch selection). After setup, it reads phases.md and executes each phase in order, performing tests along the way. If a review is requested, it can run /flow:impl-review after Phase 6 (optionally exporting for external review) and requires issues to be resolved until the review passes, all while enforcing guardrails to avoid starting without a plan, skipping tests, or leaving tasks half-done.

When to Use It

When implementing a plan from a plans/<slug>.md file
When working through a Beads epic or Beads IDs directly (e.g., bd-123, gno-45, app-12)
When following a documented steps/spec in phases.md
When executing chained instructions like 'then review with /flow:impl-review'
When you need a git-backed workflow with explicit tests and commit hygiene

Quick Start

Step 1: Confirm a plan file or Beads ID and verify rp-cli status (if applicable)
Step 2: Answer the FIRST: Setup Questions to choose branch and review options
Step 3: Read phases.md, execute phases in order, run /flow:impl-review after Phase 6 if requested, ensure tests pass, then commit

Best Practices

Ensure a plan file or Beads IDs are provided before starting
Check rp-cli availability and choose a branch strategy in the FIRST setup questions
Follow phases.md in order and perform tests before progressing
Track tasks diligently and commit with meaningful messages after each phase
Use /flow:impl-review after Phase 6 if requested and fix issues until the review passes

Example Use Cases

Implementing an OAuth flow using plans/oauth.md with Beads ID gno-40i
Executing Beads epic bd-123 and aligning implementation with the spec
Working through gno-40i and running /flow:impl-review after Phase 6
Following documented steps to build a feature per phases.md
Chaining commands like '/flow:work gno-40i then review via /flow:impl-review and fix issues'

Frequently Asked Questions

Add this skill to your agents