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.
2.3 KiB
Codebase scout — map selection table
Lazy-loaded reference for the
scout_codebasestep inworkflows/discuss-phase.md(extracted via the discuss-phase/modes progressive-disclosure split, #717). Read this only when prior.planning/codebase/*.mdmaps exist and the workflow needs to pick which 2–3 to load.
Phase-type → recommended maps
Read 2–3 maps based on inferred phase type. Do NOT read all seven — that inflates context without improving discussion quality.
| Phase type (infer from title + ROADMAP entry) | Read these maps |
|---|---|
| UI / frontend / styling / design | CONVENTIONS.md, STRUCTURE.md, STACK.md |
| Backend / API / service / data model | STACK.md, ARCHITECTURE.md, INTEGRATIONS.md |
| Integration / third-party / provider | STACK.md, INTEGRATIONS.md, ARCHITECTURE.md |
| Infrastructure / DevOps / CI / deploy | STACK.md, ARCHITECTURE.md, INTEGRATIONS.md |
| Testing / QA / coverage | TESTING.md, CONVENTIONS.md, STRUCTURE.md |
| Documentation / content | CONVENTIONS.md, STRUCTURE.md |
| Mixed / unclear | STACK.md, ARCHITECTURE.md, CONVENTIONS.md |
Read CONCERNS.md only if the phase explicitly addresses known concerns or security issues.
Single-read rule
Read each map file in a single Read call. Do not read the same file at two different offsets — split reads break prompt-cache reuse and cost more than a single full read.
No-maps fallback
If .planning/codebase/*.md does not exist:
- Extract key terms from the phase goal (e.g., "feed" → "post", "card", "list"; "auth" → "login", "session", "token")
grep -rlE "{term1}|{term2}" src/ app/ --include="*.ts" ...(use-Efor extended regex so the|alternation works on both GNU grep and BSD grep / macOS), andlsthe conventional component/hook/util dirs- Read the 3–5 most relevant files
Output (internal <codebase_context>)
From the scan, identify:
- Reusable assets — components, hooks, utilities usable in this phase
- Established patterns — state management, styling, data fetching
- Integration points — routes, nav, providers where new code connects
- Creative options — approaches the architecture enables or constrains
Used in analyze_phase and present_gray_areas. NOT written to a file —
session-only.