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
Decision gist · record as of 2026-02-24
Requirements Analysis helps you systematically uncover real project needs and validate constraints before development begins. 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.
Use it when
- Requirements Analysis teaches frameworks for drawing out real needs from stakeholders.
- Requirements Analysis walks you through discovering actual problems versus assumed solutions.
Install
jwynia/agent-skills/requirements-analysis · repository language: TypeScript
generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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.
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Systematically analyze and document project requirements from stakeholders”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
System Design helps you translate validated requirements into sound architecture by diagnosing common pitfalls: missing requirements clarity, under- or over-engineering, overlooked integration points, and unexamined risky decisions. Work through six diagnostic states to identify where your design thinking breaks down, then apply targeted interventions—data flow mapping, component identification, integration checklists, and architecture decision records—to reach a validated design ready for implementation.
Architecture Decision helps you systematically evaluate design choices, document trade-offs, and select appropriate patterns for your context. It provides frameworks for creating Architecture Decision Records, assessing technical debt, and balancing quality attributes like performance, scalability, and maintainability.
This skill guides you through GitHub-driven agile setup and troubleshooting, from CLI installation through backlog management and pull request discipline. It helps you establish healthy practices around issues, branches, and context preservation—ensuring your work stays traceable and your team stays aligned.
prd converts feature requests into structured Product Requirements Documents, delivering actionable outcomes and concrete decisions. It's designed for executable documentation tasks, not high-level strategy or planning discussions.
Project Structure analyzes and explains your project's architecture, helping you understand how your codebase is organized. It delivers concrete, actionable insights into your project layout rather than abstract planning or strategy.
This skill covers foundational architectural approaches for structuring software systems at scale. It walks through monolithic, microservices, event-driven, serverless, clean, and domain-driven architectures—each with use cases, trade-offs, and implementation guidance. A decision tree helps you pick the right pattern based on team size, deployment autonomy, audit requirements, and load variability.
More skills game-development (MIT)