skills.rest
mhawthorne
mhawthorneCOMMUNITY
Explore all skills by this author →
Website𝕏@mhawthorneGitHub

gza-spec-review

Validate spec file claims against the current codebase and project structure.

11|1|Updated Jan 6, 2026
Search Tags:#codebase#interactive#review#quality gate#spec#gate#go-no-go
One-click install
npx skills add https://github.com/mhawthorne/gza --skill gza-spec-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gza-spec-review
Source: https://github.com/mhawthorne/gza/tree/main/src/gza/skills/gza-spec-review
Command: npx skills add https://github.com/mhawthorne/gza --skill gza-spec-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams validate specs before implementation by running a structured quality gate that yields a clear go/no-go recommendation.

Core Features & Use Cases

  • Interactive quality gate that checks scope, accuracy, acceptance criteria, and risks.
  • Verifies claims against the codebase (files, commands, config fields) and surfaces issues for revision.
  • Provides a structured output with recommended actions and follow-up tasks for implementation planning.

Quick Start

Provide the path to the spec file when prompted (e.g., specs/foo.md) to begin the interactive gate.

Frequently Asked Questions about gza-spec-review

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

FAQPage Schema
How do I validate a spec file against my codebase before implementation?▼

Spec validation cross-references file existence, CLI flags, config fields, and workflow steps against your codebase to verify accuracy and surface issues before implementation begins.

What is a go/no-go quality gate in software specification review?▼

A go/no-go quality gate analyzes spec claims against the current codebase, returning a structured assessment with recommended actions and follow-up tasks for implementation planning.

How do I check if my spec's acceptance criteria match existing project structure?▼

Run an interactive review that verifies file existence, commands, config fields, and code references to ensure traceable validation of acceptance criteria against the current project structure.

Can I review development specs for scope and risks before coding starts?▼

Yes, providing the path to your spec file triggers an interactive quality gate that checks scope, accuracy, acceptance criteria, and risks to validate specifications before coding starts.

What does a structured spec assessment include for implementation planning?▼

A structured spec assessment includes a go/no-go recommendation, verified file and command cross-references, surfaced issues for revision, recommended actions, and follow-up tasks for implementation planning.

When do I need a spec quality gate in my development workflow?▼

You need a spec quality gate when early specification validation is required in your development workflow, ensuring claims are traceable against the codebase before committing to implementation.

Related Skills

Explore More Software Engineering Skills→
Daniele0302Daniele0302

prd-skill

Draft complete PRDs with standard template sections and acceptance criteria.

Community
Advanced
datamonsterrdatamonsterr

speckit-whatif-analyze

Simulate requirement changes and report complexity, effort, and task deltas.

Community
Advanced
juanca202juanca202

speckit-git-commit

Automate Git commits after Spec Kit command events.

Community
Basic
trypanictrypanic

go-code-quality-check

Run go vet, staticcheck, and semgrep to generate severity-grouped fix plans.

Community
Advanced