harness-engineering-mcp

Use 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", "提速".

代码重构 / 整理。任何重构必须先有覆盖待重构区域的测试网；分步原子 commit；每步 绿测，不允许"大爆炸式重构"。性能/行为变更属于 perf-flow / dev-flow，不在此范围。 Use when refactoring code, cleaning up tech debt, or restructuring without behavior change. Voice triggers: "重构", "整理代码", "/refactor-flow".

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

End-to-end workflow that writes Chinese WeChat tech articles from either the latest tech news or a user-provided custom topic, with source verification, readable technical depth, and ready-to-paste inline HTML. Use when asked to write a WeChat article, custom topic tech post, AI weekly, 科技新闻 / 科技周报, 公众号, 微信文章, or AI 周报.

按 PRD/需求文档实现后端功能（前端由他人或 Mock 消费）。后端视角的契约优先模式： 先产出 API_CONTRACT.md 与前端 owner 达成合同，再进入实现。覆盖鉴权、事务、回归、 迁移、安全审计，带 4 个强制人工卡点 + 1 个契约交付卡点。 Use when PRD is provided and only backend changes are needed. Voice triggers: "需求文档 后端", "PRD 后端", "接后端需求".

按 PRD/需求文档实现前端功能（后端接口已就绪或由他人开发）。从需求澄清到上线复盘全流程， 覆盖契约对齐、项目勘察、方案评审、切片验证、并行铺开、QA、上线、复盘 10 个阶段， 带 4 个强制人工卡点。 Use when PRD/需求文档 is provided and only frontend changes are needed. Voice triggers: "需求文档 前端", "PRD 前端", "接前端需求".

按 PRD 完整实现前后端并联调。契约自治模式：自己写第一版 API 合同，阶段 5 切片 必须真实端到端（禁 mock），阶段 6 并行三路派发（backend-agent / frontend-agent / test-agent）。4 个强制卡点。 Use when PRD is provided and both frontend and backend need to be implemented. Voice triggers: "需求文档 全栈", "PRD 全栈", "前后端都做".

双项目模式的完整需求开发流程（10 阶段）。从 PM 给的原型项目接手开始，到上线复盘结束，全链路自动化执行，关键节点强制人工卡点。Use when asked to "接手新需求", "双项目开发", "完整开发流程", "/dev-flow-full", or when user has a prototype project from PM and needs to implement features in a different target project. Voice triggers: "接手需求", "完整流程", "双项目模式".

一句话后端需求（如"加个 X 字段查询"）。轻量级流程：补迷你 PRD + 必出 API 契约 与 IMPACT_ANALYSIS。涉及 DB 强制升级到 dev-flow-doc-be；预估超 8 工时同样升级。 Use when only a one-liner casual backend request is provided. Voice triggers: "一句话 后端", "后端小改", "加个字段".

一句话前端需求（如"列表加个状态筛选"）。轻量级流程：先用 office-hours 把一句话补成 迷你 PRD，再走 doc-fe 简化版（少 1 个 explore subagent）。规模门槛若超 8 工时强制升级 到 doc-fe，禁止"看似简单一句话"无声变成大工程。 Use when only a one-liner casual frontend request is provided. Voice triggers: "一句话 前端", "前端小改", "顺手加个 X".

一句话全栈需求。预估超 8 工时直接强制升级到 dev-flow-doc-full；否则走 oneliner-fe + oneliner-be 的并集，并在阶段 2 必出端到端时序图。任何 DB 改动一律升级。 Use when only a one-liner casual full-stack request is provided. Voice triggers: "一句话 全栈", "顺手前后端都改一下".

PM 给了可运行的参考项目 A，只在 B 项目里实现后端。基于 dev-flow-full 裁剪： 阶段 1 跳过前端 subagent 但强化网络请求抓取，阶段 3 后端横切为主，阶段 6 只派 backend-agent + test-agent。额外追加"契约交付"卡点。 Use when a reference/prototype project is provided and only backend is needed in target project. Voice triggers: "原型 后端", "参考项目 后端".

PM 给了可运行的参考项目 A，只在 B 项目里实现前端。基于 dev-flow-full 裁剪： 阶段 1 跳过后端探索 subagent，阶段 3 跳过后端横切，阶段 6 只派 frontend-agent + test-agent。保留 A 项目只读原则与 4 个硬卡点。 Use when a reference/prototype project is provided and only frontend is needed in target project. Voice triggers: "原型 前端", "参考项目 前端".

双项目开发流程的"开发实现"阶段（阶段 3-7）。在目标项目 B 中勘察规范、设计方案、做垂直切片验证、并行派多个 subagent 实现功能、完成自查。需要 _requirements/[feature]/ 已有需求文档作为前置。Use when asked to "开始开发", "实现需求", "进入开发阶段", "/dev-implement", or when user has requirements documented and wants to implement in target project. Voice triggers: "开始开发", "实现需求".

双项目开发流程的"上线复盘"阶段（阶段 8-10）。包含 PM 验收材料准备、上线、监控、知识库沉淀。需要功能已开发完成且通过自查。Use when asked to "PM验收", "准备上线", "上线复盘", "/dev-ship-retro", or when feature is developed and ready for PM acceptance and deployment. Voice triggers: "上线复盘", "PM验收".

双项目开发流程的"理解需求"阶段（阶段 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: "理解需求", "梳理业务".

接入第三方服务（支付 / IM / OAuth / 短信 / OSS 等）。强制输出 Vendor 适配层， 应用层只用领域接口，不直接调用 SDK；强制密钥/Webhook 安全审计；强制沙箱 + 失败 重放剧本。 Use when integrating with third-party services or SDKs. Voice triggers: "接第三方", "/third-party-flow", "接入 SDK", "对接".