feature-review

Review implemented features against design plans using git-diff analysis.

2|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/EvanLavender13/audio-jones --skill feature-review-evanlavender13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-review
Source: https://github.com/EvanLavender13/audio-jones/tree/main/.claude/skills/feature-review
Command: npx skills add https://github.com/EvanLavender13/audio-jones --skill feature-review-evanlavender13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the evaluation of implemented features against their design plans to identify deviations and ensure alignment.

Core Features & Use Cases

  • Plan-as-truth verification: compares actual changes against the documented plan to surface discrepancies.
  • Git-diff based review: analyzes code changes between branches to identify scope drift.
  • Flexible agent workflow: supports single or multi-agent reviews to adapt to team size and risk.
  • Confidence-filtered reporting: surfaces issues with high confidence and actionable fixes.

Quick Start

Point the system to the target plan document and the current feature branch to begin an alignment review.

Frequently Asked Questions about feature-review

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

FAQPage Schema
How do I automate code review to verify implemented features match the design plan?

Run an automated alignment review by pointing the system to your target plan document and current feature branch. It analyzes the git diff to assess code changes and surfaces discrepancies between the implementation and the documented plan.

What is plan-as-truth verification in feature review?

Plan-as-truth verification is a code review mechanism that treats the documented design plan as the source of truth. It compares actual git-diff changes against the plan to detect scope drift and ensure implemented features align with documented requirements.

Can I use multi-agent workflows for plan-based code review?

Yes, the feature review process supports both single and multi-agent workflows to adapt to team size and risk. This flexible agent workflow enables parallel validation of code changes against design plans across distributed teams.

How does confidence filtering work when reviewing code for plan alignment?

Confidence filtering surfaces only issues with a confidence score of 80% or higher during plan-based validation. This structured issue consolidation ensures that reported deviations between code and design plans are actionable and highly reliable.

When should I use automated feature review instead of manual code review?

Use automated feature review during post-implementation checks or code reviews when you need to validate that changes meet a documented plan. It is especially useful for detecting scope drift in git diffs across single or multi-agent workflows.