deep-designlisted

# Deep Design Pipeline ## Overview A 7-phase orchestration pipeline that turns a user's feature idea into a reviewed, implementation-ready OpenSpec proposal. Inspired by the LLM Council pattern: agents analyze independently, then cross-critique each other's outputs, conflicts are resolved using confidence scoring (not hard rules), and a sanity-check gate catches design flaws before expensive spec-writing begins. **Pipeline at a glance:** ``` User describes feature │ ▼ ┌───────────────────────────────┐ │ Phase 1: PARALLEL ANALYSIS │ │ │ │ ┌─────────┐ ┌──────────┐ │ │ │ Metis │ │ Oracle │ │ │ │ (scope, │ │ (arch, │ │ │ │ risks, │ │ design, │ │ │ │ phases) │ │ MVA) │ │ │ └────┬────┘ └────┬─────┘ │ │ └──────┬───────┘ │ └──────────────┼────────────────┘ ▼ ┌──────────────────────────────────┐ │ Phase 1.5: CROSS-CRITIQUE │ │ │ │ Metis reads Oracle's output → │ │ critiques architecture │ │ Oracle reads Metis's output → │ │ rebuts scope concerns │ │ (parallel, anonymized roles) │ └──────────────┬───────────────────┘ ▼ ┌──────────────────────────────┐ │ Phase 2: SYNTHESIS │ │ Confidence-scored conflict │ │ resolution, design brief │ └──────────────┬───────────────┘ ▼ ┌──────────────────────────────┐ │ Phase 2.5: MOMUS SANITY │ │ Lightweight early rev