1. Full spec co-author Interactive agent that walks you through writing/refining any spec doc (charter, PRD, ADD, WBS, roadmap). Reads existing specs for context, asks clarifying questions, drafts sections.
2. Gap analyzer Reads all existing specs and code, then reports what's missing or stale — incomplete sections, specs that don't match the code, work packages with no spec coverage.
3. Single-doc drafter Takes a doc type as argument (e.g., /spec-buddy prd) and drafts that specific document from scratch or updates an existing one, pulling context from other specs.
4. Spec reviewer Reviews an existing spec doc for completeness, consistency with other specs, and actionability. Outputs a checklist of issues to fix.

● Done. Here's what /spec-buddy does now:

  One command, three agents:                                                                            
  Agent: Drafter                                                                                     
  Role: Writes/refines spec docs
  When it runs: draft prd, full prd
  ────────────────────────────────────────
  Agent: Reviewer
  Role: Audits for completeness, consistency, actionability
  When it runs: review prd, review all, after every draft
  ────────────────────────────────────────
  Agent: Gap Analyzer
  Role: Finds missing specs, code↔spec drift, cross-spec inconsistencies
  When it runs: gaps, full prd

  Usage examples:
  - /spec-buddy draft prd — Drafter writes, Reviewer checks the result
  - /spec-buddy review all — Reviewer runs on every spec in parallel
  - /spec-buddy gaps — Gap Analyzer does a full audit
  - /spec-buddy full add — Gap Analyzer + Reviewer diagnose → Drafter fixes → Reviewer re-checks 

the specs agents come back to me if and only if they detected multiple possible implementation of the specs, becasue calude code is only allowed to follow the specs