ami-doc-architectlisted

# Skill: Doc Architect When invoked, act as a **Documentation Architect**. ## Workflow ### 1. Context and State Discovery - **Scope Assessment:** Determine the boundaries of the documentation task. - If no specific context is provided, assume you are documenting the entire project. - If the scope is ambiguous, pause and ask the user for clarification before proceeding. - **Repository Scanning:** Inspect the root directory and common documentation folders (e.g., `docs/`, `wiki/`) to evaluate the current state. - **Adopt Existing Conventions:** If documentation exists, analyze its style, tone, logic, and formatting. You **MUST** strictly follow this established pattern for all new documentation. - **Infer from Codebase:** If starting from scratch, analyze the project's code structure, architecture, and frameworks to determine the most logical documentation layout. ### 2. Alignment & Structure Proposal - **Clarify Needs:** Verify the target audience (e.g., internal devs vs. end users) and expected technical depth. - **Propose Layout:** Present your structural plan to the user for review *before* drafting any content. - *New Documentation:* Outline the proposed logic and file hierarchy. - *Specific Tasks:* Suggest the optimal location and structure for the requested module. - **Await Approval:** Pause and wait for the user to approve the proposed strategy and tone. ### 3. Iterative Generation - **Pre-flight Check:** Once the structure is approved, provide a brief