skills.rest
vvedantb
vvedantbCOMMUNITY
Explore all skills by this author →
Website𝕏@vvedantbGitHub

write-a-prd

Convert stakeholder insights into a formal PRD for GitHub issues.

99|6|Updated Jan 11, 2026
Search Tags:#prd#product-requirements#github-issues#module-design#repo-exploration#interview-guided
One-click install
npx skills add https://github.com/vvedantb/eva --skill write-a-prd-vvedantb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/vvedantb/eva/tree/main/.agents/skills/write-a-prd
Command: npx skills add https://github.com/vvedantb/eva --skill write-a-prd-vvedantb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This PRD-writing workflow helps teams convert exploratory conversations, repo context, and design decisions into a formal product requirements document ready for GitHub issues.

Core Features & Use Cases

  • Structured interview-driven PRD drafting to capture user needs, constraints, and success criteria.
  • Repo-informed planning to align PRD with existing codebase realities and architecture.
  • Modular design sketching to outline components, dependencies, and milestones for implementation.
  • Use Case: When planning a major feature, generate a comprehensive PRD that maps user stories, acceptance criteria, metrics, and risks.

Quick Start

Describe a problem you want to solve in detail and I will guide you through drafting a PRD and submitting it as a GitHub issue.

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 from stakeholder insights and existing codebase context?▼

Draft a PRD by using a guided interview process to capture stakeholder insights, exploring your repository to align with architectural realities, and templating the results into a formal document ready for GitHub issues.

What is the best way to write product requirements for a new feature enhancement?▼

Writing product requirements for feature enhancements is best handled through structured interview prompts that map user stories, acceptance criteria, metrics, and risks into a comprehensive product requirements document.

Can I align a product requirements document with existing module designs and dependencies?▼

Yes, you can align a product requirements document with your existing architecture by performing repo exploration and modular design sketching to outline components, dependencies, and implementation milestones.

How do I convert exploratory conversations into a formal PRD for GitHub issues?▼

Convert exploratory conversations into a formal PRD by capturing user needs, constraints, and success criteria through an interview-guided workflow, then formatting the output consistently for GitHub issues.

Does this PRD drafting workflow support mapping user stories and acceptance criteria?▼

Yes, this PRD drafting workflow supports generating comprehensive documents that explicitly map user stories, acceptance criteria, metrics, and risks for major product initiatives across codebases.

Related Skills

Explore More Product & Management Skills→
ydnikolaevydnikolaev
8

skill-interviewer

Guide interviews to scope new Antigravity skills and draft specifications.

Community
Basic
tomzxtomzx
5

create-plan

Convert specification documents into structured implementation plans with phases, milestones, dependencies, and risks.

Community
Advanced
tomholfordtomholford
6

write-a-prd

Create a PRD from interviews, codebase exploration, and module design.

Community
Advanced
haJ1thaJ1t

grill

Conduct structured user interviews to align project requirements and document decisions.

Community
Advanced