analyze-coverage

# Analyze Coverage Skill Analyze test coverage for any project by running real coverage tools, parsing results into structured reports, and identifying gaps with actionable recommendations. Optionally maps coverage against spec acceptance criteria to find untested requirements. **CRITICAL: Complete ALL 6 phases.** The workflow is not complete until Phase 6: Suggest Next Steps is finished. After completing each phase, immediately proceed to the next phase without waiting for user prompts. ## Core Principles 1. **Real coverage data** -- Run actual coverage tools (pytest-cov, istanbul/c8) via Bash. Never estimate or guess coverage percentages. 2. **Standalone operation** -- This skill works on any project. It does not require the SDD pipeline, specs, or any other skill to function. 3. **Actionable output** -- Every coverage gap should include a specific suggestion for what test to write, not just a percentage. 4. **Graceful degradation** -- If coverage tools are not installed, detect and inform the user with install commands. If a spec is invalid, skip spec mapping and proceed with coverage-only analysis. ## AskUserQuestion is MANDATORY **IMPORTANT**: You MUST use the `AskUserQuestion` tool for ALL questions to the user. Never ask questions through regular text output. - Clarifying questions about project structure -> AskUserQuestion - Framework/tool selection -> AskUserQuestion - Threshold confirmation -> AskUserQuestion Text output should only be used for presenting in...