From sdlc
BMAD PRD methodology, quality standards, and reference data for creating, validating, and editing Product Requirements Documents
npx claudepluginhub nexussema/omg-marketplace --plugin sdlcThis skill uses the workspace's default tool permissions.
A BMAD PRD serves two audiences simultaneously:
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
A BMAD PRD serves two audiences simultaneously:
The PRD is the top of the funnel feeding all subsequent product development work. Quality here ripples through every phase.
Every sentence must carry information weight. Eliminate filler, padding, and verbose patterns.
All functional and non-functional requirements must be:
The PRD establishes the chain that all downstream artifacts depend on:
Vision -> Success Criteria -> User Journeys -> Functional Requirements -> (future: User Stories)
Every requirement must trace back to documented user needs and business objectives.
For detailed methodology and rationale, see:
references/prd-purpose.md - Full BMAD PRD methodology, anti-pattern examples, and downstream impact analysisFor project classification and domain-specific requirements, see:
references/project-types.csv - Project type detection signals, key questions, required/skip sections, and innovation signalsreferences/domain-complexity.csv - Domain complexity levels, compliance concerns, required knowledge, and special sections