write-a-prd

To write a PRD using user interviews, provide an initial feature idea and answer clarifying questions about constraints and success criteria. The skill guides relentless questioning to capture requirements, validates assumptions against your repository, and outputs a complete PRD with user stories.

A product requirements document for implementation should include the problem statement, solution, user stories, implementation decisions, testing decisions, out of scope items, and further notes. This skill generates all these sections grounded by exploring your current codebase context.

Yes, you can generate a GitHub issue directly from a feature idea by sharing your planned feature and current codebase assumptions. The skill validates the codebase context and formats the resulting PRD, including testing strategy and module scope, for submission as a GitHub issue.

Yes, writing an implementation-ready PRD requires existing codebase context to verify assertions and understand the current state. Sharing what you believe is already in the repository allows the skill to ground module identification and validate feasibility before committing to a plan.

To define testing strategy and out of scope items in a PRD, articulate your planned improvements and user needs during the interview process. The skill captures these requirements and explicitly documents both the testing decisions and what falls outside the module scope.

The best way to turn ambiguous feature requests into a structured PRD is through interview-based shared understanding. This approach aligns assumptions, captures user needs through relentless questioning, and checks repo-grounded feasibility to produce a decision-ready document.