review-spec

Validate SPEC.md files against the SB spec template for missing sections and frontmatter gaps.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill review-spec-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-spec
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/review-spec
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill review-spec-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SPEC.md artifacts often fail to meet SB's spec template, leading to ambiguous requirements and inconsistent documentation. This skill automatically validates a SPEC.md against the SB template, surfacing missing sections and frontmatter gaps to improve quality and auditability.

Core Features & Use Cases

  • Validates required SPEC.md sections such as Overview, User Stories, UX Flows, Acceptance Criteria, Assumptions, Open Questions, Out of Scope, and Implementations.
  • Checks that frontmatter fields (e.g., spec-version, status, created, last-updated) are present and non-empty.
  • Produces structured findings (PASS/ISSUES_FOUND) with precise locations and remediation guidance to guide authors and reviewers.

Quick Start

Review a SPEC.md by providing its path to the reviewer, and obtain a structured quality report with actionable findings.

Frequently Asked Questions about review-spec

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

FAQPage Schema
How do I validate a SPEC.md document against a spec template?

To validate a SPEC.md document, provide its file path to the reviewer to check for missing sections and frontmatter gaps. The reviewer outputs a structured PASS or ISSUES_FOUND report with precise locations and remediation suggestions for incomplete artifacts.

What sections are required in a SPEC.md artifact for quality control?

Required sections in a SPEC.md artifact include Overview, User Stories, UX Flows, Acceptance Criteria, Assumptions, Open Questions, Out of Scope, and Implementations. Validating these sections ensures requirements are complete, well-formed, and unambiguous.

Why does my SPEC.md documentation fail frontmatter quality checks?

Your SPEC.md documentation fails frontmatter quality checks when fields like spec-version, status, created, and last-updated are missing or empty. The reviewer surfaces these frontmatter gaps and provides remediation guidance to update the metadata.

Can I check SPEC.md documents across multiple projects for missing sections?

Yes, you can check SPEC.md documents across multiple projects to ensure overview and acceptance criteria are complete. The reviewer applies the SB spec template uniformly to surface missing sections and frontmatter gaps in any SPEC.md file provided.

What is the best way to get actionable remediation suggestions for SPEC.md artifacts?

The best way to get remediation suggestions for SPEC.md artifacts is to run an automated spec review that reports structured PASS or ISSUES_FOUND findings. This provides precise locations for missing sections and frontmatter gaps to guide authors and reviewers.