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).
What this skill does
# 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 |
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.