Capability node
Requirement Planning
Turn a fuzzy goal into a concrete set of requirements the agent can act on.
Why this capability exists
Agents fail when the goal is vague. Requirement planning converts "make me a site" into scope, constraints, target users, and acceptance criteria before any code is written.
Input
- A one-line goal or problem statement
- Known constraints (budget, time, platform, audience)
- Existing assets or content
Output
- Scoped requirement list with priorities
- Out-of-scope list
- Success criteria the build can be measured against
Risks
- Scope creep when requirements are written as feature wish lists
- Confusing user wants with user needs
- Skipping the step entirely and letting the agent improvise
Acceptance criteria
- Every requirement is testable and either in scope or explicitly out of scope
- The team agrees on what "done" means before execution starts