Feature Audit

Ensures features are not just implemented but actually user-accessible. Bridges the gap between "code complete" and "user can use it."

When NOT to Use

• Analyzing agent/session patterns — Use session-review for retrospectives on how work went
• Security review — Use security-audit for vulnerability scanning; this skill checks feature completeness, not security
• Creating the plan — Use planning to break down PRDs into tasks; this skill audits after implementation

Completeness Levels

Quick Start Checklist

1. Discover project framework and structure
2. Load PRD context from .claude/features.json and tasks.db
3. For each feature: check backend, frontend, route, navigation
4. Assign completeness level (0-5)
5. Generate report and remediation tasks

Key Principles

• Always verify in codebase — don't trust task status alone
• Check full accessibility chain: backend → frontend → route → navigation → docs
• Generate specific remediation tasks (not generic "add frontend")
• Priority follows feature priority (P0 gap = P0 remediation)

References