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 agentmods add skills/echovic/boss-skill/prd-writingnpx skills add echoVic/boss-skill --skill prd-writinggit clone --depth 1 https://github.com/echoVic/boss-skillWrote 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/echovic/boss-skill/prd-writing)<a href="https://agentmods.dev/skills/echovic/boss-skill/prd-writing"><img src="https://agentmods.dev/badge/skills/echovic/boss-skill/prd-writing.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.02015 |
| Opus 5 | $0.00017 | $0.01007 |
| Sonnet 5 | $0.00007 | $0.00403 |
| Haiku 4.5 | $0.00003 | $0.00201 |
Grade A, and why
pm/prd-writing 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 5d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD 编写指南
适用场景
完成需求穿透和调研分析后，需要输出一份完整的产品需求文档(PRD)，供设计师、开发者、测试人员使用。
PRD 标准结构
1. 概述
- 功能名称：[清晰简洁的名称]
- 版本：1.0
- 日期：[当前日期]
- 作者：PM Agent
摘要
下游 Agent 请优先阅读本节，需要细节时再查阅完整文档。
- 核心目标：[用一句话描述]
- 目标用户：[主要用户群体]
- 关键功能：[3-5 个最核心功能]
- 技术约束：[重要约束或偏好]
- 优先级：[MVP 范围说明]
2. 需求穿透分析（核心章节）
参见 pm/requirement-penetration skill 的输出要求。
3. 竞品调研
3.1 竞品分析
使用 WebSearch 搜索相关竞品：
| 竞品 | 核心功能 | 用户体验亮点 | 用户痛点 | 我们的机会 |
|---|---|---|---|---|
| [竞品 1] | [功能] | [亮点] | [痛点] | [机会] |
| [竞品 2] | [功能] | [亮点] | [痛点] | [机会] |
| [竞品 3] | [功能] | [亮点] | [痛点] | [机会] |
3.2 差异化策略
| 维度 | 竞品做法 | 我们的做法 | 差异化价值 |
|---|---|---|---|
| [维度 1] | [做法] | [做法] | [价值] |
| [维度 2] | [做法] | [做法] | [价值] |
4. 目标用户
用户画像 1：[名称]
- 基本特征：[年龄、职业、收入等]
- 行为特征：[使用习惯、偏好等]
- 核心需求：[最想解决的问题]
- 痛点场景：[具体的痛苦场景描述]
- 期望体验：[理想的体验是什么样]
用户旅程图
journey
title 用户完成核心任务的旅程
section 发现阶段
了解产品: 3: 用户
产生兴趣: 4: 用户
section 使用阶段
首次使用: 3: 用户
完成任务: 5: 用户
section 留存阶段
持续使用: 4: 用户
推荐他人: 5: 用户
5. 功能需求
FR-001：[需求标题]
- 需求描述：[清晰的需求描述]
- 用户价值：[这个功能给用户带来什么价值]
- 优先级：P0/P1/P2
- 需求来源：显性/隐性/潜在/惊喜
- 验收标准：
- AC-1：[可测试的标准 1]
- AC-2：[可测试的标准 2]
- 边界情况：
- [边界情况 1 及处理方式]
- [边界情况 2 及处理方式]
FR-002：[需求标题]
- 需求描述：[描述]
- 用户价值：[价值]
- 优先级：P1
- 需求来源：[来源]
- 验收标准：
- AC-1：[标准]
6. 非功能需求
NFR-001：性能需求
- 页面加载：首屏加载 < 2s，完整加载 < 3s
- 交互响应：用户操作响应 < 100ms
- API 响应：接口响应 < 200ms
NFR-002：体验需求
- 易用性：新用户无需教程即可完成核心任务
- 一致性：交互模式和视觉风格保持一致
- 容错性：操作可撤销，错误可恢复
NFR-003：安全需求
- 数据安全：敏感数据加密存储和传输
- 隐私保护：符合相关隐私法规
7. 用户故事
US-001：[故事标题]
- 作为 [用户类型]
- 我想要 [目标行为]
- 以便 [预期价值]
- 验收标准：
- [标准 1]
- [标准 2]
- 优先级：P0
US-002：[故事标题]
- 作为 [用户类型]
- 我想要 [目标行为]
- 以便 [预期价值]
- 验收标准：
- [标准]
- 优先级：P1
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.
- 5d ago First seen · 263 lines · 34 tokens per session scan A 601f3ae0d308
pm/prd-writing is a skill published in the GitHub repository echoVic/boss-skill (553 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 2,015 once invoked, about $0.0002 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
large-workspace-handling
To partition large workspaces (100+ files) into scoped subagent tasks when context is insufficient.
example-skill
Example skill template used for the CreateHub template. You should never use this skill directly as it is just a template made to be updated.
bmad-github-story-dev
Set up a git worktree/branch (or reuse the current one) and run BMAD dev-story end-to-end: auto-commits per task, PR creation, label updates. Use when the user invokes the SD menu code in bmad help, or asks to start implementing the next ready story, or asks to begin dev on a story.
bmad-github-story-sync
Reconcile GitHub state with BMAD files — detect merged PRs, mark stories done in sprint-status.yaml and story files, sync GitHub labels, and clean up worktrees and branches. Use when the user invokes the SS menu code in bmad help, or asks to sync BMAD with GitHub, or just merged a PR and wants BMAD updated.
bmad-github-story-create
Sync GitHub state then plan the next story end-to-end via the BMAD create-story flow. Detects blocking dependencies via GitHub labels and updates the GitHub issue label to ready. Use when the user invokes the SC menu code in bmad help, or asks to plan/create the next story, or asks to start the next BMAD story.
bmad-github-story-review
Run BMAD adversarial code review on the current story branch and push fixes. Does NOT mark the story done — the user merges the PR on GitHub. Use when the user invokes the SR menu code in bmad help, or asks to code-review the current story, or asks for an adversarial review of the open story PR.