# Feature Audit > Use when verifying feature completeness against PRD requirements, identifying gaps between backend implementation and user-facing accessibility, generating remediation tasks, or auditing across frameworks (Next.js, React Router, TanStack, React Native, Expo). - Skill: `tomevault-io/feature-audit` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/feature-audit` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/feature-audit/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Product & Planning - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/feature-audit --- # 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 | Level | Name | Meaning | |-------|------|---------| | 0 | Not Started | No implementation evidence | | 1 | Backend Only | Service/API exists, no frontend | | 2 | Frontend Exists | UI components exist, not accessible | | 3 | Routable | Has route/screen, not in navigation | | 4 | Accessible | In navigation, users can reach it | | 5 | Complete | Accessible + documented + tested | ## 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 | Reference | Description | |-----------|-------------| | [framework-patterns.md](references/framework-patterns.md) | Scanning patterns for each framework | | [completeness-criteria.md](references/completeness-criteria.md) | Detailed level definitions and checklists | | [gap-analysis.md](references/gap-analysis.md) | Analysis methodology | | [remediation-templates.md](references/remediation-templates.md) | Task templates for common gaps | | [scanning-process.md](references/scanning-process.md) | Backend, frontend, API, navigation scans | | [anti-patterns.md](references/anti-patterns.md) | Audit and remediation anti-patterns | --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/srstomp) — claim your Tome and manage your conversions.