acquire-codebase-knowledge

1# Acquire Codebase Knowledge
2 
3Produces seven populated documents in `docs/codebase/` covering everything needed to work effectively on the project. Only document what is verifiable from files or terminal output — never infer or assume.
4 
5## Output Contract (Required)
6 
7Before finishing, all of the following must be true:
8 
91. Exactly these files exist in `docs/codebase/`: `STACK.md`, `STRUCTURE.md`, `ARCHITECTURE.md`, `CONVENTIONS.md`, `INTEGRATIONS.md`, `TESTING.md`, `CONCERNS.md`.
102. Every claim is traceable to source files, config, or terminal output.
113. Unknowns are marked as `[TODO]`; intent-dependent decisions are marked `[ASK USER]`.
124. Every document includes a short "evidence" list with concrete file paths.
135. Final response includes numbered `[ASK USER]` questions and intent-vs-reality divergences.
14 
15## Workflow
16 
17Copy and track this checklist:
18 
19```
20- [ ] Phase 1: Run scan, read intent documents
21- [ ] Phase 2: Investigate each documentation area
22- [ ] Phase 3: Populate all seven docs in docs/codebase/
23- [ ] Phase 4: Validate docs, present findings, resolve all [ASK USER] items
24```
25 
26## Focus Area Mode
27 
28If the user supplies a focus area (for example: "architecture only" or "testing and concerns"):
29 
301. Always run Phase 1 in full.
312. Fully complete focus-area documents first.
323. For non-focus documents not yet analyzed, keep required sections present and mark unknowns as `[TODO]`.
334. Still run the Phase 4 validation loop on all seven documents before final output.
34…