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 serejaris/kimi-skills --skill idea-to-prdgit clone --depth 1 https://github.com/serejaris/kimi-skillsWrote 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/serejaris/kimi-skills/idea-to-prd)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/idea-to-prd"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/idea-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/serejaris/kimi-skills/idea-to-prd"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/idea-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.00105 | $0.03078 |
| Opus 5 | $0.00053 | $0.01539 |
| Sonnet 5 | $0.00021 | $0.00616 |
| Haiku 4.5 | $0.00011 | $0.00308 |
Grade A, and why
idea-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 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Architect
一句话需求 → 完整 PRD：通过结构化 SOP 流程，将模糊的产品想法转化为包含用户故事、功能清单、MoSCoW 优先级和验收标准的专业产品需求文档。
Quick Start
用户只需提供一句话描述需求，Agent 按照以下流程自动完成 PRD：
用户：我想做一个团队内部的知识库系统
Agent：[按 SOP 流程输出完整 PRD]
SOP 流程
Phase 1: 需求澄清（Requirement Elicitation）
目标：从用户的一句话需求中提取足够信息来构建 PRD。
操作步骤：
- 解析原始需求：识别用户需求中的核心动词、目标对象和隐含约束
- 提出澄清问题（最多 5 个关键问题）：
- 目标用户是谁？（内部团队 / 外部客户 / 两者都有）
- 要解决的核心痛点是什么？（现在怎么做的，哪里不好）
- 有没有参考产品或竞品？
- 有没有硬性约束？（时间、预算、技术栈、合规要求）
- 成功的衡量标准是什么？（关键指标）
- 如果用户要求跳过澄清，则基于合理假设继续，并在 PRD 的「假设与约束」章节中标明
输出：一份需求背景摘要（不超过 200 字）
Phase 2: 用户画像与用户故事（User Personas & Stories）
目标：识别所有关键角色，为每个角色编写用户故事。
操作步骤：
-
识别用户角色（Persona）：
-
列出 2-5 个核心角色
-
每个角色用一句话描述其身份、目标和痛点
-
格式：
**角色名称**：[一句话描述] - 身份：[职位/角色] - 核心目标：[想达成什么] - 主要痛点：[现在遇到什么问题]
-
-
编写用户故事（User Stories）：
- 每个角色至少 3 条用户故事
- 标准格式：作为[角色]，我想要[功能]，以便[价值/目的]
- 用户故事必须满足 INVEST 原则：
- Independent（独立）：故事之间尽量无依赖
- Negotiable（可协商）：不锁定实现方式
- Valuable（有价值）：对用户有明确价值
- Estimable（可估算）：团队能评估工作量
- Small（足够小）：一个迭代内可完成
- Testable（可测试）：有明确的验证方式
-
故事地图排列：按用户旅程的时间线排列故事，识别核心路径
输出：用户角色表 + 用户故事列表
Phase 3: 功能清单与分解（Feature Decomposition）
目标：将用户故事转化为具体的功能列表，区分功能性和非功能性需求。
操作步骤：
-
功能性需求（Functional Requirements）：
- 从每条用户故事中提取具体功能点
- 每个功能点包含：
- 功能编号（F-001, F-002...）
- 功能名称
- 所属用户故事编号
- 功能描述（一句话说清做什么）
- 输入 / 输出 / 交互说明
-
非功能性需求（Non-Functional Requirements）：
-
逐项检查以下维度，标注适用的：
维度 检查项 性能 响应时间、并发量、吞吐量 安全 认证、授权、数据加密、合规 可用性 SLA、容灾、备份恢复 可扩展性 用户增长、数据增长、功能扩展 易用性 学习成本、无障碍访问、多语言 兼容性 浏览器、设备、操作系统、API 版本
-
-
功能依赖关系：画出功能之间的前后依赖（哪些功能必须先做）
输出：功能需求表 + 非功能需求表 + 依赖关系说明
Phase 4: MoSCoW 优先级排序
目标：对所有功能按 MoSCoW 框架进行优先级分类。
MoSCoW 框架定义：
| 等级 | 含义 | 判断标准 | 占比建议 |
|---|---|---|---|
| Must Have | 必须有 | 没有它产品无法上线、用户核心流程走不通 | 约 60% |
| Should Have | 应该有 | 重要但不致命，可以短期用替代方案 | 约 20% |
| Could Have | 可以有 | 锦上添花，有了更好，没有也行 | 约 15% |
| Won't Have (this time) | 暂不做 | 明确排除，避免范围蔓延，留到后续版本 | 约 5% |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 320 lines · 105 tokens per session scan A 347a9f37cacd
idea-to-prd is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 3,078 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".