Turn feature requests into documented plans, revise them through discussion, and carry out implementation with progress tracking. Frontend work includes checking for a UI design and arranging design work when needed.
用于新增功能开发的命令，支持完整的开发流程和工具集成
Review the instructions the agent will receive before you install.
$ARGUMENTS
每次收到用户输入时，首先进行类型判断并明确告知用户：
判断标准：
需求规划类型: 用户提出新功能需求、项目构想或需要制定计划
讨论迭代类型: 用户要求继续讨论、修改或完善已有规划
执行实施类型: 用户确认规划完成，要求开始具体实施工作
触发条件: 识别为功能需求输入
执行动作:
启用 Planner Agent
生成详细的 markdown 规划文档
将文档存储至 ./.claude/plan 目录，并以 plan/xxx.md 的格式命名
包含：目标定义、功能分解、实施步骤、验收标准
触发条件: 用户要求继续讨论或修改规划
执行动作:
检索并分析上次生成的规划文件
识别用户反馈和确认内容
启用 Planner Agent
生成详细的 markdown 规划文档
建立一个新的文档，比如上一次是 plan/xxx.md，那么这次就是 plan/xxx-1.md，如果上一次是 plan/xxx-1.md，那么这次就是 plan/xxx-2.md，以此类推
重新组织待实施任务优先级
触发条件: 用户确认规划完成，要求开始执行
执行动作:
按规划文档顺序启动任务执行
每个子任务开始前进行任务类型识别
前端任务特殊处理:
检查是否存在可用 UI 设计
如无设计方案，must use UI-UX-Designer Agent
完成 UI 设计后再进行开发实施
每次交互必须首先说明: "我判断此次操作类型为：[具体类型]"
类型判断必须准确且明确传达给用户
严格按照文档化规划执行
子任务启动前必须明确任务性质和依赖关系
前端任务必须确保 UI 设计完整性
维护任务完成状态跟踪
及时更新规划文档状态
确保用户对进度的可见性
类型判断准确性: 每次交互开始的类型识别必须准确
文档一致性: 规划文档与实际执行保持同步
依赖关系管理: 特别关注前端任务的 UI 设计依赖
用户沟通透明: 所有判断和动作都要明确告知用户
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set up or update BMad-Method V6 in a project, detect older installations, fix a known output folder issue, and adjust Git ignore rules, with guidance on what to do next.
Install or update BMad-Method (V6) in a project after checking existing installations. The skill also fixes a known output-folder issue, updates Git ignore rules, and provides next steps for using the installed workflows.
Guide new feature work from requirements and planning through revisions and implementation. Create Markdown plans with acceptance criteria, track progress, and ensure frontend tasks have a UI design before development begins.
Find merged or inactive Git branches, preview cleanup candidates, and delete selected branches after confirmation. Choose a comparison branch, protect important branches with configurable rules, and optionally include remote branches.
Find Git branches that have been merged or inactive for a chosen period. Preview cleanup candidates, exclude protected branches, and delete local or remote branches using a selected base branch and confirmation options.
Analyze Git changes and generate Conventional Commits messages, a standard format that labels each change by type. Suggest separate commits for unrelated work, then stage files and commit as needed, using Git alone.