validate-feature

Validates a completed feature against its plan's acceptance criteria and writes a validation report.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill validate-feature-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-feature
Source: https://github.com/pnewsam/skills/tree/main/archive/redundancy-evicted/validate-feature
Command: npx skills add https://github.com/pnewsam/skills --skill validate-feature-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a feature is built, teams need structured proof that it actually works before opening a PR. This Skill runs targeted tests, surface-appropriate regression checks, and verifies every acceptance criterion from the feature plan, producing a documented validation report instead of ad-hoc manual checking. ## Core Features & Use Cases - Acceptance Criteria Verification: Checks each criterion in the feature plan and marks it VERIFIED, FAILED, or CANNOT VERIFY with evidence. - Surface-Aware Testing: Classifies the feature as browser/UI, service/API, library/CLI, or mixed, then runs proportionate targeted and regression tests for that surface. - Validation Report Generation: Writes a structured report to docs/features/ with test results, coverage gaps, regressions, and a ship/no-ship recommendation, then appends a Validation section to the feature plan. - Use Case: After execute-feature finishes a new API endpoint, run this Skill to confirm all acceptance criteria pass, detect regressions in the integration suite, and produce a READY TO SHIP report before prepare-pr. ## Quick Start Use the validate-feature skill to verify the current feature against its plan and produce a validation report.

Frequently Asked Questions about validate-feature

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

FAQPage Schema
How do I validate a completed feature before opening a PR?▼

Run this Skill after the feature plan is fully checked off. It runs targeted tests for changed files, a surface-appropriate regression suite, verifies each acceptance criterion, and writes a validation report with a READY TO SHIP, SHIP WITH CAVEATS, or DO NOT SHIP recommendation.

What is the difference between validate-feature and validate-changes?▼

validate-changes is a fast spot-check of modified files, while validate-feature is a broader post-build pass scoped to the whole feature and its blast radius. It adds acceptance criteria verification and a formal validation report.

Does feature validation work without browser tests?▼

Yes. For browser-facing features without browser tests, it runs unit tests, lint, and typecheck, verifies criteria through the best available path, and flags the missing browser coverage as a gap. Non-browser features skip browser checks entirely.

Can I validate a partially implemented feature?▼

Yes, with user confirmation. The Skill validates only the completed acceptance criteria, notes which were skipped in the report, and recommends finishing the feature before running prepare-pr.

What happens when pre-existing test failures appear during validation?▼

Pre-existing failures are flagged but do not block the validation result. The Skill distinguishes regressions caused by the feature from pre-existing and flaky failures, and may exclude known-failing tests while noting the exclusions.