mb-analysis - Optional Analysis before PRD

• What it does: adds a lightweight Analysis phase before /prd when the idea is vague, unstable, or needs explicit product framing.
• Use /analysis when: you need a router that inspects current Memory Bank state and recommends the next command.
• Use /brainstorm when: the idea is raw and needs facilitated ideation. The AI acts as a coach; the user's product intent and choices remain the source of truth.
• Use /brief when: the concept is clear enough to produce a concise Product Brief, or after a brainstorming report exists.
• Output: optional artifacts under .memory-bank/analysis/.

Analysis is optional. Raw PRD text or an existing external PRD should pass /constitution first when project principles are not ratified/partial, then be normalized and checked through /write-prd, producing .memory-bank/prd.md with type: prd, clarification_status: complete, and constitution_checked: true; then /spec-init prepares the lightweight SDD route map before /prd decomposes it. After /prd, /spec-design is mandatory but adaptive: simple T0/T1 scope may record a minimal backbone, while shared/T2/T3 scope records the needed domain/model/contracts/state/security/runtime design. Brownfield projects should map the current codebase first with /map-codebase before planning deltas.

/brief creates the Product Brief as the input contract for /constitution and /write-prd. It is not a PRD, backlog, research report, or marketing document.

The normal planning path is:

/analysis -> /brief -> /constitution -> /write-prd -> /spec-init -> /prd -> /spec-design -> /spec-improve FT-<NNN> -> /prd-to-tasks FT-<NNN>

Use /brainstorm before /brief when the idea is raw. /constitution should read the Product Brief when present and run the governing-principles interview; if the user explicitly skips it, downstream PRD work may continue with framework-default/skipped principles.