04-requirements-analysis

Installation
SKILL.md

Requirements Analysis Skill

Use When

  • classifying, reconciling, prioritising, and testing the feasibility of elicited requirements; use requirements-validation for the independent pre-baseline review.
  • Use this procedure when the required source artefacts are available and Analysed requirements set and conflict log is the next lifecycle deliverable.

Do Not Use When

  • Use requirements-validation when that neighbouring route owns the decision or deliverable.
  • Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.

Required Inputs

Artefact Source or provider Required? Behaviour when missing
Elicitation evidence, goals, stakeholder priorities, business rules, and constraints Elicitation outputs and project context Yes Stop the affected step, name the missing source, and return only a qualified gap record.
Installs
1
GitHub Stars
8
First Seen
Sep 27, 2026