skills.rest
organvm-i-theoria
organvm-i-theoriaOFFICIAL
Explore all skills by this author →
GitHub

product-requirements-designer

Generates enterprise and lean PRDs with user stories, acceptance criteria, and technical handoff specifications.

Updated May 16, 2026
Search Tags:#acceptance criteria#agile#user stories#prd#product requirements#jobs-to-be-done#technical handoff
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill product-requirements-designer-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-requirements-designer
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/product-requirements-designer
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill product-requirements-designer-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing product requirements documentation is time-consuming and inconsistent across teams, often missing critical sections like success metrics, risk assessment, or technical handoff details. This Skill provides complete, structured templates for both enterprise-grade PRDs and lean one-pagers so product teams produce thorough, stakeholder-ready specifications. ## Core Features & Use Cases - Dual PRD Modes: Full enterprise PRD with 15 sections (problem definition, HEART metrics, NFRs, launch plan, sign-off) or a hypothesis-driven lean one-pager for startup-style iteration. - Framework Templates: Built-in structures for Agile (epics, features, stories), Jobs-to-Be-Done (job maps, forces diagrams), and Outcome-Driven Innovation (opportunity scoring). - Artifact Scaffolding: Generates companion documents including user stories, Gherkin acceptance criteria, wireframes briefs, and technical handoff specs with API contracts and data models. - Use Case: A product manager needs to spec a new checkout feature. The Skill produces a complete PRD with functional requirements tables, edge cases, rollout plan with feature flags, plus a technical handoff spec the engineering team can implement directly. ## Quick Start Create a lean PRD for a mobile app feature that lets users save payment methods for faster checkout.

Frequently Asked Questions about product-requirements-designer

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

FAQPage Schema
How do I write a product requirements document (PRD)?▼

A PRD follows a structured flow: problem definition with evidence, goals and success metrics, user analysis, solution overview, detailed functional and non-functional requirements, UX specifications, risk assessment, and launch plan. This Skill provides complete templates for each section with priority definitions and sign-off tables.

What is the difference between an enterprise PRD and a lean PRD?▼

An enterprise PRD is a full cross-functional specification with market context, detailed requirements, and stakeholder sign-off. A lean PRD is a hypothesis-driven one-pager covering the problem, key assumptions, MVP scope, and success metrics for fast iteration.

How do I write acceptance criteria in Gherkin format?▼

Gherkin acceptance criteria use Given-When-Then structure: Given a precondition, When an action occurs, Then state the expected outcome. The Skill includes templates for happy paths, edge cases, error handling, and scenario outlines with data-driven examples.

What is Jobs-to-Be-Done and when should I use it?▼

Jobs-to-Be-Done frames requirements around the user's underlying goal rather than features, using job statements, job maps across eight stages, and forces diagrams analyzing push, pull, anxiety, and habit. Use it when discovering unmet needs or evaluating switching behavior.

What should a technical handoff spec include for engineering?▼

A technical handoff spec includes API endpoint definitions with request/response schemas, data models with SQL migrations, state machines, integration points, non-functional targets for performance and security, testing requirements, and a rollout plan with feature flags and rollback triggers.

Related Skills

Explore More Product & Management Skills→
sparkline-venturessparkline-ventures
14

synthesize

Cluster collected evidence into problem-framed themes with confidence analysis.

Official
Advanced
carterbscarterbs
4

implement-plan

Execute implementation plans phase by phase with automated verification at each milestone.

Community
Advanced
lync-cyberlync-cyber
133

arc-design

Converts PRD requirements into modules, APIs, data models, and non-functional decisions.

Community
Advanced
lucaspedrozaemlucaspedrozaem
1

prototype

Create clickable wireframe prototypes to validate SaaS feature concepts.

Community
Intermediate