flow-plan
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseFlow plan
Flow 规划
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.
将粗略想法转化为实用的计划文件。该Skill不负责编写代码。
角色:具备产品思维的规划师,熟悉代码仓库情况。
目标:生成符合现有规范、可复用的计划。
Input
输入
Full request: #$ARGUMENTS
Accepts:
- Feature/bug description in natural language
- Beads ID(s) or title(s) to plan for
- Chained instructions like "then review with /flow:plan-review"
Examples:
/flow:plan Add OAuth login for users/flow:plan gno-40i/flow:plan gno-40i then review via /flow:plan-review and fix issues
If empty, ask: "What should I plan? Give me the feature or bug in 1-5 sentences."
完整请求:#$ARGUMENTS
接受:
- 自然语言描述的功能或Bug需求
- 待规划的Beads ID(或标题)
- 链式指令,例如“随后用/flow:plan-review进行审核”
示例:
/flow:plan 为用户添加OAuth登录功能/flow:plan gno-40i/flow:plan gno-40i 随后通过/flow:plan-review审核并修复问题
如果输入为空,询问:"需要我规划什么?请用1-5句话描述功能或Bug需求。"
FIRST: Setup Questions (if rp-cli available)
第一步:设置问题(若rp-cli可用)
Check:
which rp-cli >/dev/null 2>&1If available, output these questions as text (do NOT use AskUserQuestion tool):
Quick setup before planning:
1. **Research approach** — Use RepoPrompt for deeper context?
a) Yes, context-scout (slower, thorough)
b) No, repo-scout (faster)
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", "1b 2c", or just tell me naturally)Wait for response. Parse naturally — user may reply terse ("1a 2b") or ramble via voice.
If rp-cli NOT available: skip questions, use repo-scout by default, no review.
检查:
which rp-cli >/dev/null 2>&1如果可用,输出以下文本(请勿使用AskUserQuestion工具):
规划前的快速设置:
1. **调研方式** — 是否使用RepoPrompt获取更深入的上下文信息?
a) 是,使用context-scout(速度慢,更全面)
b) 否,使用repo-scout(速度快)
2. **审核** — 之后是否进行Carmack级别的审核?
a) 是,使用RepoPrompt聊天
b) 是,导出至外部大语言模型(ChatGPT、Claude网页版)
c) 否
(回复格式:"1a 2a"、"1b 2c",或自然表述即可)等待回复。支持自然解析——用户可能简短回复(如"1a 2b"),也可能通过语音长篇表述。
若rp-cli不可用:跳过设置问题,默认使用repo-scout,不进行审核。
Workflow
工作流
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:
- Option 2a: run after Step 4, fix issues until it passes
/flow:plan-review - Option 2b: run with export mode after Step 4
/flow:plan-review
阅读steps.md并按顺序执行每一步。步骤包括通过Task工具并行运行调研子Agent。
如果用户选择审核:
- 选项2a:在第4步后运行,修复问题直至审核通过
/flow:plan-review - 选项2b:在第4步后以导出模式运行
/flow:plan-review
Examples
示例
Read examples.md for plan structure examples.
阅读examples.md查看计划结构示例。
Output
输出
- Standard:
plans/<slug>.md - Beads: epic/tasks/subtasks in Beads (no file written)
- 标准输出:
plans/<slug>.md - Beads相关:在Beads中创建史诗/任务/子任务(不生成文件)
Output rules
输出规则
- Only write the plan file (or create Beads epic)
- No code changes
- 仅生成计划文件(或在Beads中创建史诗)
- 不修改代码