feature-review

Reconstruct feature contracts from artifacts and generate formal verification verdicts.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill feature-review-cyberpunk042
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-review
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/feature-review
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill feature-review-cyberpunk042

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The closing gate of the feature-development chain. Test stage produced green tests; review verifies the FEATURE (not just the tests) meets the spec authored at document stage. Per Methodology Standards: "99→100 is human-only on both dimensions — adversarial review required." This skill runs the adversarial review the operator confirms or rejects.

Core Features & Use Cases

  • Reconstruct the spec contract from artifacts and capture all requirements, decisions, and artifacts.
  • Validate alignment by re-running tests and tracing each requirement to its implementation, tests, and outcomes.
  • Generate a formal verdict with evidence, flag design drift, and surface gaps for sign-off.

Quick Start

Load this skill during the test-complete stage to initiate adversarial verification and sign-off for the feature.

Frequently Asked Questions about feature-review

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

FAQPage Schema
How do I verify a feature meets its spec after tests pass?

Feature verification reconstructs the feature contract from artifacts to rigorously validate alignment, re-executing tests and tracing requirements to implementation for formal sign-off.

What is adversarial review in software quality assurance?

Adversarial review is the human-only closing gate verifying a feature meets the authored spec, checking design decisions against implementation and surfacing gaps with evidence before sign-off.

How to perform pre-merge feature verification and traceability?

Pre-merge verification traces each requirement to its implementation and test outcomes, re-executing tests and checking design decisions against the spec to produce a formal verdict with evidence.

When do I need post-incident validation for feature sign-off?

Post-incident validation is required when sign-off is needed after an incident, reconstructing the spec contract to re-execute tests and confirm implementation alignment with formal evidence.

Does feature review work without external dependencies?

Feature review operates with no external dependencies, reconstructing the feature contract entirely from available artifacts to perform adversarial verification and produce a formal verdict.

What does a feature verification verdict include?

A feature verification verdict includes formal evidence of test re-execution, requirement-to-implementation traceability, design drift flags, and surfaced gaps for sign-off rejection or confirmation.