メニュー
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).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
John Carmack-level implementation review via rp-cli for current branch changes. Use when reviewing code changes, PRs, or implementations. Triggers on mentions of code review, implementation review, or PR review.
Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).
Resume interrupted flow:work session from last checkpoint. Reads flow-progress.txt to restore context and continue work.
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
| name | flow-work |
| description | 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). |
Execute a plan systematically. Focus on finishing.
Role: execution lead, plan fidelity first. Goal: complete every plan step in order with tests.
Full request: #$ARGUMENTS
Accepts:
plans/<slug>.mdExamples:
/flow:work plans/oauth.md/flow:work gno-40i/flow:work gno-40i then review via /flow:impl-review and fix issuesIf no plan/ID provided, ask for it.
Before doing anything else, output these questions as text:
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 b) No
(Reply: "1a 2b", "current branch, skip 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.
After setup questions answered:
flow-progress.txt at repo root to track session state (enables /flow:resume)flow-progress.txt and TodoWrite after each task completion/flow:impl-review after Phase 6, fix issues until it passesTodoWrite tool to track tasks visibly in the UITask tool with subagent_type for research agents