skills.rest
craft-ts
craft-tsCOMMUNITY
Explore all skills by this author →
GitHub

to-prd

Generates a PRD from conversation context and publishes it to the project issue tracker.

3|Updated Jan 9, 2026
Search Tags:#planning#documentation#issue tracker#user stories#prd#product requirements#generate
One-click install
npx skills add https://github.com/craft-ts/craft-ts --skill to-prd-craft-ts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/craft-ts/craft-ts/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/craft-ts/craft-ts --skill to-prd-craft-ts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long planning conversation into a structured, actionable Product Requirements Document is tedious and error-prone. This Skill synthesizes the existing conversation context and codebase understanding into a complete PRD and publishes it directly to the project issue tracker, without re-interviewing the user. ## Core Features & Use Cases - Context-to-PRD synthesis: Converts the current conversation and codebase exploration into a structured PRD covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Module planning: Identifies deep, testable modules to build or modify and confirms them with the user before writing the PRD. - 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 feature with the AI and exploring the repository, invoke this Skill to produce a ready-to-implement PRD issue that respects the project's domain glossary and ADRs. ## Quick Start Ask the AI 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 create a PRD from an AI conversation?▼

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

What sections does the 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. It avoids specific file paths that could become outdated.

Does the skill ask me questions before writing the PRD?▼

No, it explicitly does not interview the user and instead synthesizes what is already known. It only checks with the user about which modules to build and which modules should have tests written.

What setup is required before using this skill?▼

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

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

Avoid it when the feature scope has not been discussed yet, since the skill relies on existing context. It is also unsuitable when implementation details are still unsettled, as the PRD records decisions rather than open questions.

Related Skills

Explore More Product & Management Skills→
docs-plusdocs-plus
88

to-prd

Synthesize conversation context and codebase knowledge into structured PRDs and publish them to issue trackers.

Official
Intermediate
prabaljainnprabaljainn

to-prd

Generates a PRD from conversation context and publishes it to the project issue tracker.

Community
Intermediate
ishandutta2007ishandutta2007
13

PRD Synthesis (To PRD)

Convert product and technical conversation context into a complete Product Requirements Document.

Community
Intermediate
chrisallenlanechrisallenlane
18

scope

Explore a problem space and draft a ticket with acceptance criteria.

Community
Advanced