adom-plan — Exhaustive Plan Review

@@ -10,7 +10,7 @@ End-to-end planning pipeline: expand a sketch into a detailed plan, then stress-  1. **Phase 0** — Locate the plan (plan file, file path argument, or conversation context) 2. **Phase 0.5** — Expand the plan via a built-in Opus expansion agent-3. **Phase 1** — Fetch platform context (wiki catalog, installed skills, recent commits, existing plans)+3. **Phase 1** — Fetch platform context via the `adom-wiki` CLI (wiki catalog, installed skills, recent wiki activity, existing plans) 4. **Phase 2** — Launch 6 adversarial debate agents in parallel (3 pairs):    - Architecture: Opus advocate vs Sonnet challenger    - Implementation: Sonnet roadmap-builder vs Opus gap-finder

@@ -48,16 +48,24 @@ Gather three kinds of context so agents argue about reality, not assumptions.  #### 1a. Platform catalog (what already exists) +Use the canonical `adom-wiki` CLI (never raw HTTP or a deprecated host). The+`discover` pillar lists what's on wiki.adom.inc; run a broad `popular` pull for+the catalog and targeted `search` for anything the plan sounds adjacent to:+ ```bash-curl -s https://wiki.adom.inc/api/v1/pages | python3 -c "+adom-wiki discover popular --limit 60 --json 2>/dev/null | python3 -c " import sys, json-data = json.load(sys.stdin)-pages = data.get('pages', data) if isinstance(data, dict) else data-for p in pages:-    print(f\"[{p['type']}] {p['slug']} — {p.get('brief','')[:120]}\")+d = json.load(sys.stdin)+for p in d.get('data', {}).get('results', d.get('data', [])):+    print(f\"[{p.get('type','?')}] {p.get('owner','')}/{p['slug']} — {p.get('brief','')[:110]}\") " ``` +```bash+# Targeted: swap the query for the plan's domain (e.g. 'task tracker', 'auth').+adom-wiki discover search --query "<plan domain keywords>" --limit 20 --json 2>/dev/null+```+ ```bash ls ~/.claude/skills/ 2>/dev/null | head -50 ```@@ -65,24 +73,20 @@ ls ~/.claude/skills/ 2>/dev/null | head -50 #### 1b. Prior art (what's been tried before)  ```bash-gh api repos/adom-inc/gallia/commits?per_page=15 2>/dev/null | python3 -c "-import sys, json-for c in json.load(sys.stdin):-    print(f\"{c['sha'][:8]} {c['commit']['author']['name']}: {c['commit']['message'].split(chr(10))[0][:80]}\")-"+adom-wiki status --json 2>/dev/null | head -60 ```  ```bash ls /home/adom/.claude/plans/ 2>/dev/null-ls /home/adom/project/gallia/plans/ 2>/dev/null+ls /home/adom/project/*/plans/ 2>/dev/null ```  #### 1c. Compile the context block  Build a **Context Block** (under 3000 chars) containing:-- Wiki apps/skills grouped by type (one line each)+- Wiki apps/skills grouped by type (one line each), from `adom-wiki discover` - Installed Claude Code skills (names only)-- Recent gallia commits (last 15, one-liners)+- Recent Adom Wiki activity (`adom-wiki status` open-work rollup, one-liners) - Any existing plan files found  This block is prepended to every agent prompt.

@@ -145,7 +145,8 @@ For each major design decision: 4. **Blast radius** — If this design decision is wrong, how much do we have to    rewrite? Rate: CONTAINED / MODERATE / CATASTROPHIC. 5. **Prior art conflict** — Does this contradict patterns already established-   in the gallia codebase or Adom platform? Check the recent commits.+   on the Adom platform (wiki.adom.inc packages, existing Adom apps)? Check+   the context block's platform catalog.  ## Scoring 

@@ -1,6 +1,6 @@ {   "slug": "adom-plan",-  "version": "1.1.0",+  "version": "1.2.0",   "type": "skill",   "description": "Expand a sketch into a full plan, then stress-test it with 6+ adversarial debate agents (Opus vs Sonnet pairs across architecture, implementation, and security) plus a red-team consensus attack and a scored synthesis. The plan half of the plan->build pipeline; pairs with three-musketeers.",   "tags": ["planning", "multi-agent", "adversarial", "claude-code", "skill"],