feature-review

Validate feature implementations against user journey completeness and UX feedback.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill feature-review-n0rvyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-review
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/apple-dev/skills/feature-review
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill feature-review-n0rvyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates whether a completed feature satisfies its intended user journeys and UX expectations by mapping specs and user stories to code entry points, detecting navigation dead ends, and verifying feedback and empty-state handling.

Core Features & Use Cases

  • User story mapping: extract user operations from feature specs or user description and locate corresponding code entry points such as buttons, navigation links, gestures, and menu commands.
  • Journey and navigation analysis: trace navigation stacks, modals, and window flows to detect dead ends, missing dismiss paths, and excessive navigation depth.
  • UX feedback and edge-case checks: verify success/failure/loading states, confirm destructive-action flows, and ensure lists and search results present meaningful empty states.
  • Use case: After merging a feature branch, produce a Feature Review Report that lists uncovered stories, navigation issues, missing confirmations, and a device validation checklist for QA.

Quick Start

Run a feature-review for the Create Note feature by comparing the feature spec in docs/05-features, the project-brief context, and the current code changes to generate a user-journey completeness report.

Frequently Asked Questions about feature-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate user journey completeness after merging a feature branch?

To validate user journey completeness, map feature specs to modified source files to trace navigation flows and detect dead ends. This identifies uncovered user stories and missing UI feedback within the changed code.

What is the best way to check for missing empty states and UX feedback in mobile app features?

Checking for missing empty states and UX feedback involves mapping user stories to code entry points to verify success, failure, and loading states. It ensures lists and search results present meaningful empty states.

How do I trace navigation dead ends and missing dismiss paths in macOS app workflows?

Tracing navigation dead ends in macOS workflows requires analyzing changed source files against feature specs to map navigation stacks and modals. This detects missing dismiss paths and excessive navigation depth.

Can I generate a QA checklist for uncovered user stories using feature specs and project briefs?

You can generate a QA checklist by comparing feature specs and project-brief context against repository code changes. This produces a Feature Review Report listing uncovered stories and a device validation checklist.

Does user story mapping work without a dedicated feature spec document?

User story mapping requires a feature spec or a user-provided description of expected behavior to extract operations. Without this context, the tool cannot locate corresponding code entry points or trace journeys.

Why does my feature review report show missing confirmations for destructive actions?

A feature review report shows missing confirmations when changed source files lack explicit UI feedback for destructive flows. The analysis verifies destructive-action flows against the expected behavior defined in the feature spec.