
Requirements Analysis & Decomposition for Business Analysts
Decompose business requirements into testable components with acceptance criteria
What You Can Do
You can break down complex business requirements into actionable components that developers can implement and test. Claude helps you parse stakeholder input, identify hidden assumptions, generate testable acceptance criteria, map dependencies between requirements, and flag conflicts early—reducing implementation time and clarification cycles.
Features
Split high-level business needs into atomic features, user stories, and constraints
Create testable, specific acceptance criteria developers can use as test specifications
Identify relationships between requirements and flag sequential or conflicting dependencies
Surface hidden assumptions in stakeholder language and validate them
Create audit trails connecting business goals → requirements → acceptance criteria
Detect scope creep and conflicting requirements before handoff to development
Transform business language into structured requirement documents (BRD, SRS, epics)
Example Output
Input: "Make the checkout process faster for mobile users"
Claude Output:
Requirement 1: Reduce checkout page load time
- Acceptance Criteria:
- Mobile checkout loads in <2 seconds on 4G
- Lazy-load non-critical UI elements below fold
- Performance meets Core Web Vitals standards
- Dependencies: Image optimization (Req 3), API caching (Req 4)
Requirement 2: Minimize form fields on mobile
- Acceptance Criteria:
- Checkout form shows ≤4 fields on initial load
- Auto-populate customer address from profile
- Single-tap payment method selection
- Dependencies: Customer profile API (Req 4)
Conflicts: Shipping options field vs. minimized form goal — recommend conditional display
What's Included
- SKILL.md instruction file with decomposition framework and stakeholder validation checklist:
- Requirements Decomposition Template: structured worksheet for breaking down complex requirements
- Acceptance Criteria Checklist: SMART criteria validation framework (Specific, Measurable, Achievable, Relevant, Testable)
- Dependency Mapping Canvas: visual format for requirements relationships and conflict detection
- Stakeholder Validation Worksheet: questions to surface hidden assumptions and confirm understanding
Who It's For
- Business Analysts — structuring ambiguous requirements into testable components
- Product Managers — decomposing epics and features before engineering handoff
- Solutions Architects — breaking down complex RFP requirements into implementation tasks
- Scrum Masters/Agile Leads — converting business language into actionable user stories
- Technical Project Managers — validating requirement completeness and dependency clarity
Best For
- Decomposing high-level business requests into granular, testable requirements
- Generating acceptance criteria for development teams and QA
- Creating Requirements Documents (BRD, SRS) from stakeholder input
- Mapping dependencies and flagging requirement conflicts early
- Validating assumptions with stakeholders before development begins







