Requirements Analysis
Turn fuzzy product asks into testable functional and non-functional requirements with gaps and edge cases surfaced before build.
Overview
Requirements Analysis is an agent skill most often used in Validate (also Build pm, Ship testing) that clarifies scope by classifying requirements, applying Five Whys and SMART checks, and validating testability.
Install
npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill requirements-analysisWhat is this skill?
- Splits functional, non-functional, and constraint requirement types
- Five Whys worked example to expose underlying needs (e.g., export vs dashboard)
- SMART criteria checklist for ambiguous requirements
- Edge-case analysis prompts (empty data, scale, offline, permissions)
- Validation gates: testable, achievable, and aligned with goals
- Five Whys analysis technique with worked export-to-dashboard example
- SMART requirement criteria (five dimensions)
- Requirement validation checklist including testability and achievability
Adoption & trust: 1 installs on skills.sh; 97 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You have a pile of feature ideas or a vague ticket and cannot tell what is essential, measurable, or technically constrained.
Who is it for?
Solo founders and indie PMs framing an MVP slice, refactor, or integration before writing plans or code.
Skip if: Fully signed-off specs that already passed formal sign-off and only need line-by-line implementation with no open questions.
When should I use this skill?
User needs to analyze or refine product requirements, clarify scope, identify gaps, or validate requirements using types and analysis techniques.
What do I get? / Deliverables
You produce refined functional, non-functional, and constraint requirements with edge cases noted and a validation checklist ready for design or implementation planning.
- Categorized functional, non-functional, and constraint requirements
- Gap and edge-case notes with SMART-aligned revisions
- Validation checklist marking testable and achievable items
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate / scope is the canonical shelf because the skill clarifies, refines, and validates requirements before implementation commitments. Scope subphase matches gap identification, SMART tightening, and separating real needs from stated feature requests.
Where it fits
Rewrite a stakeholder 'export button' ask into the real need—a regional performance view—before prototype work.
Split epics into testable functional and NFR statements with explicit AWS or auth constraints.
Derive acceptance cases from edge-case analysis (no data, permission denied).
Sanity-check whether a competitor-parity feature list aligns with measurable goals before validating build cost.
How it compares
Use for structured requirement refinement, not automated test generation or deployment checklists.
Common Questions / FAQ
Who is requirements-analysis for?
Builders and solo PMs who need to clarify scope, find gaps, and make requirements testable before agents or developers implement.
When should I use requirements-analysis?
Use in Validate when scoping an MVP or pricing-related capability, in Build pm when breaking down epics, and in Ship testing when deriving acceptance criteria from ambiguous asks.
Is requirements-analysis safe to install?
It is analysis-only guidance; review the Security Audits panel on this Prism page for the hosting repo before install.
SKILL.md
READMESKILL.md - Requirements Analysis
# Requirements Analysis ## Requirement Types ### Functional Requirements What the system should DO. - "Users can log in with email and password" - "System sends order confirmation email" ### Non-Functional Requirements How the system should BEHAVE. - Performance: "Page loads in < 2 seconds" - Security: "Passwords stored with bcrypt" - Scalability: "Supports 10,000 concurrent users" ### Constraints Limitations on the solution. - "Must use existing authentication system" - "Must run on AWS" ## Analysis Techniques ### Ask "Why?" Five Times Uncover the real requirement. ``` Requirement: "Add export to Excel button" Why? → "Users need to share reports" Why? → "Finance reviews monthly sales" Why? → "They compare against targets" Why? → "To identify underperforming regions" Real Need: Regional performance dashboard ``` ### SMART Criteria Requirements should be: - **S**pecific: Clear and unambiguous - **M**easurable: Can verify completion - **A**chievable: Technically feasible - **R**elevant: Aligned with goals - **T**ime-bound: Has deadline ### Edge Case Analysis - What happens with no data? - What happens with too much data? - What if the user is offline? - What if permissions are denied? ## Requirement Validation - [ ] Is it testable? - [ ] Is it achievable? - [ ] Is it necessary? - [ ] Is it consistent with other requirements? - [ ] Is it complete? - [ ] Is the priority clear? ## Documenting Requirements ```markdown **REQ-001**: User Authentication **Description**: Users must authenticate to access the system. **Acceptance Criteria**: 1. Given valid credentials, user gains access 2. Given invalid credentials, user sees error 3. After 5 failed attempts, account is locked **Priority**: Must Have **Dependencies**: REQ-002 (User Management) ```