to-prd

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

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/TrayMachi/dotfiles --skill to-prd-traymachi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/TrayMachi/dotfiles/tree/main/agents/skills/to-prd
Command: npx skills add https://github.com/TrayMachi/dotfiles --skill to-prd-traymachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a structured 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's issue tracker, without re-interviewing the user. ## Core Features & Use Cases - Context Synthesis: Converts the current conversation and codebase exploration into a structured PRD covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Test Seam Planning: Identifies existing architectural seams for testing the feature and confirms them with the user before writing. - 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 codebase, invoke this Skill to produce a ready-to-implement PRD ticket without writing any documentation by hand. ## 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 your issue tracker.

What sections does the generated PRD template include?

The PRD template includes Problem Statement, Solution, an extensive numbered list of User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. It avoids specific file paths so the document stays accurate as code evolves.

Does to-prd publish the PRD to an issue tracker automatically?

Yes, it publishes the finished PRD to the project issue tracker and applies the ready-for-agent triage label. The tracker and label vocabulary must be configured beforehand via the setup-matt-pocock-skills command.

Why does to-prd ask about test seams before writing the PRD?

The skill identifies architectural seams where the feature will be tested, preferring existing high-level seams over new ones. It confirms these with the user to ensure the testing strategy matches expectations before finalizing the PRD.

When should I not use to-prd for requirements documentation?

Avoid it when the feature has not been discussed yet, since it synthesizes existing context rather than interviewing you. It is also unsuitable if no issue tracker or triage label vocabulary has been configured for the project.