describe-design

# Describe Design Research a codebase and produce an architectural document describing how features or systems work. The output is a markdown file organized for both human readers and future AI agents. ## Workflow ### Stage 1: Scope Definition Understand what to document before exploring: 1. Ask what feature, system, or component to document. 2. Clarify the target audience (developers, AI agents, or both). 3. Confirm the codebase location if not obvious from context. ### Stage 2: Initial Exploration Explore the codebase broadly to build a mental model. Use lightweight, fast exploration methods when available (in Claude Code, for example, use a Haiku Explore subagent): 1. Scan directory structure and identify key entry points. 2. Read README, config files, and existing documentation. 3. Identify the main files and modules related to the feature. 4. Build a mental model of codebase organization. Present a high-level outline to the user: ``` ## Proposed Outline 1. [Component A] - Brief description 2. [Component B] - Brief description 3. [Component C] - Brief description * Have I correctly captured the scope of the research? Reply "yes" to continue. * Otherwise, please let me know what I've misunderstood. ``` When the user confirms the scope, move on to deep research. ### Stage 3: Deep Research For each component in the approved outline: 1. Trace code paths from entry points. 2. Identify dependencies and interactions between components. 3. Note configuration optio...