to-prd
vinvcn/mattpocock-skills-zh-cn
Convert conversation context into a structured PRD and publish to your project's issue tracker.
What is to-prd?
This skill synthesizes your current conversation context and codebase understanding into a complete Product Requirements Document (PRD), then posts it to your project's issue tracker with appropriate triage labels. Use it when you want to formalize feature requirements based on what you've already discussed and learned about the codebase.
- Analyzes current conversation context and codebase state to generate comprehensive PRDs
- Drafts testing seams and confirms them with you before finalizing
- Publishes PRDs directly to your project's issue tracker with `ready-for-agent` label
- Uses project domain glossary and respects existing Architecture Decision Records (ADRs)
- Structures requirements as detailed user stories covering all feature aspects
- Documents implementation and testing decisions with technical clarity
How to install to-prd
npx skills add https://github.com/vinvcn/mattpocock-skills-zh-cn --skill to-prd- Issue tracker configured and accessible (GitHub Issues, Jira, or similar)
- Project domain glossary and Architecture Decision Records (ADRs) provided to the agent
- Codebase accessible for exploration and understanding current state
How to use to-prd
- 1.Discuss your feature idea or requirements in the conversation
- 2.Let the skill explore the repository to understand current codebase state
- 3.Review the proposed testing seams and confirm they align with your expectations
- 4.The skill generates a complete PRD using the provided template
- 5.PRD is automatically published to your issue tracker with `ready-for-agent` label
Use cases
- Formalizing a feature discussion into a tracked requirement after exploring the codebase
- Creating a PRD from a prototype or proof-of-concept conversation
- Documenting architectural decisions and testing strategy for a new feature
- Converting informal requirements into issue-tracker items ready for agent implementation
- Ensuring feature scope, testing approach, and implementation decisions are explicit before development
- Engineering teams using issue trackers (GitHub, Jira, etc.) for project management
- Developers working with AI coding agents who need structured requirements
- Teams practicing architecture-driven development with ADRs
- Projects with established domain glossaries and testing conventions
to-prd FAQ
No. The skill synthesizes only what you've already discussed and what it learns from the codebase—it does not interview you for additional details.
Run `/setup-matt-pocock-skills` to provide the skill with your project's vocabulary and architectural decisions. Without these, the skill will work but may not align with your project conventions.
The skill generates the PRD and shows it to you for confirmation of testing seams before publishing. Review the full PRD output before it posts to your issue tracker.
The skill applies only the `ready-for-agent` label. No additional triage is needed—the PRD is ready for agent-based implementation.
Only when a snippet (state machine, reducer, schema, type shape) more precisely encodes a decision than prose would. Full working code is not included—only decision-critical excerpts.
Full instructions (SKILL.md)
Source of truth, from vinvcn/mattpocock-skills-zh-cn.
name: to-prd description: 将当前对话上下文转成 PRD，并发布到项目 issue tracker。适用于用户想基于当前上下文创建 PRD 时。
这个 skill 使用当前 conversation context 和 codebase understanding 产出 PRD。不要访谈用户，只综合你已经知道的内容。
Issue tracker 和 triage label vocabulary 应该已经提供给你；如果没有，运行 /setup-matt-pocock-skills。
Process
-
如果还没有探索 repo，先探索它以理解 codebase 当前状态。在 PRD 中始终使用项目 domain glossary vocabulary，并遵守相关 ADRs。
-
草拟你准备在哪些 seams 上测试这个 feature。优先使用现有 seams，而不是新增 seams。使用尽可能高层的 seam。如果确实需要新增 seams，尽可能在最高层提出。
与用户确认这些 seams 是否符合预期。
- 使用下面模板写 PRD，并发布到项目 issue tracker。应用
ready-for-agenttriage label；不需要额外 triage。
Problem Statement
用户正在面对的问题，从用户视角描述。
Solution
问题的解决方案，从用户视角描述。
User Stories
一份很长的编号 user stories 列表。每条 user story 使用以下格式：
- As an <actor>, I want a <feature>, so that <benefit>
这份 user stories 列表应该非常完整，覆盖 feature 的所有方面。
Implementation Decisions
已作出的 implementation decisions 列表。可以包括：
- 将 build/modify 的 modules
- 将 modify 的 module interfaces
- 来自 developer 的技术澄清
- Architectural decisions
- Schema changes
- API contracts
- Specific interactions
不要包含具体 file paths 或 code snippets。它们可能很快过时。
例外：如果 prototype 产出的 snippet 比 prose 更精确地编码了某个决策（state machine、reducer、schema、type shape），可以内联到相关 decision 中，并简短说明它来自 prototype。只保留决策密集部分，不要放完整 working demo。
Testing Decisions
已作出的 testing decisions 列表。包括：
- 什么是好测试的描述（只测试 external behavior，不测试 implementation details）
- 哪些 modules 会被测试
- 测试的 prior art（即 codebase 中类似类型的 tests）
Out of Scope
本 PRD 范围外事项的描述。
Further Notes
关于 feature 的其他 notes。
</prd-template>Related skills
More from vinvcn/mattpocock-skills-zh-cn and the wider catalog.
to-questionnaire
Convert decisions you can't answer alone into a structured questionnaire for others to complete.
to-spec
Convert conversation context into a spec and publish to your project issue tracker.
to-tickets
Break plans, specs, or conversations into tracer-bullet tickets with blocking dependencies for your issue tracker.
triage
Triage issues and PRs through a state machine of roles, verify claims, and generate agent-ready briefs.
ubiquitous-language
Extract and formalize domain terminology from conversations into a DDD-style ubiquitous language glossary.
wait-what
Pause and clarify: restate unclear messages using simplified technical English.