Files
msd-core/.planning/ROADMAP.md
Lex Christopherson e3d39c09e6 docs(04): create phase 4 plans for semantic intelligence
Phase 4: Semantic Intelligence & Scale
- 3 plans in 2 waves
- Wave 1: 04-01 SQLite graph layer (sql.js WASM)
- Wave 2: 04-02 Rich summary generation, 04-03 Semantic entity generation

Key additions:
- sql.js for zero-native-deps graph database
- @anthropic-ai/sdk for Claude API entity generation
- Recursive CTEs for dependency queries ("what uses X")
- Graph-backed summaries with hotspots

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-20 09:39:22 -06:00

2.7 KiB

Roadmap: v1.9.0 Codebase Intelligence System

Goal: Make GSD feel intelligent and automagical in how it navigates and understands both greenfield and brownfield projects.

Phases: 4 (3 complete, 1 remaining)


Current Milestone: v1.9.0

Phase 1: Foundation & Learning ✓

Goal: Establish index schema and incremental learning via PostToolUse hook Status: Complete Plans: 2/2

Phase 2: Context Injection ✓

Goal: Inject codebase awareness into every session via SessionStart hook Status: Complete Plans: 2/2

Phase 3: Brownfield & Integration ✓

Goal: Deep analysis command for existing codebases, workflow integration Status: Complete Plans: 3/3

Phase 4: Semantic Intelligence & Scale

Goal: Transform syntax-only indexing into semantic understanding with graph-based relationships

Depends on: Phase 3 Plans: 3 plans

Plans:

  • 04-01-PLAN.md — SQLite graph layer with sql.js (Wave 1)
  • 04-02-PLAN.md — Graph-backed rich summary generation (Wave 2)
  • 04-03-PLAN.md — Semantic entity generation via Claude API (Wave 2)

Wave Structure:

  • Wave 1: 04-01 (SQLite foundation)
  • Wave 2: 04-02, 04-03 (parallel - both depend only on 04-01)

Why this phase:

  • Current system provides "2-3 ls commands worth of information" (Claude's own assessment)
  • Missing: what files actually DO, who uses them, blast radius of changes
  • Senior engineers at top companies need real intelligence, not file counts

Delivers:

  • SQLite graph layer (sql.js - zero native deps) for relationship queries
  • Entity-based semantic documentation (Claude writes understanding, not just syntax)
  • Semantic /gsd:analyze-codebase that creates initial entities
  • Rich summary generation from accumulated semantic knowledge

Requirements:

  • INTEL-04: Entity files capture semantic understanding (purpose, what exports do)
  • INTEL-05: Relationships queryable ("what uses this file?", "blast radius")
  • INTEL-06: /gsd:analyze-codebase creates initial entity docs via Claude
  • INTEL-07: Summary reflects accumulated semantic knowledge

Success Criteria:

  1. Claude can answer "what uses src/lib/db.ts?" from SessionStart context
  2. Summary includes file purposes, not just file counts
  3. Transitive dependency queries work (blast radius)
  4. Works at scale (500+ file codebases)

Traceability

Requirement Phase Status
INTEL-01 Phase 1 ✓ Complete
INTEL-02 Phase 2 ✓ Complete
INTEL-03 Phase 3 ✓ Complete
INTEL-04 Phase 4 Pending
INTEL-05 Phase 4 Pending
INTEL-06 Phase 4 Pending
INTEL-07 Phase 4 Pending

Created: 2026-01-19 Updated: 2026-01-20 — Phase 4 planned (3 plans in 2 waves)