plugins/pokayokay/skills/feature-audit/SKILL.md
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).
npx skillsauth add srstomp/pokayokay feature-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Ensures features are not just implemented but actually user-accessible. Bridges the gap between "code complete" and "user can use it."
session-review for retrospectives on how work wentsecurity-audit for vulnerability scanning; this skill checks feature completeness, not securityplanning to break down PRDs into tasks; this skill audits after implementation| 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 |
.claude/features.json and tasks.db| Reference | Description | |-----------|-------------| | framework-patterns.md | Scanning patterns for each framework | | completeness-criteria.md | Detailed level definitions and checklists | | gap-analysis.md | Analysis methodology | | remediation-templates.md | Task templates for common gaps | | scanning-process.md | Backend, frontend, API, navigation scans | | anti-patterns.md | Audit and remediation anti-patterns |
development
Git worktree management for isolated task development
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
testing
Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.
development
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.