discover

Generate a codebase.md file that maps your architecture, patterns, and integration points with file:line references. This creates a searchable, evidence-based record of your code structure that developers can verify by navigating directly to cited locations.

Produce a research.md file that captures external knowledge with official-source verification and attribution. Each claim links back to its source, ensuring your documentation is auditable and distinguishes between verified facts and opinions.

Yes. This process combines codebase mapping and external research into linked deliverables, producing both codebase.md and research.md with consistent file:line and source citations so architecture decisions trace to both code and authoritative references.

Follow the commit steps specified to validate claims against official sources, add attributions to external knowledge, and maintain file:line references throughout. This creates documentation others can verify by checking your cited evidence independently.

Use this approach when documenting a feature that spans multiple code files and depends on external standards, libraries, or domain knowledge. It's essential for onboarding, compliance, and preserving the reasoning behind architectural choices.