
Requirements Synthesis & Validation
Transform stakeholder feedback into validated, conflict-free requirement documents
What You Can Do
You can take raw stakeholder feedback—interview notes, emails, meeting transcripts, fragmented documents—and systematically synthesize them into formal, validated requirement statements. Claude identifies conflicting expectations, flags missing information, eliminates ambiguity, and produces a requirements baseline ready for development handoff without constant clarification requests.
Features
Extract and organize conflicting perspectives from multiple sources into a unified view
Identify contradictory requirements and propose resolution paths with stakeholder alignment
Flag missing acceptance criteria, edge cases, and undefined scope before development begins
Generate testable requirement statements with clear success criteria and acceptance tests
Cross-check requirements for completeness, consistency, and feasibility against constraints
Link requirements to stakeholders and business objectives for change control and scope justification
Rewrite vague or colloquial feedback as precise, measurable requirement language
Example Output
Input: Raw interview notes from 3 stakeholders with conflicting views on user authentication scope.
Output:
REQUIREMENT R-AUTH-001: User Login
- Description: System shall support single-sign-on via corporate LDAP
- Acceptance Criteria:
✓ Users authenticate within 3 seconds
✓ Failed login attempts locked after 5 tries
✓ Session timeout after 30 minutes of inactivity
- Conflicting Input: Stakeholder A wants OAuth, Stakeholder B wants LDAP → RESOLVED: LDAP primary with OAuth phase 2
- Status: VALIDATED with Finance and IT
Gap Identified: No requirement for password reset flow or multi-factor authentication—flagged for stakeholder decision.
What's Included
- SKILL.md: Complete requirements synthesis workflow and phase-by-phase instructions
- Stakeholder Consolidation Template: Structure for organizing raw input by source and theme
- Conflict Resolution Framework: Decision matrix for resolving contradictory requirements with justification
- Requirements Statement Checklist: Validation criteria for testability, clarity, and acceptance condition completeness
- Gap Identification Worksheet: Structured list of missing information to surface before handoff
Who It's For
- Business Analysts — Transform raw stakeholder feedback into formal specifications for development teams
- Product Managers — Consolidate feature requests and validate scope before engineering handoff
- Project Managers — Create requirements baseline for change control and scope justification to executives
- Systems Analysts — Document conflicting system requirements and resolve interdependencies
- Process Improvement Leads — Synthesize process feedback from multiple departments into documented workflows
Best For
- Consolidating feedback from 3+ stakeholders with conflicting expectations
- Converting unstructured interview notes into testable requirement statements
- Identifying gaps and ambiguities before development begins
- Resolving scope conflicts and documenting justification for executive alignment
- Creating requirements baselines for regulatory compliance or change control tracking







