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/yulin-bi/codeauto/to-prdnpx skills add Yulin-Bi/CodeAuto --skill to-prdgit clone --depth 1 https://github.com/Yulin-Bi/CodeAutoWhat 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.00050 | $0.00608 |
| Opus 5 | $0.00025 | $0.00304 |
| Sonnet 5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
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 yesterday.
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
此技能基于当前对话上下文和对代码库的理解来生成 PRD。不要追问用户——仅基于已有信息进行综合整理。
如果尚未配置好 backlog 后端和 triage 标签体系，请先运行 /setup-matt-pocock-skills。
流程
-
探索仓库，了解代码库当前状态（如果尚未做）。在整个 PRD 中使用项目的领域术语，并遵守相关区域的 ADR（架构决策记录）。
-
勾勒主要模块，识别需要新建或修改哪些模块来完成实现。积极寻找可以提取为"深度模块"（deep module）的机会——这类模块封装大量功能，提供简单、可测试且不易变动的接口。
与用户确认这些模块是否符合预期，以及用户希望对哪些模块编写测试。
-
按以下模板撰写 PRD，然后发布到项目 backlog。打上
needs-triage标签以便进入正常的三级流程。
问题陈述
从用户视角描述所面临的问题。
解决方案
从用户视角描述解决方案。
用户故事
一份长长的、编号的用户故事列表。每个用户故事的格式为：
- 作为 <角色>，我想要 <功能>，以便 <收益>
用户故事列表应尽可能详尽，覆盖该功能的各个方面。
实现决策
已做出的实现决策清单，可包括：
- 将要构建/修改的模块
- 这些模块将要修改的接口
- 来自开发者的技术澄清
- 架构决策
- 数据库 Schema 变更
- API 契约
- 具体的交互方式
不要包含具体的文件路径或代码片段——它们可能很快就会过时。
测试决策
已做出的测试决策清单，包括：
- 好测试的标准（只测试外部行为，不测试实现细节）
- 哪些模块需要测试
- 测试的参考依据（即代码库中类似的测试范例）
非范围
明确说明本次 PRD 不涉及的内容。
补充说明
关于该功能的任何补充说明。
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.
- yesterday First seen · 73 lines · 50 tokens per session scan A 690ca9eb7796
to-prd is a skill published in the GitHub repository Yulin-Bi/CodeAuto (43 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 608 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
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
multi-module-maven
Use when working in a multi-module Maven project. Covers parent POM conventions, shared dependency management, inter-module rules, and build ordering.
epic-breakdown-advisor
Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.
lean-ux-canvas
Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.
daily-meeting-update
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday…
jira
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.