gk-spec-review

Audit planning documents for gaps, contradictions, and untestable criteria.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-spec-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gk-spec-review
Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-extra/gk-spec-review
Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-spec-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents expensive software bugs by auditing planning documents for gaps, contradictions, and untestable criteria before any code is written.

Core Features & Use Cases

  • Automated Audit: Systematically checks BRIEF.md, AGENT_ARCH.md, SPEC.md, and ARCHITECTURE.md against established rubrics.
  • Consistency Check: Identifies contradictions across multiple planning documents to ensure architectural alignment.
  • Use Case: Before starting a new feature build, run this skill to ensure your FEATURE_SPEC.md is testable and fully aligned with the project's existing architecture.

Quick Start

Trigger the spec review process by typing review the spec in your chat interface to audit all existing planning documents.

Frequently Asked Questions about gk-spec-review

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

FAQPage Schema
How do I audit software specification documents for gaps before implementation?

Auditing software specification documents involves systematically checking planning files like BRIEF.md, SPEC.md, and ARCHITECTURE.md against established rubrics to identify gaps, contradictions, and untestable criteria before coding begins.

What is the best way to check architectural alignment across multiple planning documents?

Checking architectural alignment requires consistency validation across multiple planning documents to identify contradictions, ensuring your feature specifications fully match the existing project architecture before a build starts.

How do I validate if a feature specification is testable before starting a build?

To validate if a feature specification is testable, run an automated audit process against internal rubrics and compliance standards to ensure your FEATURE_SPEC.md contains clear, testable criteria for agent readiness.

Does this specification validation skill work within the GK-Stack framework?

Yes, this specification validation skill applies to project initialization, feature specification, and architectural design phases specifically within the GK-Stack framework to ensure build reliability and agent readiness.

When should I run a specification audit to prevent build failures?

You should run a specification audit before starting any new feature build or implementation phase, ensuring your planning documents are fully aligned, testable, and free of expensive contradictions.