spec-review

Review technical specifications for ambiguities, design bugs, and requirement adherence.

862|67|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/saffron-health/libretto --skill spec-review-saffron-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/saffron-health/libretto/tree/main/.agents/skills/spec-review
Command: npx skills add https://github.com/saffron-health/libretto --skill spec-review-saffron-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps ensure that technical specifications are clear, complete, and free of bugs before implementation begins, preventing wasted development effort.

Core Features & Use Cases

  • Identify Ambiguities: Flags under-specified areas in a spec where decisions are unclear.
  • Detect Design Bugs: Finds logical errors that could lead to incorrect behavior or implementation pitfalls.
  • Enforce Requirements: Checks adherence to the skill's own structural and quality guidelines.
  • Use Case: Before starting a new feature, submit your spec to this Skill for a thorough review to catch potential issues early in the design phase.

Quick Start

Use the spec-review skill to review the attached file 'new-feature-spec.md'.

Frequently Asked Questions about spec-review

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

FAQPage Schema
How do I review technical specifications for design-level bugs before implementation?

To review technical specifications for design bugs, you analyze software design documents and implementation plans to identify logical errors that could lead to incorrect behavior. This catches potential issues early before development begins.

What is the best way to find under-specified areas in a software design document?

Finding under-specified areas in a software design document requires evaluating the spec to flag unclear decisions. This ensures your technical specifications are clear and complete before implementation starts.

How does spec review enforce adherence to defined requirements?

Spec review enforces adherence by checking technical specifications against defined structural and quality guidelines. It requires analyzing referenced codebase files and external documentation to ensure a comprehensive assessment of the design.

Can I use automated code review techniques to check implementation plans?

Yes, you can apply code review techniques to check implementation plans by evaluating software design documents for under-specified areas and design-level bugs. This ensures your plans align with defined requirements and external documentation.

What limitations exist when evaluating technical writing in software development specs?

A limitation when evaluating technical writing in software development specs is that the review requires analysis of referenced codebase files and external documentation. Without providing these referenced files, the spec assessment cannot be comprehensive.