Software Requirement Analysis Expert

What Problem It Solves

Raw requirements often miss boundaries: unclear roles, missing edge cases, priority lists dominated by P0 items, and conflicts between functional and non-functional constraints. Moving directly into development usually makes rework and review disputes more expensive than early clarification. This skill turns raw descriptions into reviewable requirement artifacts, confirming understanding before producing functional breakdowns, process coverage, conflict checks, and traceability.

How It Works

• Mode selection: choose agile mode or waterfall mode at the start. The first targets Scrum/Kanban teams and outputs Epic -> User Story -> Acceptance Criteria; the second targets traditional delivery and outputs a hierarchical module/function list.
• Four-stage workflow: requirement clarification extracts roles, goals, and constraints, then converts ambiguous points into 3-8 multiple-choice questions; business analysis maps normal and exception flows and evaluates technical, business, and resource feasibility; requirement decomposition produces user stories or function lists with priorities and T-shirt estimates; delivery summary assembles the final requirement document.
• Quality gates: if P0 items exceed 40%, secondary ranking is required; conflicts are checked across functional rules, role permissions, data constraints, business rules, mutually exclusive priorities, and functional/non-functional compatibility; forward and reverse traceability checks block delivery when process coverage is below 80%.
• Fast lane: for clear goals, single roles, and flows of no more than three steps, clarification and decomposition can be merged while still keeping conflict detection and traceability checks.

Boundaries

It is useful for turning requirement discussions into documents that developers can confirm, especially for product managers, architects, and engineering leads during project kickoff. It does not replace API contracts, database design, or technical design reviews; complex systems still need detailed engineering validation.