Product Requirements Architect
Creates comprehensive, actionable product requirements documents (PRDs) with user stories, acceptance criteria, technical constraints, and prioritization frameworks like MoSCoW and RICE. Produces stakeholder-ready documents that bridge business goals and engineering execution.
SupaScore
80.25Best for
- ▸B2B SaaS feature specification with user stories and acceptance criteria
- ▸Mobile app MVP requirements with MoSCoW prioritization framework
- ▸Enterprise software enhancement PRDs with RICE scoring and technical constraints
- ▸API product requirements with stakeholder alignment and success metrics
- ▸Platform feature documentation bridging product strategy and engineering execution
What you'll get
- ●Executive summary with problem statement, followed by user stories in Given-When-Then format with clear acceptance criteria and MoSCoW categorization
- ●Structured PRD with outcome-driven problem definition, RICE-scored feature list, technical constraints section, and measurable success criteria
- ●Stakeholder-ready document with Jobs-to-be-Done framing, prioritized user stories, non-functional requirements, and clear scope boundaries
Not designed for ↓
- ×High-level product strategy or market positioning without specific feature details
- ×Technical architecture decisions or system design specifications
- ×Marketing requirements or go-to-market strategy documentation
- ×Project management timelines or resource allocation planning
A product feature idea, user problem, or initiative description with business context and target users.
A complete PRD document with problem statement, user stories, acceptance criteria, technical constraints, and prioritization using MoSCoW/RICE frameworks.
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (5 industry frameworks, 1 academic, 2 community practice)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
Initial version
Prerequisites
Use these skills first for best results.
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
Common Workflows
Product Discovery to Development Handoff
Complete flow from user research and problem validation through detailed requirements documentation to technical API specification for engineering teams
Activate this skill in Claude Code
Sign up for free to access the full system prompt via REST API or MCP.
Start Free to Activate This Skill© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice