skills.rest
tsunami28
tsunami28COMMUNITY
Explore all skills by this author →
Website𝕏@MilosKatinskiGitHub

elaboration-upsert-prd-document

Create Product Requirements Documents with goals, scope, and success criteria.

Updated Jun 18, 2026
Search Tags:#product management#prd#product requirements#epic planning#scope definition#success metrics
One-click install
npx skills add https://github.com/tsunami28/MindNova --skill elaboration-upsert-prd-document
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: elaboration-upsert-prd-document
Source: https://github.com/tsunami28/MindNova/tree/main/.claude/skills/elaboration-upsert-prd-document
Command: npx skills add https://github.com/tsunami28/MindNova --skill elaboration-upsert-prd-document

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams transform confirmed initiatives into structured Product Requirements Documents that clarify problems, goals, scope, requirements, and success measures before implementation begins.

Core Features & Use Cases

  • PRD Creation: Produces disciplined product requirement documents covering context, goals, non-goals, users, scope, requirements, metrics, and open questions.
  • Product Alignment: Establishes a durable source of intent that connects epics with downstream stories, API contracts, and implementation decisions.
  • Use Case: When a product initiative is ready for delivery planning, use this Skill to define what should be built, why it matters, and how success will be evaluated.

Quick Start

Use the elaboration-upsert-prd-document skill to draft a PRD for the confirmed initiative and link it to the appropriate epic.

Frequently Asked Questions about elaboration-upsert-prd-document

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

FAQPage Schema
How do I create a Product Requirements Document from confirmed epics and initiatives?▼

You need to provide confirmed initiatives, epics, and validated hypotheses to generate structured product requirements that include context, scope boundaries, goals, requirements, and measurable success criteria.

What should a PRD include for successful product delivery?▼

A product requirements document should include explicit scope boundaries, traceable requirements, measurable outcomes, linked planning metadata, defined goals, and open questions to guide implementation.

When do I need to write a PRD with success criteria and scope definition?▼

You write a PRD during product elaboration workflows when confirmed initiatives and epics require structured problem definitions, scope boundaries, and success criteria before development begins.

Can I use this to align product requirements with API contracts and downstream stories?▼

Yes, PRD creation establishes a durable source of intent that connects confirmed epics with downstream stories, API contracts, and implementation decisions for product alignment.

How do I define success metrics and non-goals for product requirements?▼

You define success metrics by establishing measurable outcomes and explicit scope boundaries within the PRD, ensuring traceable requirements and linked planning metadata clarify what matters and what is excluded.

Related Skills

Explore More Product & Management Skills→
DavidsonGomesDavidsonGomes

evo-check-implementation-readiness

Identify gaps in PRD, UX, architecture, and epic specifications.

Community
Advanced
kbrgnjkbrgnj
14

domain-decomposition-api-design-advisor

Decompose business scope into bounded contexts and API contracts for Kotlin and Spring projects.

Community
Advanced
dhar174dhar174
1

breakdown-epic-pm

Translate user requests into a complete Epic PRD with standard sections.

Community
Advanced
ilandahanilandahan
9

aid-discovery

Validate problem space and stakeholder readiness before PRD initiation.

Community
Basic