Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BlueprintOS/analysis-to-delivery --skill to-prdgit clone --depth 1 https://github.com/BlueprintOS/analysis-to-deliveryWrote 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/to-prd)<a href="https://agentmods.dev/skills/blueprintos/analysis-to-delivery/to-prd"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/to-prd/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/to-prd"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/to-prd.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.00060 | $0.01166 |
| Opus 5 | $0.00030 | $0.00583 |
| Sonnet 5 | $0.00012 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
to-prd 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 10d 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.
What it actually says
To-PRD — 产品需求文档生成
Contract
- 输入: 已签字的 BRD、合规评审、测试用例、字段对齐分析
- 输出:
05-产品需求文档 PRD.md、可选05-PRD.html、可选05-PRD.docx、可选 Figma 设计文档 - 门控: PRD 必备章节齐全;验收标准已签字;字段映射与知识库核对
- Required rules:
stage-gate,no-field-guessing,doc-numbering,goal-boundary - Required paths:
knowledge-path,doc-naming-path - 下一步:
/dev-design
适用场景
- BRD + 合规评审 + 测试用例已通过
- 需要把业务需求翻译成产品视角
- 设计/开发团队需要可执行的需求输入
流程步骤
1. 加载模板
templates/PRD.md(8 节必备章节)
2. 三格式输出
| 格式 | 用途 | 生成方式 |
|---|---|---|
| Markdown | 源文件、版本管理 | 手工编写 |
| HTML | 浏览器阅读、分享 | pandoc + scripts/postprocess_prd_html.py |
| DOCX | Word 阅读、批注 | pandoc |
3. 填充内容
按 PRD 模板逐节生成:
| 章节 | 内容来源 |
|---|---|
| 一、产品概述 | BRD §1 |
| 二、用户故事 | BRD §2 角色 + 业务场景 |
| 三、功能需求 | BRD §4 + 测试用例(用作验收) |
| 四、非功能需求 | BRD §7 |
| 五、数据需求 | BRD §5 + 字段对齐分析 |
| 六、合规要求 | 04-合规评审.md |
| 七、验收标准 | 07-测试用例设计.md |
| 八、风险与依赖 | BRD §8 |
4. 关键纪律
- 字段名必须与知识库定义一致
- 业务同义不同名需在 PRD 注释中显式标注("业务上称为 X = 知识库定义的 Y")
- 严禁自行发明字段
- 用户故事格式:
As an <actor>, I want a <feature>, so that <benefit>
5. Figma 设计文档引用(如适用)
- 简单需求(加字段/调规则)→ 跳过
- 中等需求(新增功能/页面改造)→ 需要 Figma 文档
- 复杂需求(跨模块/多角色/算法介入)→ 必须 Figma 文档
输出
05-PRD.md(Markdown 源)05-PRD.html(可选,后处理)05-PRD.docx(可选)Figma设计文档_{功能名}_{端}.md(可选,不受编号约束)
调用的 rule
rules/no-field-guessing— 字段名必须查知识库rules/doc-numbering— 文档编号 05
结束条件
- PRD 8 个必备章节齐
- §七 验收标准签字
- 字段映射表通过
field-alignment-check.py - 三格式产物存在(可选 HTML/DOCX)
- 用户签字进入
/dev-design
反模式
- ❌ PRD 8 章节缺一 —
prd-check.py --strict直接 fail(一~八必须齐) - ❌ §七 验收标准未被白名单签字 — 必须 4 句之一(我已全部确认,可以进入下一步 / 确认通过,进入 dev-design / 全部完成,继续 / approved, proceed to next stage)
- ❌ §二 用户故事只列 P0 — P0/P1/P2 三档必须都有,否则后续排期无法决策
- ❌ §五 数据需求不引用 03-数据模型设计 — 必须明确"参考 03-数据模型设计.md §X"
- ❌ §六 合规要求不引用 04-合规评审 — 必须明确"参考 04-合规评审.md §X"
- ❌ §三 功能需求跳过异常处理 — 3.1.X 异常处理表格必填(异常/提示/处理 三列)
- ❌ §八 风险与依赖无缓解措施 — 每条风险必须配缓解 + 责任方
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.
- 10d ago First seen · 98 lines · 60 tokens per session scan A c321ef688c2d
to-prd is a skill published in the GitHub repository BlueprintOS/analysis-to-delivery (26 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,166 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
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…
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.…
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…
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.
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.