a9a7a328e6
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
84 lines
3.6 KiB
Markdown
84 lines
3.6 KiB
Markdown
---
|
|
name: msd:map-codebase
|
|
description: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
|
|
argument-hint: "[--fast [--focus tech|arch|quality|concerns]] [--query <term>|status|diff|refresh] [area]"
|
|
allowed-tools:
|
|
- Read
|
|
- Bash
|
|
- Glob
|
|
- Grep
|
|
- Write
|
|
- Agent
|
|
requires: [config, new-project, plan-phase, onboard]
|
|
---
|
|
|
|
<objective>
|
|
Analyze existing codebase using parallel msd-codebase-mapper agents to produce structured codebase documents.
|
|
|
|
Each mapper agent explores a focus area and **writes documents directly** to `.planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.
|
|
|
|
Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/msd-core/workflows/map-codebase.md
|
|
</execution_context>
|
|
|
|
<flags>
|
|
- **--fast**: Lightweight scan mode — spawns one mapper agent instead of four. Accepts an optional `--focus` value: `tech`, `arch`, `quality`, `concerns`, or `tech+arch` (default). Faster and lower-context than the full map.
|
|
- **--query**: Codebase intelligence query mode. Sub-commands: `query <term>`, `status`, `diff`, `refresh`. Requires intel to be enabled in config (`intel.enabled: true`). Runs inline for query/status/diff; spawns an agent for refresh.
|
|
- **(no flag)**: Full parallel map — spawns 4 mapper agents to produce all 7 codebase documents.
|
|
</flags>
|
|
|
|
<context>
|
|
Arguments: $ARGUMENTS
|
|
|
|
Parse the first token of $ARGUMENTS:
|
|
- If it is `--fast`: strip the flag, then read and execute `~/.claude/msd-core/workflows/scan.md` (passing remaining args including optional --focus). Load it on demand here — it is deliberately not in `<execution_context>`, so the common full-map path does not pay for it.
|
|
- If it is `--query`: strip the flag, run the intel workflow (passing remaining args as the subcommand).
|
|
- Otherwise: pass all of $ARGUMENTS as focus area to the map-codebase workflow.
|
|
|
|
**Load project state if exists:**
|
|
Check for .planning/STATE.md - loads context if project already initialized
|
|
|
|
**This command can run:**
|
|
- Via /msd:onboard for first-time brownfield setup - creates codebase map first
|
|
- After /msd:new-project (greenfield codebases) - updates codebase map as code evolves
|
|
- Anytime to refresh codebase understanding
|
|
</context>
|
|
|
|
<when_to_use>
|
|
**Use map-codebase for:**
|
|
- Brownfield projects before initialization (understand existing code first)
|
|
- Refreshing codebase map after significant changes
|
|
- Refreshing or deepening an onboarded codebase map
|
|
- Before major refactoring (understand current state)
|
|
- When STATE.md references outdated codebase info
|
|
|
|
**Skip map-codebase for:**
|
|
- Greenfield projects with no code yet (nothing to map)
|
|
- Trivial codebases (<5 files)
|
|
</when_to_use>
|
|
|
|
<process>
|
|
1. Check if .planning/codebase/ already exists (offer to refresh or skip)
|
|
2. Create .planning/codebase/ directory structure
|
|
3. Spawn 4 parallel msd-codebase-mapper agents:
|
|
- Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md
|
|
- Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md
|
|
- Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md
|
|
- Agent 4: concerns focus → writes CONCERNS.md
|
|
4. Wait for agents to complete, collect confirmations (NOT document contents)
|
|
5. Verify all 7 documents exist with line counts
|
|
6. Commit codebase map
|
|
7. Offer next steps (typically: /msd:onboard, /msd:new-project, or /msd:plan-phase)
|
|
</process>
|
|
|
|
<success_criteria>
|
|
- [ ] .planning/codebase/ directory created
|
|
- [ ] All 7 codebase documents written by mapper agents
|
|
- [ ] Documents follow template structure
|
|
- [ ] Parallel agents completed without errors
|
|
- [ ] User knows next steps
|
|
</success_criteria>
|