validate

Evaluate working software against the originating user need and report prioritized specification gaps.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/kieranpotts/skills --skill validate-kieranpotts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/kieranpotts/skills/tree/main/skills/validate
Command: npx skills add https://github.com/kieranpotts/skills --skill validate-kieranpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Software can pass every acceptance test and still fail the user, because the requirements specification itself may be wrong. This Skill judges working software against the original statement of need rather than its acceptance criteria, surfacing where the specification diverged from what users actually wanted. ## Core Features & Use Cases - Need-based evaluation: Recovers the originating statement of need and walks the working software as the user pursuing their real goal, not the specified steps. - Classified, evidenced findings: Each gap is typed (unmet need, wrong target, missing requirement, over-specification, or stale assumption), backed by cited evidence, and priced by change cost. - Bounded prioritized report: Produces five to ten findings with an explicit verdict — MEETS THE NEED or GAPS FOUND — without modifying any specification or code. - Use Case: After a release is complete and demonstrable, ask whether the software fulfills its goals; the agent walks the running increments and returns a report your team feeds into the next requirements refinement round. ## Quick Start Ask the agent: did we build the right thing, and what gaps can you find in the requirements specification?

Frequently Asked Questions about validate

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

FAQPage Schema
How do I validate that software meets actual user needs?▼

Recover the original statement of need, then walk the working software end-to-end as the user pursuing their real goal rather than the specified steps. Record observed behavior as evidence and classify each gap between what was specified and what was wanted.

What is the difference between software validation and verification?▼

Verification checks code against its acceptance criteria, while validation questions whether those criteria were right in the first place. A faithfully implemented but wrong specification passes verification and fails validation.

Can this validation run in CI or unattended workflows?▼

Yes, it runs non-interactively by resolving the specification, statement of need, and running software from context and environment. If requirements cannot be determined, it stops with an error instead of prompting the user.

What if no working instance of the software can be run?▼

Validation falls back to next-best evidence such as acceptance test coverage, interface definitions, screenshots, or telemetry. The report summary must state plainly that the walkthrough was not possible, since those findings are weaker.

Does validation change the requirements specification or code?▼

No, it is evaluation only and produces a report of suggestions with an explicit verdict. The working tree must remain unchanged apart from the persisted report, and revising requirements belongs to whoever acts on the findings.