acquire-codebase-knowledge

Topics in the source

• Acquire Codebase Knowledge
• Output Contract (Required)
• Workflow
• Focus Area Mode
• Phase 1: Scan and Read Intent
• Phase 2: Investigate
• Phase 3: Populate Templates
• Phase 4: Validate, Repair, Verify

Produces 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. Before finishing, all of the following must be true: 1. Exactly these files exist in docs/codebase/: STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, INTEGRATIONS.md, TESTING.md, CONCERNS.md. 2. Every claim is traceable to source files, config, or terminal output. 3. Unknowns are marked as [TODO]; intent-dependent decisions are marked [ASK USER]. 4. Every document includes a short "evidence" list with concrete file paths. 5. Final response includes numbered [ASK USER] questions and intent-vs-reality divergences. Copy and track this checklist: If the user supplies a focus area (for example: "architecture only" or "testing and concerns"): 1. Always run Phase 1 in full. 2. Fully complete focus-area documents first. 3. For non-focus documents not yet analyzed, keep required sections present and mark unknowns as [TODO]. 4. Still run the Phase 4 validation loop on all seven documents before final output. 1. Run the scan script from the target project root: Where $SKILLROOT is the

This is an excerpt. Refer to the complete source and its current requirements.