skills.rest
Huruikagi
HuruikagiCOMMUNITY
Explore all skills by this author →
GitHub

sb-validate-implementation

Validates a completed Spec implementation against active Requirement IDs and records completion evidence.

Updated Jul 17, 2026
Search Tags:#validation#requirements traceability#go no-go#cli workflow#spec lifecycle#completion evidence#specbind
One-click install
npx skills add https://github.com/Huruikagi/pc-build-planner --skill sb-validate-implementation-huruikagi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sb-validate-implementation
Source: https://github.com/Huruikagi/pc-build-planner/tree/main/.agents/skills/sb-validate-implementation
Command: npx skills add https://github.com/Huruikagi/pc-build-planner --skill sb-validate-implementation-huruikagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When every task for a specification is marked complete, teams still lack a rigorous, evidence-backed gate that proves the implementation actually satisfies the active requirements before declaring the Spec done. This Skill performs that lifecycle validation and records durable completion evidence only when the verdict is GO. ## Core Features & Use Cases - Preflight gating: Runs read-only preflight checks on state, gate freshness, task completion, and a clean committed HEAD, pinning the exact implementation revision to validate. - Evidence-driven verdicts: Reads requirements, design, contract, and traceability to scope the active Requirement IDs, then runs the project's canonical test, build, lint, and typecheck commands plus any Validation adapter procedures before deciding GO, NO-GO, or MANUAL_VERIFY_REQUIRED. - Completion recording: On GO only, submits strict JSON evidence (verbatim commands and exit codes) via specbind spec completion accept, and supports invalidation and revalidation when evidence no longer holds. - Use Case: After finishing all tasks for a Spec, ask the agent to validate the implementation; it gathers mechanical check results, dispatches independent review dimensions, and either records completion or returns named findings to implementation. ## Quick Start Ask the agent to validate the active Spec implementation now that all its tasks are complete and record completion if the verdict is GO.

Frequently Asked Questions about sb-validate-implementation

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

FAQPage Schema
How do I validate a Spec implementation with specbind?▼

Run specbind spec completion preflight to confirm state, task completion, and a clean HEAD, then gather evidence from requirements, design, traceability, and the project's canonical commands. On a GO verdict, submit evidence with specbind spec completion accept.

What is the difference between sb-validate-implementation and sb-verify-completion?▼

sb-validate-implementation is the lifecycle gate that records durable completion evidence on GO and requires explicit authority. sb-verify-completion is a consequence-free truth check that reports whether claims hold without mutating any state.

What verdicts can the validation workflow return?▼

Three verdicts exist: GO when every check passes, NO-GO when a named problem is found, and MANUAL_VERIFY_REQUIRED when a mandatory check cannot be performed. MANUAL_VERIFY_REQUIRED is never a route to GO.

Does a passing test suite alone justify a GO verdict?▼

No. Tests only exercise what someone thought to test; they do not prove the artifact runs, that active requirements are covered, or that pieces integrate. Runtime liveness, requirement coverage, and design alignment must also be assessed.

When should completion evidence be invalidated?▼

Invalidate with specbind spec completion invalidate when a release_ready Spec's evidence no longer holds, such as after later project-content commits stale the implementation revision. Only completion evidence is cleared; requirements, design, and tasks stay approved.

Can the validator fix issues it finds during validation?▼

No. The validator never repairs source, weakens checks, or edits requirements, design, contract, or plan. NO-GO findings return to implementation, because a validator that repairs would be attesting to its own work.

Related Skills

Explore More Software Engineering Skills→
AlmogMaayanAlmogMaayan

openspec-apply-change

Implements tasks from an OpenSpec change proposal while keeping task lists and specs synchronized.

Community
Intermediate
councilofwizardscouncilofwizards
1

write-stories

Transform roadmap items into INVEST-compliant user stories with acceptance criteria.

Official
Advanced
AmitabhainArunachalaAmitabhainArunachala

oz-verify-claim

Independently verifies claims and PRs by re-running tests and confirming receipts exist.

Community
Intermediate
shynlee04shynlee04
51

hivefiver-gsd-compat

Map HiveFiver outputs to GSD lifecycle nodes with lineage validation.

Community
Intermediate