Requirements Analysis
Diagnose requirements problems and guide discovery of real needs and constraints
Install
npx skills add jwynia/agent-skills --skill requirements-analysisgit clone --depth 1 https://github.com/jwynia/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/tech/development/architecture/requirements-analysis ~/.claude/skills/requirements-analysisPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Requirements Analysis: From Vague Intent to Validated Needs
You diagnose requirements-level problems in software projects. Your role is to help solo developers distinguish stated wants from underlying problems, discover real constraints, and avoid premature solution thinking.
## Core Principle
**Requirements are hypotheses about what will solve a problem. The goal is not to document requirements but to discover whether they address the actual problem.**
## The States
### State RA0: No Problem Statement
**Symptoms:**
- Starting with "I want to build X" (solution, not problem)
- Can't articulate who has what problem
- "Everyone needs this" reasoning
- Feature list without problem grounding
- Copying existing solutions without understanding why they exist
**Key Questions:**
- What happens if this doesn't exist? Who suffers?
- What are people (or you) doing today instead?
- What triggered you thinking about this now?
- If you're the user, what specific frustration led here?
**Interventions:**
- Jobs-to-be-Done self-interview: "When I [situation], I want to [motivation], so I can [outcome]"
- Problem archaeology: trace the origin of the idea back to a specific frustration
- "Five users" test: name 5 specific people who would benefit (even if one is yourself)
- Use Problem Statement Brief template
---
### State RA1: Solution-First Thinking
**Symptoms:**
- Requirements describe implementation ("needs a database", "should use React")Details
- Skill name
requirements-analysis- Repository
- jwynia/agent-skills
- Path
skills/tech/development/architecture/requirements-analysis/SKILL.md- Repo updated
- 24 February 2026
FAQ
What does the Requirements Analysis skill do?
Diagnose requirements problems and guide discovery of real needs and constraints
How do I install the Requirements Analysis skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jwynia/agent-skills --skill requirements-analysis. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Requirements Analysis popular?
It lives in jwynia/agent-skills, which has 191 GitHub stars and 24 forks.
Related skills
Abstract Strategy
191jwynia/agent-skills
Design abstract strategy games with perfect information, no randomness, and strategic depth. Use when designing a board game, exploring abstract strategy games, brainstorming game mechanics, or evaluating game balance. Keywords: board game, game design, strategy, mechanics, balance.
Adaptation Synthesis
191jwynia/agent-skills
Synthesize new works from extracted functional DNA documents. Use when adapting a source work to a new context, when combining multiple source extractions, or when generating variations that preserve function while changing form.
Agent Bootstrap
191jwynia/agent-skills
Bootstrap agentic development environment from agent.toml manifest
Restful Hateoas
228pproenca/dot-skills
RESTful API design guidelines following the Richardson Maturity Model through to Level 3 (HATEOAS) for Ruby on Rails. This skill should be used when designing, building, reviewing, or refactoring REST APIs to ensure proper resource modeling, HTTP method semantics, hypermedia controls, content negotiation, and API evolvability. Triggers on tasks involving API controllers, serializers, routing, link relations, pagination, error handling, or HTTP caching in Rails.
Refactor
228pproenca/dot-skills
Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles (formerly refactoring). This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.
Ruby Optimise
228pproenca/dot-skills
Ruby performance optimization guidelines. This skill should be used when writing, reviewing, or refactoring Ruby code to ensure optimal performance patterns. Triggers on tasks involving object allocation, collection processing, ActiveRecord queries, string handling, concurrency, or Ruby runtime configuration.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.