Agent-Skills.md

Agent Skills: 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).

UncategorizedID: srstomp/pokayokay/feature-audit

Repository

srstomp/pokayokay
srstompLicense: MIT
4

Install this agent skill to your local

pnpm dlx add-skill https://github.com/srstomp/pokayokay/tree/HEAD/plugins/pokayokay/skills/feature-audit

Skill Files

Browse the full folder contents for feature-audit.

Download Skill

Loading file tree…

plugins/pokayokay/skills/feature-audit/SKILL.md

Skill Metadata

Name
feature-audit
Description
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).

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 | 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 |