Requirements Analysis
Requirements Analysis guides you through discovering actual problems versus assumed solutions, clarifying vague needs into testable requirements, and surfacing hidden constraints before they derail your project. It provides diagnostic states, targeted questions, and structured exercises to move from solution-first thinking to validated requirements.
Requirements Analysis helps you systematically uncover real project needs and validate constraints before development begins.
AI-generated summary based on this skill's SKILL.md
Install
jwynia/agent-skills/requirements-analysis · repository language: TypeScript
git clone https://github.com/jwynia/agent-skills
cp -r agent-skills ~/.claude/skills/requirements-analysisgenerated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
npx skillfed install jwynia/agent-skills/requirements-analysisFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I structure requirements for traceability?
Requirements Analysis helps you organize requirements so each one links to stakeholder needs, design decisions, and test cases throughout delivery. Structure them with unique identifiers, clear ownership, priority levels, and acceptance criteria. This traceability lets you track which requirements made it into the final product and catch gaps before implementation begins.
What are requirements elicitation techniques?
Requirements Analysis teaches frameworks for drawing out real needs from stakeholders. Common techniques include interviews, workshops, observation, prototyping, and document review. The skill guides you to ask targeted questions that uncover hidden constraints, surface conflicts between stakeholder groups, and distinguish actual problems from proposed solutions.
How to analyze project requirements systematically?
Requirements Analysis walks you through discovering actual problems versus assumed solutions, clarifying vague needs into testable requirements, and surfacing hidden constraints before they derail your project. Use diagnostic states, targeted questions, and structured exercises to move from solution-first thinking to validated requirements that all stakeholders can verify.
How do I identify gaps and conflicts in requirements?
Requirements Analysis helps you spot missing pieces and competing priorities by analyzing requirements against stakeholder goals, business rules, and technical constraints. Map functional versus non-functional needs, cross-check coverage against scope, and facilitate conversations between stakeholder groups to resolve conflicts early and align on priorities.
What's the difference between functional and non-functional requirements?
Requirements Analysis clarifies that functional requirements describe what the system must do—features, workflows, data handling. Non-functional requirements specify how well it must perform—speed, reliability, security, usability, scalability. Both matter equally; missing non-functional requirements often causes late-stage rework and deployment failures.
How do I ensure all stakeholder needs are captured?
Requirements Analysis emphasizes validating requirements before design and implementation. Engage all stakeholder groups early, document their needs in their own words, then translate into testable requirements. Use checklists and traceability matrices to confirm coverage, and hold sign-off reviews so stakeholders confirm their needs are represented accurately.