brainstorm

Run a requirements discovery session. Focus: $ARGUMENTS (whole product if empty). Precondition: .saas-factory/ exists (else tell the user to run /saas-factory:init).

Delegate the heavy lifting to the saas-factory:requirements-analyst subagent in rounds, keeping this session light:

0. Round 0 — context dump (preferred): invite the user to BRAIN-DUMP everything they're thinking — messy is fine. Spawn the analyst to EXTRACT scope surfaces, epics, implied domains, platforms, constraints, taste signals, and inferred needs edges from the dump. Then round 1 covers only what the dump left open — never re-ask what was already said.

1. Round 1 — shape: analyst asks about users, core jobs-to-be-done, and success criteria; proposes an epic list. Present epics for user approval/edits.

2. Round N — drill: for ONE epic at a time, spawn the analyst with only that epic charter; it interviews, writes REQ files, registers them via bin/sf add, and returns counts + open questions (never full REQ bodies).

3. After each epic: show bin/sf counts, relay the analyst's open questions, ask whether to approve the batch (bin/sf set REQ-… approved per confirmed id, or approve-all for the epic), continue to the next epic, or stop.

4. Finish — phase roadmap sketch (cheap, before any deep planning): from the approved REQs + bin/sf frontier, present a one-screen sketch — phase titles and WHAT EACH DEMO WILL SHOW (no tasks) — so the user sees the whole demo trajectory and can redirect NOW, while it costs nothing. Only phase 1 gets planned in detail next.

Rules for this session: keep only ids/titles/counts in context; the user can stop anytime and resume later — everything is on disk. End with counts and the next step: /saas-factory:plan EPIC-###.