to-prd

Synthesizes conversation context into a PRD and publishes it to the project issue tracker.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill to-prd-cloudofgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/to-prd
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill to-prd-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design discussion into a formal Product Requirements Document usually means re-interviewing stakeholders and re-writing context from scratch. This Skill converts the current conversation and codebase understanding directly into a structured PRD and files it in the project issue tracker, eliminating redundant interviews. ## Core Features & Use Cases - Context Synthesis: Generates a PRD from the existing conversation and repository exploration, using the project's domain glossary and respecting existing ADRs. - Test Seam Planning: Identifies the highest-level testing seams in the codebase before writing the PRD and confirms them with the user. - Issue Tracker Publishing: Writes the PRD using a fixed template (problem statement, user stories, implementation and testing decisions, scope) and publishes it with the ready-for-agent triage label. - Use Case: After discussing a new feature with an agent, invoke this Skill to produce a complete PRD issue ready for an implementation agent to pick up, without any further triage. ## Quick Start Ask the agent to turn the current conversation into a PRD and publish it to the project 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?▼

Invoke the to-prd skill after discussing the feature with the agent. It synthesizes the existing conversation and codebase exploration into a structured PRD covering problem statement, user stories, implementation decisions, and testing decisions, then publishes it to the issue tracker.

How to write user stories for a product requirements document?▼

The skill generates an extensive numbered list of user stories in the format 'As an <actor>, I want a <feature>, so that <benefit>'. The stories are derived from the conversation context and cover all aspects of the feature.

Does the PRD skill require an interview with the user?▼

No. The skill explicitly avoids interviewing the user and instead synthesizes what has already been discussed. The only checkpoint is confirming the proposed testing seams match the user's expectations before writing the PRD.

What happens if the issue tracker setup is missing?▼

The skill expects the issue tracker and triage label vocabulary to be preconfigured. If they are missing, it instructs you to run /setup-matt-pocock-skills before proceeding with PRD publication.

Should a PRD include file paths and code snippets?▼

Generally no, because they become outdated quickly. The skill's template excludes specific file paths and code, with one exception: prototype snippets that encode a decision more precisely than prose, such as state machines, schemas, or type shapes.