to-prd

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

Updated Nov 23, 2024
One-click install
npx skills add https://github.com/tokisakiyuu/dotfiles --skill to-prd-tokisakiyuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/tokisakiyuu/dotfiles/tree/main/home/dot_claude/skills/to-prd
Command: npx skills add https://github.com/tokisakiyuu/dotfiles --skill to-prd-tokisakiyuu

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 interviewing the user again. ## Core Features & Use Cases - Context-Driven PRD Synthesis: Converts the existing conversation and codebase exploration into a full PRD covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Module Planning: Identifies deep modules with simple, testable interfaces before writing, and confirms module and testing scope with the user. - 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 AI and exploring the repo, invoke this Skill to produce a complete PRD with extensive user stories and architectural decisions, then file it as a triaged issue ready for implementation. ## 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 full PRD without re-interviewing you, 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. File paths and code snippets are excluded except for decision-rich prototype excerpts.

Does the PRD skill require any setup before use?▼

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

Can I review the module plan before the PRD is written?▼

Yes, the skill sketches the major modules to build or modify, favoring deep modules with simple testable interfaces, and checks with you on the module list and which modules should have tests before writing the PRD.

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

Avoid it when requirements are not yet discussed or the codebase context is unexplored, since the skill deliberately does not interview the user. It works best after a substantive design conversation has already occurred.