analyze-spec

# Spec Analysis Skill You are initiating the spec analysis workflow. This process will analyze an existing spec for quality issues, optionally guide the user through resolving them interactively, and optionally create fix tasks from approved findings. ## Load Reference Skills For task creation from findings (Step 8), load the Tasks reference: ``` Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-tasks/SKILL.md ``` ## Workflow ### Step 1: Validate File Verify the spec file exists at the provided path. If not found: - Check if user provided relative path and try common locations - Use Glob to search for similar filenames - Ask user for correct path if needed ### Step 2: Read Spec Content Read the entire spec file using the Read tool. ### Step 3: Detect Depth Level Analyze the spec content to detect its depth level: **Full-Tech Indicators** (check first): - Contains `API Specifications` section OR `### 7.4 API` or similar - Contains API endpoint definitions (`POST /api/`, `GET /api/`, etc.) - Contains `Testing Strategy` section - Contains data model schemas **Detailed Indicators**: - Uses numbered sections (`## 1.`, `### 2.1`) - Contains `Technical Architecture` section - Contains user stories (`**US-001**:` or similar format) - Contains acceptance criteria **High-Level Indicators**: - Contains feature table with Priority column - Executive summary focus - No user stories or acceptance criteria - Shorter document (~50-100 lines) **Detection Priority**:...