skills.rest
bennybennison
bennybennisonCOMMUNITY
Explore all skills by this author →
GitHub

review-specs

Identify and eliminate duplicate, overlapping, or conflicting specifications in a plan/specs/ directory.

Updated Apr 11, 2026
Search Tags:#workflow#documentation#deduplication#conflict resolution#specs#spec management
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill review-specs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-specs
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/review-specs
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill review-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec repositories accumulate duplicate, overlapping, or contradictory specifications, leading to confusion and implementation errors.

Core Features & Use Cases

  • Keyword Search: Quickly locate existing specs related to a new feature.
  • Adjacency Lookup: Review full spec content and status to detect overlaps.
  • Classification & Cross‑Reference: Categorize overlaps as duplicate, overlapping, complementary, or conflicting and take appropriate actions.
  • Reference Update: Refresh master indexes and related documentation after changes.
  • Use Cases: Before drafting a new spec, during periodic spec cleanup, or after major scope changes.

Quick Start

Ask the skill to analyze the plan/specs/ directory and suggest deduplication steps for any overlapping specifications.

Frequently Asked Questions about review-specs

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

FAQPage Schema
How do I find and remove duplicate specs in a project directory?▼

To remove duplicate specs, perform keyword searches and adjacency lookups in the project's plan/specs/ directory to identify overlapping content, classify the overlaps, and update master indexes to maintain consistency.

How do I resolve conflicting specifications during spec cleanup?▼

Resolve conflicting specifications by cross-referencing related specs, classifying the conflicts as duplicate, overlapping, complementary, or conflicting, and applying the appropriate deduplication workflow actions.

What is the best way to manage spec consistency after major scope changes?▼

The best way to manage spec consistency after scope changes is to analyze the plan/specs/ directory for overlapping or contradictory specifications, classify the overlaps, and refresh master indexes and related documentation.

When should I run a spec deduplication workflow on my documentation?▼

You should run a spec deduplication workflow before drafting a new spec, during periodic spec repository cleanup, or immediately after major project scope changes to prevent implementation errors.

Can I classify overlapping specifications as complementary instead of deleting them?▼

Yes, you can classify overlapping specifications as duplicate, overlapping, complementary, or conflicting, allowing you to take appropriate actions like preserving complementary specs instead of eliminating them.

Why do spec repositories accumulate contradictory specifications and how is this prevented?▼

Spec repositories accumulate contradictory specifications due to untracked updates, which is prevented by cross-referencing new features against existing specs and updating master indexes to maintain spec consistency.

Related Skills

Explore More Product & Management Skills→
pradeepmoulipradeepmouli
2

speckit-workflows.baseline

Execute a script to generate baseline-spec.md and current-state.md from JSON output.

Community
Advanced
cslsoftwarescslsoftwares

governance-spec-reviewer

Audit SPEC and PRD for security, database edge cases, and rollback gaps.

Community
Advanced
v1bh0rv1bh0r

nw-collapse-detection

Detect documentation collapse by identifying type-mixing across adjacent quadrants.

Community
Intermediate
ksciuskscius
2

fix-merge-conflicts

Resolve Git merge conflicts and verify buildable, test-passing state.

Community
Advanced