requirements

Cross-cutting PM utilities and essential PM practices.

'MUST BE USED PROACTIVELY when user mentions: planning, PRD, product requirements document, project plan, roadmap, specification, requirements analysis, feature breakdown, technical spec, project estimation, milestone planning, or task decomposition. Use IMMEDIATELY when user says "create a PRD", "plan this feature", "document requirements", "break down this project", "estimate this work", "create a roadmap", "write specifications", or references planning/documentation needs. Expert Technical Project Manager that creates comprehensive PRDs with user stories, acceptance criteria, technical architecture, task breakdowns, and separate task assignment files for sub-agent delegation.'

Use this agent when you need to create comprehensive Product Requirements Documents (PRDs) that combine business strategy, technical architecture, and user research. Examples: <example>Context: The user needs to create a PRD for a new feature or product launch. user: "I need to create a PRD for our new user authentication system that will support SSO and multi-factor authentication" assistant: "I'll use the prd-specialist agent to create a comprehensive PRD that covers the strategic foundation, technical requirements, and implementation blueprint for your authentication system."</example> <example>Context: The user is planning a major product initiative and needs strategic documentation. user: "We're launching a mobile app for our e-commerce platform and need a detailed PRD to guide development" assistant: "Let me engage the prd-specialist agent to develop a thorough PRD that includes market analysis, user research integration, technical architecture, and implementation roadmap for your mobile app initiative."</example>

Skills for the Ralph autonomous agent system - Generate PRDs and convert them to prd.json format for autonomous execution

Problem-Based Software Requirements Specification methodology for AI-assisted requirements engineering. Provides structured approach to capture Customer Problems (WHY), Customer Needs (WHAT), and Functional Requirements (HOW) with full traceability.

Comprehensive AI-assisted requirements elicitation. Supports stakeholder interviews (LLMREI pattern), document extraction, stakeholder simulation, domain research, gap analysis, user story mapping, customer journey mapping, JTBD analysis, prioritization (MoSCoW/Kano/WSJF), surveys, workshops, brainstorming, and business rules analysis. Exports to canonical, EARS, and Gherkin formats.