write-a-prd

Create a PRD through user interviews and codebase exploration, then submit it as a GitHub issue.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill write-a-prd-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-extras/skills/write-a-prd
Command: npx skills add https://github.com/toderian/project_template --skill write-a-prd-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Product Requirements Document from scratch is time-consuming and often misses technical context. This Skill guides an AI agent through a structured interview, codebase verification, and module design process to produce a complete PRD submitted directly as a GitHub issue. ## Core Features & Use Cases - Structured PRD Workflow: Interviews the user about the problem, explores the repository to verify assumptions, and sketches deep, testable modules before writing. - Standardized PRD Template: Produces a PRD with problem statement, solution, extensive user stories, implementation decisions, testing decisions, and out-of-scope notes. - GitHub Issue Submission & Task Generation: Submits the finished PRD as a GitHub issue and optionally generates area-prefixed task files from it. - Use Case: A product manager wants to plan a new billing feature. The Skill interviews them, checks the codebase, drafts the PRD with user stories and module decisions, and files it as a GitHub issue ready for the team. ## Quick Start Ask the agent to write a PRD for the new feature you have in mind and answer its interview questions about the problem and solution.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I write a PRD with an AI coding agent?

Invoke the write-a-prd skill and describe the problem you want to solve in detail. The agent interviews you, explores your codebase to verify assumptions, designs the major modules, and writes a complete PRD using a structured template.

What sections does a good product requirements document include?

This 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 deliberately excludes specific file paths and code snippets that quickly become outdated.

Can a PRD be submitted as a GitHub issue automatically?

Yes, the skill submits the finished PRD directly as a GitHub issue once the content is complete. Afterward it can optionally generate area-prefixed task files in docs/tasks_manager/_todos/ linked back to the PRD identifier.

Does the PRD workflow verify ideas against the actual codebase?

Yes, step two of the workflow explores the repository to verify the user's assertions and understand the current state of the code before designing modules. This grounds the PRD's implementation decisions in the real architecture.

When should I not use a full PRD workflow?

Skip the full PRD process for small bug fixes, trivial changes, or well-understood tasks that need no stakeholder alignment. The workflow is designed for planning new features where user stories, module design, and testing decisions need documentation.