analysis-delivery-workflow
starsforks
How to install analysis-delivery-workflow?
blueprintos/analysis-to-delivery/analysis-delivery-workflow
$npx -y skills add BlueprintOS/analysis-to-delivery --skill analysis-delivery-workflow严守 9 阶段流程(分析-设计)— 适合新手/复杂项目,按顺序自动调 9 个 user-invoked skill。希望按完整结构化流程、逐步推进且不需每步自行决策时调用本编排。
SKILL.md
| 1 | # Analysis to Delivery Workflow — 9 阶段流程编排 |
| 2 | |
| 3 | ## Contract |
| 4 | |
| 5 | - 输入: 项目目标、领域、技术栈,可选既有 `paths/*.md` |
| 6 | - 输出: 9 阶段交付链,终点为 `HANDOVER.md` |
| 7 | - 门控: 每阶段间 stage-gate 签字;`task-confirm-check.py --strict` 用于 2→3;QA P0=0 才能 8→9 |
| 8 | - Required rules: `stage-gate`, `doc-numbering`, `context-pointer`, `goal-boundary` |
| 9 | - Required paths: `knowledge-path`, `tech-stack-path`, `compliance-path`, `doc-naming-path` |
| 10 | - 下一步: 先 `/setup-analysis-delivery`,再按顺序走 9 阶段;阶段 9 之后可选 `/using-superpowers` |
| 11 | |
| 12 | ## 适用场景 |
| 13 | |
| 14 | - 复杂项目(中等+) |
| 15 | - 新手第一次用 |
| 16 | - 严守流程纪律,避免跳步 |
| 17 | |
| 18 | ## 9 阶段(按顺序触发) |
| 19 | |
| 20 | | # | 阶段 | 调用的 skill | 产出 | |
| 21 | |---|---|---|---| |
| 22 | | 1 | 项目配置 | `/setup-analysis-delivery` | 4 个 `*-path.md` | |
| 23 | | 2 | 需求澄清 | `/grill-task` | TASK_CONFIRM + 字段对齐 | |
| 24 | | 3 | BRD | `/to-brd` | 01-BRD + 流程图 | |
| 25 | | 4 | 合规评审 | `/compliance-review` | 04-合规评审 | |
| 26 | | 5 | 测试用例 | `/test-case-design` | 07-测试用例 | |
| 27 | | 6 | PRD | `/to-prd` | 05-PRD(三格式) | |
| 28 | | 7 | 开发设计 | `/dev-design` | AGENTS + FSD + 数据模型 + 开发设计 + 回测 + 复盘 | |
| 29 | | 8 | QA 审计 | `/qa-audit` | 09-QA 审计报告 | |
| 30 | | 9 | 交接 | `/handoff` | HANDOVER.md | |
| 31 | |
| 32 | ## 衔接 superpowers 实施(阶段 9 之后) |
| 33 | |
| 34 | **设计交接完成后,推荐进入 `/using-superpowers` 走 5 步实施**: |
| 35 | |
| 36 | ``` |
| 37 | brainstorming → design-an-interface → domain-modeling → writing-plans → tdd → executing-plans → verification-before-completion |
| 38 | ``` |
| 39 | |
| 40 | | 实施步骤 | 产出 | |
| 41 | |---|---| |
| 42 | | brainstorming | 设计稿 | |
| 43 | | design-an-interface | 接口契约 | |
| 44 | | domain-modeling | 领域模型 | |
| 45 | | writing-plans | ≤ 2h 子任务列表 | |
| 46 | | tdd | RED → GREEN → REFACTOR | |
| 47 | | executing-plans | 逐步开发 + commit | |
| 48 | | verification-before-completion | 完成前验证 | |
| 49 | |
| 50 | ## 门控(贯穿) |
| 51 | |
| 52 | 每阶段必签字才能进入下一阶段。详细见 `disciplines/stage-gate` 3 层门控: |
| 53 | |
| 54 | - **第 1 层**:9 阶段之间 → 用户签字 |
| 55 | - **第 2 层**:实施子流程之间 → 用户 + Claude 双向 |
| 56 | - **第 3 层**:每个 writing-plans 子任务 → 测试 + 用户抽查 |
| 57 | |
| 58 | ## 关键纪律 |
| 59 | |
| 60 | - **严禁自动推进**：本编排"按顺序触发"9 个 skill，但每阶段产物必须经用户显式签字（白名单话术）后才能进入下一阶段。LLM 不得自行解释"OK""继续""好"等模糊回复为签字。 |
| 61 | - 严禁跳阶段(从 1 跳 3 / 从 5 跳 7) |
| 62 | - 每阶段产物必须签字 |
| 63 | - HARD GATE:阶段 7 设计回测 ❌ 禁入阶段 8 |
| 64 | - HARD GATE:阶段 8 QA 审计 P0>0 禁入阶段 9 |
| 65 | |
| 66 | ## 2→3 门控（2026-06-24 强化） |
| 67 | |
| 68 | 阶段 2 → 阶段 3 之间，必须同时满足： |
| 69 | |
| 70 | 1. TASK_CONFIRM 状态 = ✅ |
| 71 | 2. REVIEW 文档中 ❓=0 且 🔴=0 |
| 72 | 3. 用户白名单话术签字（详见 `skills/disciplines/stage-gate/SKILL.md`） |
| 73 | |
| 74 | 详见 `scripts/task-confirm-check.py` 自动化校验。 |
| 75 | |
| 76 | ## 状态文件(plan §P1-3,v4.0.0) |
| 77 | |
| 78 | 每个项目根维护 `.analysis-delivery-state.json`(加入 `.gitignore`),5 个子命令: |
| 79 | |
| 80 | ```bash |
| 81 | # 初始化(项目级) |
| 82 | python3 scripts/analysis-state.py init --project <name> [--project-root .] [--force] |
| 83 | |
| 84 | # 记录 gate 脚本结果(pass/fail 会自动 +1 拦截次数) |
| 85 | python3 scripts/analysis-state.py record-gate --stage N --script <gate> --result pass|fail |
| 86 | |
| 87 | # 记录阶段签字(只接受 4 句白名单之一,其他一律 reject) |
| 88 | python3 scripts/analysis-state.py signoff --stage N --text "我已全部确认,可以进入下一步" |
| 89 | |
| 90 | # 查看当前状态(9 阶段进度 + last_gate + errors) |
| 91 | python3 scripts/analysis-state.py status |
| 92 | |
| 93 | # 5 项度量指标(total_gates / total_signoffs / 拦截次数 / 重试次数 / 阶段用时) |
| 94 | python3 scripts/analysis-state.py metrics [--json] |
| 95 | ``` |
| 96 | |
| 97 | **白名单话术(只 4 句)**: |
| 98 | - "我已全部确认,可以进入下一步" |
| 99 | - "确认通过" |
| 100 | - "全部完成,继续" |
| 101 | - "approved, proceed to next stage" |
| 102 | |
| 103 | ❌ "OK / 好 / 继续 / 确认" 一律视为非签字。 |
| 104 | |
| 105 | **中断恢复**:状态文件在 `.gitignore`,存在本地;下次开会话时跑 `status` 即可看到当前阶段、已签字阶段、错误计数。 |
| 106 | |
| 107 | ## 调用的 rule |
| 108 | |
| 109 | - `rules/stage-gate` — 3 层门控 |
| 110 | - `rules/no-field-guessing` — 字段名 |
| 111 | - `rules/doc-numbering` — 文档编号 |
| 112 | |
| 113 | ## 结束条件 |
| 114 | |
| 115 | - [ ] 9 阶段全部签字 |
| 116 | - [ ] HANDOVER.md 已生成 |
| 117 | - [ ] 已交接给编码 skill 或开发团队 |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
