mz-design

flowchart LR
    A["/deep-research"]:::base --> B["/build"]:::pipe
    B --> C["/verify"]:::pipe
    C --> D["/review-branch"]:::base
    classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
    classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37

1. /deep-research — survey trade-offs, cite references, pick an approach
2. /build — research → plan (approval gate) → parallel code → review → test
3. /verify — lint + types + tests + coverage, diagnose failures
4. /review-branch — independent final pass before opening the PR

flowchart LR
    A["/debug"]:::pipe --> B["/blast-radius"]:::pipe
    B --> C["/investigate"]:::pipe
    C --> D["/polish"]:::pipe
    classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37

1. /debug — reproduce → regression test → diagnose → fix → verify
2. /blast-radius — map every caller, test, and type at risk of the patch
3. /investigate — prove or disprove "does the same race exist on the refund path" without touching code
4. /polish — fix-test-review loop until the criteria are met

flowchart LR
    A["/init-rules"]:::base --> B["/explain"]:::pipe
    B --> C["/audit"]:::pipe
    C --> D["/blast-radius"]:::pipe
    classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
    classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37

1. /init-rules — install curated coding rules for the detected languages
2. /explain — multi-angle walkthrough with Mermaid diagrams of the module
3. /audit — ranked list of landmines and tech-debt hotspots
4. /blast-radius — know what shatters before the first refactor commit

flowchart LR
    A["/audit"]:::pipe --> B["/investigate"]:::pipe
    B --> C["/debug"]:::pipe
    C --> D["/review-branch"]:::base
    classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
    classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37

1. /audit — prioritized vulnerabilities with file:line evidence
2. /investigate — verify top critical findings, drop false positives
3. /debug — TDD-style fix anchored on a regression test
4. /review-branch — catch any fallout the fix introduced elsewhere

flowchart LR
    A["/brainstorm"]:::creative --> B["/expert"]:::creative
    B --> C["/design-document"]:::design
    C --> D["/build"]:::pipe
    classDef creative fill:#fbefff,stroke:#8250df,color:#8250df
    classDef design fill:#ffebf0,stroke:#bf3989,color:#bf3989
    classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37

1. /brainstorm — 5 lens personas → parallel ideation → vote-to-consensus
2. /expert — Delphi critique (3 rounds) with dedicated report writer
3. /design-document — draft → 4-critic loop → WCAG 2.2 AA hard gate
4. /build — plan → code → review → test against the approved spec

flowchart LR
    A["/lead-gen"]:::outreach --> B["/deep-research"]:::base
    B --> C["/brainstorm"]:::creative
    classDef outreach fill:#fff1e5,stroke:#bc4c00,color:#bc4c00
    classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
    classDef creative fill:#fbefff,stroke:#8250df,color:#8250df

1. /lead-gen — strategy → source research → scout → enrich → score → report
2. /deep-research — domain context to ground outreach in current regulation
3. /brainstorm — multi-lens positioning ideas tied back to the lead-gen report