spec-review

Apply natural-language spec feedback to v2 specification artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

spec-review fixes a common workflow gap where feedback given in natural language is applied to design.md (or other documents) without updating the source-of-truth requirements.md and the v2 pipeline artifacts consistently.

Core Features & Use Cases

  • Gate-free document synchronization: Applies document-based feedback outside the specify/blueprint approval gate while keeping requirements.md / plan.json / contracts.md / design.md aligned.
  • Targeted editing by artifact type: Edits requirements.md and Markdown sections of contracts.md/design.md directly, while routing plan.json changes through sr-harness-cli merge/validate instead of manual edits.
  • Impact analysis and section-level regeneration: Rebuilds only the affected sections (not entire files) to preserve IDs and maintain traceability.
  • Coverage warnings for missing task implementation: Warns when new/changed requirements are not covered by plan.json tasks, suggesting re-running blueprint or adding tasks via the CLI flow.

Quick Start

Ask the skill to review a specific spec and apply your change request, for example: " /spec-review, then update wheel-controller-uart-refactor so R-T1.2 includes the new E-Stop emission condition and regenerate the affected design.md sections."

Frequently Asked Questions about spec-review

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

FAQPage Schema
How do I synchronize requirements.md with design.md after a spec review without going through the blueprint approval gate?

To synchronize requirements.md with design.md outside the blueprint approval gate, apply natural-language spec feedback consistently across v2 pipeline artifacts. Targeted section-level editing rebuilds only affected parts to preserve IDs and maintain traceability.

What is the best way to apply natural-language feedback to plan.json while keeping requirements synchronized?

Applying natural-language feedback to plan.json requires routing changes through sr-harness-cli merge and validate commands rather than manual edits. This ensures plan.json task wording and status updates remain synchronized with requirements.md updates.

Does spec-review support cross-module requirement edits and sub-requirement GWT updates?

Spec-review supports both scenario-specific and cross-module changes, including sub-requirement GWT updates, parent requirement edits, and interface or invariant updates. It directly edits SSoT Markdown files to enforce correct update constraints.

Why are my new requirements not showing up as tasks in plan.json after a document synchronization?

New or changed requirements may not be covered by plan.json tasks after synchronization. The process warns when coverage is missing and suggests re-running the blueprint or adding tasks via the sr-harness-cli flow to resolve the gap.

Can I update contracts.md invariants without regenerating the entire file?

You can update contracts.md invariants without regenerating the entire file. The process performs impact analysis and rebuilds only the affected sections, preserving existing IDs and maintaining document traceability across artifacts.