Skip to content
APEX

Step 1 — Requirements

Purpose

Section titled “Purpose”

Capture the functional, non-functional, compliance, and budget constraints for a new Azure workload through an interactive conversation. Step 1 also produces the empty sku-manifest.{json,md} artifact that downstream steps mutate.

Agent

Section titled “Agent”

02-Requirements

Invocation

Section titled “Invocation”
Invoke: Ctrl+Shift+A → 02-Requirements
Output: agent-output/{project}/01-requirements.md
        agent-output/{project}/sku-manifest.{json,md} (rev 1)

What gets captured

Section titled “What gets captured”
  • Functional requirements — what the system does
  • Non-functional requirements — performance, availability, security, scale targets
  • Compliance requirements — regulatory, organizational, residency
  • Budget constraints — monthly cap, cost guardrails
  • User-pinned SKUs (optional) — anything the user has already decided

Review

Section titled “Review”

1 × comprehensive adversarial pass by challenger-review-subagent is mandatory. Findings land in challenge-findings-01-requirements.json and must be triaged before Step 2.

Hand-off

Section titled “Hand-off”

The Orchestrator routes context to Step 2 — Architecture once the user approves the requirements artifact.

See also

Section titled “See also”