write-a-prd

Create a module-oriented PRD with user stories and GitHub-issue-ready format.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Levezze/devkit --skill write-a-prd-levezze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/Levezze/devkit/tree/main/skills/write-a-prd
Command: npx skills add https://github.com/Levezze/devkit --skill write-a-prd-levezze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a rough feature idea into a clear, shared product requirements document by interviewing you, validating assumptions against the codebase, and designing the modules needed for delivery.

Core Features & Use Cases

  • User interview and alignment: Drives a relentless question-and-answer session until problem, goals, constraints, and tradeoffs are understood.
  • Repo exploration and assumption checking: Reviews the existing codebase to confirm what’s true and what needs to change.
  • Module-focused design: Breaks the solution into major modules, emphasizing deep, testable interfaces, and confirms expected ownership for tests.
  • PRD submission-ready output: Produces a PRD structured with problem, solution, extensive user stories, implementation decisions, testing decisions, and out-of-scope items, formatted for publishing as a GitHub issue.

Quick Start

Use the write-a-prd skill to create a PRD for your feature by giving a long description of the problem you want to solve and any initial ideas you already have.

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 product requirements document from a rough feature idea?

Creating a PRD for new features involves checking assumptions against the existing codebase and defining module boundaries. It results in a structured specification containing problem statements, implementation decisions, and clearly marked out-of-scope items.

How do I align team goals and constraints before writing user stories?

To align team goals and constraints before writing user stories, engage in a relentless question-and-answer session. This validates tradeoffs and ensures the problem is fully understood before generating the product requirements document.

Does this PRD generation process format output for GitHub issues?

Yes, the PRD generation process formats the final output for GitHub issues. The resulting specification includes implementation decisions and out-of-scope boundaries, structured for direct publishing to your repository.

What is the best way to validate product assumptions against an existing codebase?

The best way to validate product assumptions against an existing codebase is through repo exploration during the PRD creation process. This checks what is true and what needs to change before designing the required solution modules.