feature-coverage-auditlisted

# Feature Coverage Audit Audit one project at a time to answer whether implemented functionality is covered by both human-readable documentation and `.aidd/features/*/feature.json` blueprints. This workflow is semantic and evidence-driven. It sits above `feature-review`, which reviews existing backlog specs, and above aidd's own end-of-run feature-contract check, which validates feature metadata syntax and roadmap contracts. ## Usage ```text feature-coverage-audit [app] [--report-only|--apply] [--include-completed] ``` ## Modes - Default: analyze one project, auto-fix only high-confidence safe gaps, and report ambiguous gaps. - `--report-only`: do not write files. Produce the coverage report only. - `--apply`: explicit alias for the default safe auto-fix behavior. It does not authorize risky changes. - `--include-completed`: include completed and verified feature JSONs in spec-completeness review, not only coverage matching. Never run a fleet sweep from this skill. For cross-app work, run this skill separately per app or create a dedicated sweep command. ## Phase 1: Resolve Target 1. Resolve the target from the argument, current directory, or `<applications-root>/AGENTS.md` app name. 2. Verify the target is local and contains `.aidd/features/`. 3. Read project-local instructions first: `AGENTS.md`, `CLAUDE.md`, `.aidd/project.md`, `docs/template/STACK.md`, and `docs/template/DEVELOPMENT.md` when present. 4. Capture baseline dirty state with `git status --short`. Dirt