write-a-prd

Interview users and explore codebases to draft structured PRDs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kagenti/humr --skill write-a-prd-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/kagenti/humr/tree/main/.agents/skills/write-a-prd
Command: npx skills add https://github.com/kagenti/humr --skill write-a-prd-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need a well-structured Product Requirements Document (PRD) that captures user needs, technical considerations, and acceptance criteria, and you want to ensure explicit user approval before any GitHub submission.

Core Features & Use Cases

  • Guided user interviews to elicit goals, constraints, and success metrics.
  • Codebase exploration to validate context and discover dependencies.
  • Modular design sketches that outline key components, interfaces, and risks.
  • PRD drafting using a structured template with sections for problem, proposed solution, user stories, and implementation decisions.
  • GitHub issue submission only after explicit user approval.

Quick Start

Describe your product goal and constraints, and I will guide you through interviews, repo exploration, and PRD drafting for approval.

Frequently Asked Questions about write-a-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a PRD with structured requirements and user approval?

To draft a PRD with structured requirements and user approval, this skill guides you through interactive interviews and codebase exploration to outline modular designs, then generates a detailed document for your explicit approval before submission.

What is the best way to generate user stories from an existing codebase for product planning?

Generating user stories from an existing codebase for product planning involves exploring your repository to validate context and discover dependencies, then synthesizing those technical constraints into structured user stories within a drafted PRD.

Can I scope product features and architectural planning before submitting a GitHub issue?

Yes, you can scope product features and architectural planning before submitting a GitHub issue by sketching modular designs that outline key components, interfaces, and risks during the guided interview process.

How does the PRD drafting process handle problem statements and implementation decisions?

The PRD drafting process handles problem statements and implementation decisions by applying a structured template that captures proposed solutions, user stories, and architectural choices based on your elicited goals and constraints.

Do I need explicit user approval before creating a GitHub issue for requirements documentation?

Yes, explicit user approval is required before creating a GitHub issue for requirements documentation, ensuring the drafted PRD accurately reflects the problem statement, solution description, and implementation decisions.

What are the limitations of using automated interviews for feature scoping and product ideation?

The limitations of using automated interviews for feature scoping and product ideation include relying entirely on your ability to accurately describe product goals and constraints during the interview to produce a valid modular design sketch.