메뉴
双项目开发流程的"理解需求"阶段（阶段 0-2）。在 PM 给的原型项目中只读探索，产出抽象化的需求文档，并通过 PM 沟通循环确保需求清晰。Use when asked to "理解需求", "梳理业务", "探索原型项目", "/dev-understand", or when user has a prototype project from PM but doesn't yet have clear requirements documented. Voice triggers: "理解需求", "梳理业务".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | dev-understand |
| description | 双项目开发流程的"理解需求"阶段（阶段 0-2）。在 PM 给的原型项目中只读探索，产出抽象化的需求文档，并通过 PM 沟通循环确保需求清晰。Use when asked to "理解需求", "梳理业务", "探索原型项目", "/dev-understand", or when user has a prototype project from PM but doesn't yet have clear requirements documented. Voice triggers: "理解需求", "梳理业务". |
完整开发流程的前置阶段。当 PM 给了原型项目，需要：
/dev-implement）准备好需求知识库/freeze + SwitchMode 到 plan 模式AskQuestion 阻塞等待使用 AskQuestion 工具一次性收集（用户消息已含则跳过）：
supplier-batch-approve）写入 ~/Projects/_requirements/[feature]/META.md。
~/Projects/_requirements/[feature]/ 目录META.md~/Projects/_requirements/_lessons.md（如存在）作为背景move_agent_to_root 切到 A 项目/freeze + SwitchMode 到 planbrowser_snapshot + browser_take_screenshotbrowser_network_requests 抓 APIbrowser_console_messages 查报错~/Projects/_requirements/[feature]/：
BUSINESS_FLOW.md（业务流程，含截图、mermaid，无代码）API_CONTRACT.md（接口契约，业务语言）DATA_MODEL.md（数据模型，通用 ER）ENV_NOTES.md（A 的运行环境特征）文档模板位置：~/.cursor/skills/dev-flow-full/templates/（统一维护，避免重复）：
META.md - 需求元信息BUSINESS_FLOW.md - 业务流程API_CONTRACT.md - 接口契约DATA_MODEL.md - 数据模型_lessons.md - 经验沉淀（已存在则追加）读取模板后填充实际内容输出到 ~/Projects/_requirements/[feature]/。
gstack-office-hours 视角挑战需求文档questions-for-pm.md：
AskQuestion 阻塞等待：
prompt: "需求文档已生成，请查看 questions-for-pm.md。请选择："
options:
- "已和 PM 沟通，提供答复（粘贴在下条消息）"
- "需求清楚无疑问，结束理解阶段"
- "需要重新探索 A 项目某些细节"
pm-answers.mdAskQuestion 询问"还有疑问吗？"输出本阶段总结：
✅ 理解需求阶段完成
📁 知识库位置：~/Projects/_requirements/[feature]/
📄 产出文档：
- META.md
- BUSINESS_FLOW.md
- API_CONTRACT.md
- DATA_MODEL.md
- ENV_NOTES.md
- questions-for-pm.md
- pm-answers.md（如有）
下一步建议：使用 /dev-implement 进入开发实现阶段
/dev-implement/dev-flow-fullUse whenever an AI agent executes a multi-step task to save tokens, parallelize tool calls, cache prompts, and keep replies under 2000 chars
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Bug 修复全流程。强制 /investigate 找根因，禁止"看似修好就交付"。/freeze 锁定文件 防止顺手"清理"无关代码；先写复现失败测试再写修复。 Use when reporting bugs, errors, 500s, stack traces, or "it stopped working" type issues. Voice triggers: "修 bug", "/bugfix-flow", "bugfix".
开发组合拳总入口。根据输入形式（需求文档 / 原型项目 / 一句话）× 开发范围（前端 / 后端 / 全栈） × 修饰符（带设计稿 / 数据库迁移 / 只联调 等）自动路由到正确的子 skill。同时覆盖 4 类非需求任务： bugfix / 重构 / 性能优化 / 第三方接入。 Use when asked to "接需求", "开始开发", "/dev-flow", "组合拳", "dev flow", or whenever the user hands over a development task and you need to decide which workflow skill to invoke. Voice triggers: "接需求", "开始开发", "组合拳". Note: 阶段切片型 skills（/dev-understand、/dev-implement、/dev-ship-retro）按阶段拆分， 与本路由按场景类型拆分的子 skill 互补；当用户明确说"只做某阶段"时优先匹配那些 skill。
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
性能优化全流程。先 benchmark 立基线 → profile 找瓶颈 → 单一变量优化 → 再 benchmark 对比。禁止"凭感觉优化"，每个改动必须带数据证明。 Use when optimizing for performance, page speed, web vitals, or backend latency. Voice triggers: "性能优化", "/perf-flow", "提速".