write-a-prd

Generates a structured Product Requirements Document from a rough feature idea through guided interviews.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/arndvs/ctrlshft --skill write-a-prd-arndvs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/arndvs/ctrlshft/tree/main/skills/write-a-prd
Command: npx skills add https://github.com/arndvs/ctrlshft --skill write-a-prd-arndvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague feature idea into a well-scoped Product Requirements Document is hard — requirements stay fuzzy, module boundaries go undefined, and implementation starts without a shared plan. This Skill guides an AI agent through a structured interview and codebase exploration to produce a complete PRD submitted as a GitHub issue. ## Core Features & Use Cases - Guided Requirements Interview: Asks one question at a time with recommended answers, exploring the codebase to answer what code can reveal. - Module Sketching: Identifies major modules, their public interfaces, test boundaries, and deep-module opportunities before writing the PRD. - Structured PRD Template: Produces a PRD covering problem statement, user stories, implementation decisions, schema changes, testing, and out-of-scope items, submitted as a GitHub issue. - Use Case: You have a rough idea for a new notification system. The Skill interviews you about the problem, explores your codebase, sketches the modules, and writes a complete PRD as a GitHub issue ready for architecture planning. ## Quick Start Ask the agent to write a PRD for your new feature idea and answer its questions one at a time.

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 for a new feature?▼

Describe your problem to the agent, even vaguely. It interviews you one question at a time, explores your codebase for context, sketches module boundaries, then writes a complete PRD using a structured template and submits it as a GitHub issue.

What should a Product Requirements Document include?▼

This PRD template includes a problem statement, solution overview, user stories, module definitions with interfaces and test boundaries, technical decisions, schema changes, testing plans, and an explicit out-of-scope section.

Can I use this PRD skill with an existing codebase?▼

Yes. The process explicitly explores the existing codebase to understand architecture, conventions, data models, and relevant code paths before interviewing you, so the PRD reflects your actual system.

What happens after the PRD is complete?▼

The Skill offers two handoff paths: run the architect step to plan implementation with vertical slices and acceptance criteria, or convert the PRD directly into GitHub issues if it is detailed enough.

When should I not write a PRD for a task?▼

Skip the PRD for small bug fixes, trivial changes, or well-understood tasks that do not need scoping. The PRD process is designed for new features requiring problem definition, module design, and stakeholder alignment.