Prepare repository for the MCP client's analysis. This tool: 1. Extracts directory structure from the repository 2. Returns an EMPTY ProjectAnalysis for you to fill out 3. Provides directory structure in file_structure["directory_structure"] 4. Provides repository statistics in file_structure["statistics"] (file count, character count, etc.) You should: 1. Review the directory structure in file_structure["directory_structure"] 2. Use read_file to examine key files you identify from the structure 3. Fill out the empty fields in ProjectAnalysis based on your analysis 4. Set has_infrastructure_as_code=True if you detect CDK, Terraform, or other infrastructure as code 5. Use create_context to create a DocumentationContext from your analysis 6. Use the DocumentationContext with plan_documentation NOTE: This tool does NOT analyze the code - that's your job! The tool only extracts the directory structure and statistics to help you identify important files.

Create a DocumentationContext from a ProjectAnalysis. This tool simplifies the creation of a DocumentationContext for use with plan_documentation and generate_documentation tools. Args: project_root: Path to the code repository analysis: Completed ProjectAnalysis from prepare_repository ctx: Optional MCP context for logging and progress reporting Returns: A DocumentationContext ready for use with other tools

Third step: Create documentation plan using analysis. Using your analysis from prepare_repository and the DocumentationContext from create_context: 1. Review the ProjectAnalysis in doc_context containing: - Project type and purpose - Key features and capabilities - Programming languages and dependencies - APIs and interfaces 2. Determine what documentation types are needed 3. Create appropriate documentation structure 4. Return documentation plan

Final step: Generate documentation content. Using your analysis and documentation plan: 1. Generate document structures with empty sections 2. YOU (MCP Client) MUST then: - Write detailed content for each section - Include relevant code examples and explanations - Fill in ALL empty sections with comprehensive content - Cover all aspects: * Project setup and installation * Architecture and design * Features and capabilities * APIs and interfaces (if any) * Dependencies and requirements 3. Return document structures for you to fill with content IMPORTANT: When you receive the generated documents, it is YOUR responsibility to write comprehensive content for each section. Do not leave sections empty or wait for further instructions - YOU must fill them in!