biz-requirements

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.

Guides you through creating a Product Requirements Document (PRD) for a new app or feature.

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.

Generate comprehensive Product Requirements Documents (PRDs) from conversation context. Use when planning new features, products, or projects.

PRDs, user stories, acceptance criteria, and technical specifications.

'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.'