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/miniidealab/openlogos/prd-writernpx skills add miniidealab/openlogos --skill prd-writergit clone --depth 1 https://github.com/miniidealab/openlogosWrote 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/miniidealab/openlogos/prd-writer)<a href="https://agentmods.dev/skills/miniidealab/openlogos/prd-writer"><img src="https://agentmods.dev/badge/skills/miniidealab/openlogos/prd-writer.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.00000 | $0.02450 |
| Opus 5 | $0.00000 | $0.01225 |
| Sonnet 5 | $0.00000 | $0.00490 |
| Haiku 4.5 | $0.00000 | $0.00245 |
Grade A, and why
prd-writer 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: PRD Writer
辅助撰写场景驱动的需求文档——从用户痛点出发，识别核心业务场景，为每个场景定义 GIVEN/WHEN/THEN 验收条件。场景编号将贯穿后续所有阶段。
触发条件
- 用户要求写需求文档、产品需求或 PRD
- 用户讨论产品定位、目标用户、功能需求
- 用户提到 "Phase 1"、"需求层"、"WHY"
- 当前处于项目的需求分析阶段
核心能力
- 引导用户梳理产品定位和目标用户
- 提炼用户痛点，建立因果链
- 从痛点中识别和定义业务场景（分配
S01,S02... 编号） - 为每个场景编写 GIVEN/WHEN/THEN 验收条件
- 排列场景优先级
- 识别约束和"不做"清单
- 生成符合 OpenLogos 规范的场景驱动需求文档
执行步骤
Step 1: 理解产品定位
与用户确认以下核心问题（如果信息不足则主动追问）：
- 一句话定位：这个产品是什么？为谁？解决什么问题？
- 目标用户画像：具体到可以描述一个真实的人
- 核心目标：产品要达成什么，用什么指标衡量成功
Step 2: 提炼用户痛点
引导用户从以下维度梳理痛点：
- 用户当前是怎么做的？（现状）
- 做的过程中遇到什么困难？（痛点）
- 困难导致了什么后果？（影响）
- 用户期望怎么被解决？（期望）
每条痛点必须有因果链：因为 [原因] → 导致 [痛点] → 造成 [后果]
为每条痛点分配编号（P01, P02...），便于场景追溯。
Step 3: 识别和定义场景
场景是贯穿整个研发周期的锚。 这一步至关重要。
从痛点和需求中提取业务场景。每个场景是一个完整的用户操作路径：
- 谁在什么情况下触发
- 经过什么步骤（必须包含多个交互环节，不能只是单个 API 调用）
- 达到什么业务成果（用户可感知的价值）
为每个场景分配全局唯一编号（S01, S02...），这个编号将一路带到 Phase 2 和 Phase 3。
输出场景清单表：
| 编号 | 场景名称 | 触发条件 | 关联痛点 | 优先级 |
|------|---------|---------|---------|--------|
| S01 | 邮箱注册 | 新用户首次访问 | P01 | P0 |
| S02 | 密码登录 | 已注册用户返回 | P01 | P0 |
| S03 | 忘记密码 | 用户无法登录 | P02 | P1 |
场景粒度自检（必须通过）
生成场景清单后，运行以下 4 项测试。任何一项不通过，必须重新组织场景后再继续。
- 单 API 测试：如果一个场景只需要调用 1 个 API 就能完成，它不是场景——它是一个操作。应将其合并到更大的场景中。
- CRUD 测试：如果场景清单中出现"创建X"、"查询X"、"更新X"、"删除X"作为 4 个独立场景，说明粒度过细。应按用户目标重新组织（例如用"负责人规划周任务"代替"创建任务"+"分配任务"+"更新任务"+"删除任务"）。
- 业务价值测试：用一句话描述场景完成后用户获得的价值。如果答案只是"数据被写入/读取/删除了"，说明缺少真正的业务目标——应合并到有明确目标的场景中。
- 步骤数测试：一个场景的主路径至少包含 3 个用户可感知的步骤。少于 3 个说明粒度过细。
❌ 反模式：一个 API = 一个场景
| S01 | 创建任务 | 用户点击"新建" |
| S02 | 获取任务列表 | 用户打开页面 |
| S03 | 更新任务 | 用户编辑任务 |
| S04 | 删除任务 | 用户删除任务 |
→ 这是 API 清单，不是场景清单！
✅ 正确：按业务目标组织场景
| S01 | 团队负责人规划周任务 | 负责人登录 → 创建多个任务 → 设置优先级和截止日期 → 分配给成员 → 成员收到通知 |
| S02 | 开发者完成并交付任务 | 开发者查看待办 → 更新进度 → 标记完成 → 负责人收到通知并审核 |
| S03 | 负责人查看项目进度 | 负责人打开看板 → 按状态/成员筛选 → 导出周报 |
Step 4: 编写场景验收条件
为每个 P0 和 P1 场景编写验收条件：
### S01: 邮箱注册
- **触发条件**：新用户首次访问，点击注册
- **用户价值**：快速创建账号开始使用产品（← P01）
- **优先级**：P0
- **主路径**：用户填写邮箱和密码，提交后收到验证邮件，点击验证完成注册
#### 验收条件
##### 正常：完整注册流程
- **GIVEN** 用户未注册过，且在注册页面
- **WHEN** 用户填写有效邮箱和密码（≥8位），点击「注册」
- **THEN** 系统创建账号，发送验证邮件，页面显示「请查收验证邮件」
##### 异常：邮箱已注册
- **GIVEN** 邮箱 [email protected] 已注册
- **WHEN** 用户使用 [email protected] 尝试注册
- **THEN** 显示「该邮箱已注册，请直接登录」，不发送任何邮件
##### 异常：密码不符合要求
- **GIVEN** 用户在注册页面
- **WHEN** 用户填写有效邮箱但密码少于 8 位，点击「注册」
- **THEN** 显示「密码至少 8 位」，不提交请求
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 · 199 lines · 0 tokens per session scan A f10f5d873c91
prd-writer is a skill published in the GitHub repository miniidealab/openlogos (71 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,450 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…