菜单
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).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
Resume interrupted flow:work session from last checkpoint. Reads flow-progress.txt to restore context and continue 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).
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-plan |
| description | 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). |
Turn a rough idea into a practical plan file. This skill does not write code.
Role: product-minded planner with strong repo awareness. Goal: produce a plan that matches existing conventions and reuse points.
Full request: #$ARGUMENTS
Accepts:
Examples:
/flow:plan Add OAuth login for users/flow:plan gno-40i/flow:plan gno-40i then review via /flow:plan-review and fix issuesIf empty, ask: "What should I plan? Give me the feature or bug in 1-5 sentences."
Flow v1.0 uses smart defaults instead of asking setup questions. Override with flags if needed.
| Setting | Default | Override Flag |
|---|---|---|
| Research | repo-scout (fast) | --research=deep for context-scout |
| Review | auto (only if complex) | --review=always or --review=skip |
| Depth | auto-detect | --depth=simple|standard|deep |
/flow:plan fix typo in README # Auto: simple, no questions
/flow:plan add OAuth login --depth=deep # Force deep research
/flow:plan refactor auth --review=skip # Skip review even if complex
/flow:plan add feature --research=deep # Use context-scout (rp-cli)
For complex tasks (score 4+), Flow will still confirm:
Detected: Complex task (auth system changes)
Recommended: DEEP plan with full research and review
Proceed with defaults? [Y/n/customize]
If rp-cli NOT available: context-scout unavailable, uses repo-scout automatically.
Read steps.md and follow each step in order. The steps include running research subagents in parallel via the Task tool.
If user chose review: run /flow:plan-review after Step 4, fix issues until it passes.
Read examples.md for plan structure examples.
plans/<slug>.md