impl-validator

Verify implementations against stated goals and report pass/warn/fail verdicts.

Updated Apr 27, 2014
One-click install
npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill impl-validator-nirajkashyap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impl-validator
Source: https://github.com/Nirajkashyap/nirajkashyap.github.io/tree/main/.agents/skills/impl-validator
Command: npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill impl-validator-nirajkashyap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate whether an implementation matches its stated goal. This skill helps ensure that outputs from other skills or agents are accurate and align with user expectations, catching mistakes before presenting to the user.

Core Features & Use Cases

  • Structured verification: returns a pass/warn/fail verdict with specific actionable issues.
  • Dual-mode operation: works as a subagent (receives a structured check block) or directly via user invocation.
  • Quality gate: verifies the presence and correctness of artifacts against the stated goal and project conventions.

Quick Start

Invoke the /impl-validator with either a description of the completed work or a structured check block to receive a structured verdict.

Frequently Asked Questions about impl-validator

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

FAQPage Schema
How do I verify if a code implementation actually achieves its stated goal?

To verify an implementation achieves its goal, you need a quality gate that performs existence, completeness, and correctness checks on artifacts against project conventions and returns a structured pass, warn, or fail verdict.

What is the best way to validate outputs from other subagents before presenting them to the user?

Validating subagent outputs requires a subagent mode that receives a structured check block, enforcing project conventions and catching mistakes by verifying the presence and correctness of artifacts against the stated goal.

Can I use a structured pass warn fail verdict system for code review?

Yes, a structured verification system can enforce project conventions during code review, returning actionable pass, warn, or fail verdicts with specific issues to ensure outputs align with user expectations.

How does subagent mode work for quality assurance verification?

Subagent mode operates by receiving a structured check block, then performing existence, completeness, and correctness checks on artifacts to deliver a structured verdict on the completed work.

When do I need a quality gate for software implementation verification?

You need a quality gate when you want to catch mistakes from other skills or agents before presenting outputs to the user, ensuring accuracy by validating artifacts against project conventions and stated goals.

What are the limitations of using a subagent to validate completed work?

The skill operates in two distinct modes and requires either a description of completed work or a structured check block, meaning it cannot verify implementations without explicit context or stated goals to check against.