prd-create

Interview stakeholders, survey codebases, and map requirements to modules for GitHub issues.

Updated Mar 23, 2026

Search Tags:#requirements #interview #prd #product-management #github-issue #repository-exploration

Ready to run

npx skills add https://github.com/mia-cx/.agents --skill prd-create-mia-cx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-create
Source: https://github.com/mia-cx/.agents/tree/main/skills/prd-create
Command: npx skills add https://github.com/mia-cx/.agents --skill prd-create-mia-cx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate a complete Product Requirements Document (PRD) by conducting user interviews, examining the codebase, and designing modular solutions, then exporting as a GitHub issue.

Core Features & Use Cases

Interview-led discovery to gather goals, constraints, and success metrics.
Repo exploration to validate assumptions and surface context.
Modular design sketching that identifies components and dependencies.
PRD-to-issue workflow to submit a maintainable document as a GitHub issue.

Quick Start

Provide a complete PRD draft by interviewing the user, outlining modules, and submitting it as a GitHub issue.

Frequently Asked Questions about prd-create

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

FAQPage Schema

How do I create a PRD from user interviews and codebase analysis?▼

You can create a PRD by conducting interview-led discovery to gather goals, validating assumptions through repository exploration, sketching modular designs, and exporting the final requirements document as a GitHub issue.

What is the best way to map product requirements to code modules?▼

The best way to map product requirements to modules is by surveying the codebase to surface context, then sketching a modular design that identifies specific components and dependencies based on stakeholder interview insights.

How do I turn a product requirements document into a GitHub issue?▼

You turn a product requirements document into a GitHub issue by using a structured PRD-to-issue workflow that submits the maintainable document directly to your repository for feature tracking and product planning.

Can I use interview-led discovery to gather success metrics for feature planning?▼

Yes, interview-led discovery is designed to gather goals, constraints, and success metrics directly from stakeholders, which then informs feature discovery and product planning tasks.

Does PRD creation work without exploring the code repository?▼

Repository exploration is a core step to validate assumptions and surface context for modular design, so skipping it may result in requirements that are not properly mapped to existing code components.

How do I gather product constraints and goals before writing requirements?▼

You gather product constraints and goals by conducting structured user interviews with stakeholders, capturing their needs and success metrics to form the foundation of the product requirements document.