Requirements Specification

Background & Use Cases

When you have nothing but a vague system idea — like "I want to build a consumer payment service platform" — but can't articulate what specific features to build, what scenarios exist, or how data flows, this skill helps you turn fuzzy ideas into clarity through structured dialogue. It won't make decisions for you, but through iterative questioning, it helps you uncover genuine business requirements and produce a usable requirements specification.

Input & Output

You need to provide: A vague system/feature concept, even just one sentence. For example, "Build a consumer payment service platform supporting multi-app management."

You will receive: A structured requirements specification including: root purpose statement (why build it), complete descriptions of core business scenarios (who participates, what happens, how exceptions are handled), scenario priority ranking, and a checklist of authentication/authorization/audit/compliance constraints.

Process Overview

Starting from your one-sentence concept, the Agent will first work with you to discover the system's root purpose and identify key stakeholders. Once the direction is confirmed, it helps you list business scenarios one by one, then deep-dive into each: who participates, what triggers it, what the normal flow looks like, how exceptions are handled, and what data is involved. After scenarios are fully explored, it helps you prioritize them, define boundaries (In/Out/TBD/Won't), and finally scan for authentication/authorization/audit/compliance constraints to produce a structured requirements specification.