speckit-validation

Validate Spec Kit feature delivery and route PASS, FAIL, or BLOCKED outcomes.

95|39|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-validation
Source: https://github.com/liuminxin45/auto-podcast/tree/main/.agents/spec-kit/skills/speckit-validation
Command: npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams verify Spec Kit deliveries without touching product code, so they can reproduce issues, collect evidence, and decide next actions with confidence.

Core Features & Use Cases

  • Validation-only workflow: Run smoke checks, audits, or regression validation while keeping production code unchanged.
  • Evidence-driven reporting: Capture commands, logs, screenshots, and validation summaries for traceable acceptance.
  • Routing guidance: Determine whether the result should move to micro-fix, standard-bugfix, full-sdd, or blocked-investigation.
  • Use Case: A release engineer checks an Electron host flow, records the CDP evidence, and outputs a validation verdict with the right next delivery profile.

Quick Start

Use the speckit-validation skill to validate the current feature, summarize evidence, and report blockers with the recommended next delivery profile.

Frequently Asked Questions about speckit-validation

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

FAQPage Schema
How do I validate Spec Kit feature delivery without modifying production code?

To validate Spec Kit feature delivery without code changes, use a validation-only workflow that runs smoke checks and audits while keeping production code unchanged. This requires the .specify project structure and validation artifacts like validation.md.

How do I collect acceptance evidence for Electron host-embedded UI during regression testing?

Acceptance evidence for Electron host-embedded UI is collected by capturing commands, logs, and screenshots during CDP smoke checks. This evidence-backed routing determines whether the outcome results in PASS, FAIL, or BLOCKED.

What is the best way to route blocked Spec Kit validation results to the correct next delivery profile?

Routing blocked Spec Kit validation results involves auditing acceptance evidence to recommend the next delivery profile, categorizing the outcome into micro-fix, standard-bugfix, full-sdd, or blocked-investigation based on the captured logs and validation summaries.

Do I need a .specify project structure to run validation-only workflows for Spec Kit repositories?

Yes, running validation-only workflows for Spec Kit repositories requires the .specify project structure. This structure ensures the necessary validation artifacts, including validation.md and evidence.md files, are present to support evidence-backed routing decisions.

What limitations exist when reproducing issues with Spec Kit validation artifacts?

Limitations when reproducing issues with Spec Kit validation artifacts include the strict dependency on the .specify project structure and evidence.md files to function, meaning workflows cannot proceed without these specific prerequisites.