write-a-prd

Create structured product requirement documents from feature ideas and codebase exploration.

4|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Ni-Bu/skills --skill write-a-prd-ni-bu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/Ni-Bu/skills/tree/main/write-a-prd
Command: npx skills add https://github.com/Ni-Bu/skills --skill write-a-prd-ni-bu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn vague feature ideas into a clear, structured PRD by guiding the user through discovery, validating the idea against the codebase, and organizing the result into a practical planning document.

Core Features & Use Cases

  • Interview-driven requirement gathering to uncover goals, constraints, and open questions.
  • Codebase exploration to confirm assumptions before proposing implementation details.
  • Obsidian-ready PRD creation with user stories, implementation decisions, testing decisions, and out-of-scope notes.
  • Use it when you need to scope a new feature, align stakeholders, or document a product plan before breaking it into implementation slices.

Quick Start

Ask me to help write a PRD for your feature idea and I will interview you, inspect the codebase, and draft the note in your Obsidian vault.

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 requirement document from a vague feature idea?▼

Writing a product requirement document from a feature idea involves an interview-driven discovery process to gather goals and constraints, validating assumptions against your codebase, and structuring the output into a comprehensive PRD for stakeholder alignment.

What should be included in a PRD for new feature planning?▼

A PRD for new feature planning should include a problem statement, proposed solution, user stories, implementation decisions, testing decisions, out-of-scope items, and slice-ready scaffolding to guide development.

Can I generate PRDs directly in my Obsidian vault?▼

Yes, you can generate Obsidian-ready PRD notes directly in your vault, organizing feature planning details like user stories and implementation decisions alongside your existing product documentation.

How does codebase exploration help with feature scoping?▼

Codebase exploration confirms technical assumptions before proposing implementation details, ensuring your feature scoping is grounded in existing architecture and preventing unfeasible product plans.

Do I need a finished feature concept before creating a PRD?▼

No, you do not need a finished concept. The PRD creation process uses stakeholder interviews to uncover goals, constraints, and open questions, turning vague ideas into a structured product plan.

What is the best way to document implementation decisions in a PRD?▼

The best way to document implementation decisions in a PRD is to record them alongside testing decisions and out-of-scope notes, creating a slice-ready scaffolding that aligns stakeholders before development begins.