harness-spec-review

Analyzes pending project specifications for quality, consistency, and risk before implementation.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/kekemoto/skills --skill harness-spec-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-spec-review
Source: https://github.com/kekemoto/skills/tree/main/skills/harness-spec-review
Command: npx skills add https://github.com/kekemoto/skills --skill harness-spec-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of implementing ambiguous or poorly defined specifications by performing a structured, cross-cutting review before any code is written.

Core Features & Use Cases

  • Automated Review Gate: Identifies weak acceptance conditions, missing observation points, and cross-spec dependency conflicts.
  • Risk Assessment: Evaluates specifications against defined risk criteria to prevent implementation of high-risk or ill-defined features.
  • Interactive Refinement: Uses structured questioning to resolve uncertainties and records confirmed decisions directly into the specification files.

Quick Start

Invoke the harness-spec-review skill to audit the pending specifications for your current project and resolve any identified concerns before starting implementation.

Frequently Asked Questions about harness-spec-review

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

FAQPage Schema
How do I review project specifications for quality and risk before implementation?

Spec review analyzes pending project specifications for quality, consistency, and risk by identifying weak acceptance conditions, missing observation points, and cross-spec dependency conflicts before code is written.

What is the best way to resolve logical gaps and dependency conflicts in pending specs?

Interactive refinement resolves logical gaps and dependency conflicts by using structured questioning to clarify uncertainties, then documenting confirmed design decisions directly back into the specification files.

How does risk assessment evaluate specifications against defined development gates?

Risk assessment evaluates specifications against defined risk criteria to prevent implementation of high-risk or ill-defined features, functioning as an automated review gate before development begins.

When do I need to audit specifications for cross-cutting dependency conflicts?

You need to audit specifications for cross-cutting dependency conflicts before implementation begins to ensure adherence to acceptance criteria and maintain a clear audit trail for subsequent development.

Can I document confirmed design decisions back into specification files automatically?

Yes, spec review facilitates user-driven resolution of uncertainties and ensures all confirmed design decisions are documented back into the specification files to maintain a clear audit trail.

What are the limitations of using an automated review gate for specification quality assurance?

An automated review gate requires existing pending specifications with defined risk criteria to evaluate; without structured spec sets and acceptance criteria, it cannot identify logical gaps or facilitate interactive refinement.