Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/BlueprintOS/analysis-to-deliverynpx agentmods add skills/blueprintos/analysis-to-delivery/analysis-delivery-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/blueprintos/analysis-to-delivery/analysis-delivery-workflow)<a href="https://agentmods.dev/skills/blueprintos/analysis-to-delivery/analysis-delivery-workflow"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/analysis-delivery-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/blueprintos/analysis-to-delivery/analysis-delivery-workflow"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/analysis-delivery-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00066 | $0.01497 |
| Opus 5 | $0.00033 | $0.00749 |
| Sonnet 5 | $0.00013 | $0.00299 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
analysis-delivery-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analysis to Delivery Workflow — 9 阶段流程编排
Contract
- 输入: 项目目标、领域、技术栈,可选既有
paths/*.md - 输出: 9 阶段交付链,终点为
HANDOVER.md - 门控: 每阶段间 stage-gate 签字;
task-confirm-check.py --strict用于 2→3;QA P0=0 才能 8→9 - Required rules:
stage-gate,doc-numbering,context-pointer,goal-boundary - Required paths:
knowledge-path,tech-stack-path,compliance-path,doc-naming-path - 下一步: 先
/setup-analysis-delivery,再按顺序走 9 阶段;阶段 9 之后可选/using-superpowers
适用场景
- 复杂项目(中等+)
- 新手第一次用
- 严守流程纪律,避免跳步
9 阶段(按顺序触发)
| # | 阶段 | 调用的 skill | 产出 |
|---|---|---|---|
| 1 | 项目配置 | /setup-analysis-delivery |
4 个 *-path.md |
| 2 | 需求澄清 | /grill-task |
TASK_CONFIRM + 字段对齐 |
| 3 | BRD | /to-brd |
01-BRD + 流程图 |
| 4 | 合规评审 | /compliance-review |
04-合规评审 |
| 5 | 测试用例 | /test-case-design |
07-测试用例 |
| 6 | PRD | /to-prd |
05-PRD(三格式) |
| 7 | 开发设计 | /dev-design |
AGENTS + FSD + 数据模型 + 开发设计 + 回测 + 复盘 |
| 8 | QA 审计 | /qa-audit |
09-QA 审计报告 |
| 9 | 交接 | /handoff |
HANDOVER.md |
衔接 superpowers 实施(阶段 9 之后)
设计交接完成后,推荐进入 /using-superpowers 走 5 步实施:
brainstorming → design-an-interface → domain-modeling → writing-plans → tdd → executing-plans → verification-before-completion
| 实施步骤 | 产出 |
|---|---|
| brainstorming | 设计稿 |
| design-an-interface | 接口契约 |
| domain-modeling | 领域模型 |
| writing-plans | ≤ 2h 子任务列表 |
| tdd | RED → GREEN → REFACTOR |
| executing-plans | 逐步开发 + commit |
| verification-before-completion | 完成前验证 |
门控(贯穿)
每阶段必签字才能进入下一阶段。详细见 disciplines/stage-gate 3 层门控:
- 第 1 层:9 阶段之间 → 用户签字
- 第 2 层:实施子流程之间 → 用户 + Claude 双向
- 第 3 层:每个 writing-plans 子任务 → 测试 + 用户抽查
关键纪律
- 严禁自动推进：本编排"按顺序触发"9 个 skill，但每阶段产物必须经用户显式签字（白名单话术）后才能进入下一阶段。LLM 不得自行解释"OK""继续""好"等模糊回复为签字。
- 严禁跳阶段(从 1 跳 3 / 从 5 跳 7)
- 每阶段产物必须签字
- HARD GATE:阶段 7 设计回测 ❌ 禁入阶段 8
- HARD GATE:阶段 8 QA 审计 P0>0 禁入阶段 9
2→3 门控（2026-06-24 强化）
阶段 2 → 阶段 3 之间，必须同时满足：
- TASK_CONFIRM 状态 = ✅
- REVIEW 文档中 ❓=0 且 🔴=0
- 用户白名单话术签字（详见
skills/disciplines/stage-gate/SKILL.md）
详见 scripts/task-confirm-check.py 自动化校验。
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 126 lines · 66 tokens per session scan A 2a6281ca9971
analysis-delivery-workflow is a skill published in the GitHub repository BlueprintOS/analysis-to-delivery (26 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 1,497 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.