plan-prd

Name: plan-prd
Availability: InStock
Author: dthompson-jti

Create PRD documents with user stories, scope, and accessibility requirements.

Updated Aug 23, 2026

Search Tags:#requirements #validation #prd #ux #product-management #user-stories

Ready to run

npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill plan-prd-dthompson-jti

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-prd
Source: https://github.com/dthompson-jti/safety-check-app-concept/tree/main/.agent/skills/plan/prd
Command: npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill plan-prd-dthompson-jti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD planning with defined user stories, scope, acceptance criteria, and accessibility requirements helps teams align, reduce rework, and accelerate delivery on large features.

Core Features & Use Cases

Structured artifacts: PRD-[EPIC-NAME].md, a state matrix, and a comprehensive DoD checklist for scope and progress tracking.
Design options & debate: Generate 4-6 architecturally distinct options with Socratic Debate to resolve tradeoffs.
Validation & governance: Phase-driven discovery, UX specification, and accessibility validation with explicit success criteria.

Quick Start

Start by drafting Phase 1 discoveries for your EPIC and save the resulting PRD-[EPIC-NAME].md under docs/working/.

Frequently Asked Questions about plan-prd

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

FAQPage Schema

How do I plan a PRD for large features with defined user stories and acceptance criteria?▼

Planning a PRD for large features involves generating structured artifacts like a markdown document, a state matrix, and a comprehensive Definition of Done checklist to define user stories, scope, and acceptance criteria systematically.

What is the best way to resolve design tradeoffs when scoping product requirements?▼

Resolving design tradeoffs in product requirements is best handled by generating 4 to 6 architecturally distinct options and applying Socratic Debate to evaluate and resolve the competing tradeoffs before finalizing the scope.

How do I include accessibility requirements in product requirement documents?▼

Including accessibility requirements in PRDs requires integrating phase-driven discovery, UX specification, and explicit accessibility validation steps with defined success criteria directly into the planning workflow.

Can I use a phased discovery approach for product management epics?▼

Using a phased discovery approach for product management epics guides the process through structured discovery, design specification, and validation phases to align teams and reduce rework on large features.

Does PRD planning constrain architecture decisions to the design phase?▼

PRD planning constrains architecture to the planning phase, focusing strictly on discovery, design validation, and scope definition rather than generating detailed technical implementation or architectural blueprints.