analyzelisted

# Codebase Analysis Workflow This skill provides a complete analysis workflow for existing codebases. It is organized into stages that can be used independently or as a sequential pipeline. **Usage**: Invoke `/analyze` and specify which stage to run, or start from Stage 1 for a full discovery workflow. Provide `{project}` and optionally `{subproject}` as context. --- ## Stage 1: Analyze Codebase Purpose: Perform discovery analysis of existing codebase to: - Document system architecture and technology stack - Identify technical debt and improvement opportunities - Provide foundation for creating architectural components, slices, or maintenance tasks - Create reference documentation for team members This is reconnaissance work - not goal-oriented development. Analyze the following existing codebase and document your findings. We want this to not only assist ourselves in updating and maintaining the codebase, but also to assist humans who may be working on the project. ### Expected Output * Document your findings in `user/analysis/nnn-analysis.{topic}.md` where: - nnn starts at 940 (analysis range) - {topic} describes the analysis focus (e.g., "initial-codebase", "dependency-audit", "architecture-review") * Write in markdown format, following our rules for markdown output. ### General Guidelines * Document the codebase structure. Also note presence of any project-documents or similar folders which probably contain information for us. * Document presence or average o