requirement-analyzer_skill

Overview

This skill analyzes and documents software requirements using a technology-agnostic, repeatable approach. It decomposes raw inputs into functional, non-functional and constraint categories and generates clear, testable specification artifacts. The output is designed for traceability, validation and integration with project workflows.

How this skill works

It ingests stakeholder inputs, documents and research, then classifies each item by type, priority and dependencies. The skill applies user-story and acceptance-criteria templates, SMART quality checks, and MoSCoW/Kano prioritization to produce requirement specs, traceability matrices, and acceptance criteria documents. It also generates achievement indicators and validation protocols to drive implementation and evaluation.

When to use it

• At project kickoff to translate stakeholder needs into structured requirements
• When refining product roadmaps or preparing a release backlog
• Before design or implementation to reduce ambiguity and technical risk
• When compliance, security or performance constraints must be formalized
• During vendor selection or procurement to define measurable acceptance criteria

Best practices

• Engage all relevant stakeholders early and validate assumptions with prototypes
• Use measurable acceptance criteria and SMART checks for every requirement
• Assign priorities with MoSCoW or Kano and document trade-offs
• Maintain traceability from source to test cases and implementation
• Iterate requirements through review/inspection cycles and record decisions

Example use cases

• Create a requirement specification for a web or mobile application including FRs, NFRs and constraints
• Produce acceptance criteria and achievement indicators for a new API rollout
• Map stakeholder influence and communications for regulatory or enterprise projects
• Perform gap analysis and risk assessment before a large refactor or migration
• Generate a traceability matrix to support testing and compliance audits