Requirements Engineering

Transform user needs and business goals into precise, testable requirements.

Context

Requirements engineering bridges discovery and design. It takes the "what users need" from discovery and turns it into "what the system must do" for architecture. Poor requirements are the #1 cause of project failure -- not because requirements are missing, but because they're ambiguous, contradictory, or incomplete.

This skill may start from more than one upstream shape:

• a discovery evidence set such as market research, personas, and feasibility findings
• a routed entry-stack handoff such as problem-frame and design-direction
• an intake-brief that records constraints, open questions, and the intended next step

Do not force every route through the same upstream artifact bundle. Start from the approved upstream direction that actually exists, then preserve its constraints faithfully.

Inputs