write-a-prd

A PRD defines product scope by clarifying problems and mapping modular design. A complete PRD includes Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, Further Notes, and a GitHub issue template for development handoff.

To write a PRD for a new feature, describe the initial problem and desired outcome. The skill guides you through structured user interviews, audits your existing codebase to verify assumptions, maps modular components, and generates a complete requirements document ready for submission.

Yes, you can generate a GitHub issue template directly from product requirements. The skill outputs a structured PRD that includes a clear problem statement, solution approach, user stories, decisions, and tests formatted for immediate submission as a GitHub issue.

To align product requirements with your codebase, the skill audits your repository during the planning phase. It explores existing code and design context to verify assumptions, ensuring the generated PRD and modular design accurately reflect your current architecture.

The best way to document user stories and acceptance criteria is through a structured PRD. By conducting user interviews to clarify goals and mapping modular design, the skill outlines major components, success criteria, risks, and acceptance criteria ready for developer handoff.

Yes, conducting user interviews before drafting product requirements ensures alignment. The skill uses structured interviews to clarify problems and goals, verifying assumptions against existing code before generating the final PRD document and GitHub issue template.