to-prd

Generate a PRD from conversation context and publish it to the project issue tracker.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill to-prd-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/core/to-prd
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill to-prd-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an exploratory conversation about a feature into a structured, actionable PRD is tedious and often loses context. This Skill synthesizes the current conversation and codebase understanding directly into a complete PRD and publishes it to the project issue tracker without re-interviewing the user. ## Core Features & Use Cases - Context-Driven Synthesis: Builds the PRD from existing conversation context and repository exploration, using the project's domain glossary and respecting existing ADRs. - Test Seam Planning: Identifies the highest-level testing seams for the feature and confirms them with the user before writing. - Structured PRD Template: Produces problem statement, solution, extensive user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. - Issue Tracker Publishing: Publishes the finished PRD to the project issue tracker and applies the ready-for-agent triage label. - Use Case: After discussing a new billing feature with the agent, invoke this Skill to produce a full PRD with user stories and testing decisions, then file it as a triaged issue ready for implementation. ## Quick Start Ask the agent to turn the current conversation into a PRD and publish it to the issue tracker.

Frequently Asked Questions about to-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a conversation into a PRD with an AI agent?

Invoke the to-prd skill after discussing the feature. It synthesizes the existing conversation context and codebase exploration into a structured PRD, then publishes it to the project issue tracker without asking additional interview questions.

What sections does a generated PRD include?

The PRD template includes a problem statement, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. File paths and code snippets are excluded except for decision-rich prototype excerpts.

Does the PRD skill require setup before use?

Yes, the issue tracker and triage label vocabulary must be provided first by running /setup-matt-pocock-skills. Without that setup, the skill cannot publish the PRD or apply the ready-for-agent triage label.

Can the PRD include code snippets or file paths?

Specific file paths and code snippets are excluded because they become outdated quickly. The exception is a prototype snippet that encodes a decision more precisely than prose, such as a state machine or schema, trimmed to decision-rich parts.

When should I not use conversation-to-PRD generation?

Avoid it when the feature scope is still unclear or the user has not yet confirmed testing seams. The skill checks seam expectations with the user before writing, so premature invocation produces a PRD built on unvalidated assumptions.