skills.rest
ivegamsft
ivegamsftCOMMUNITY
Explore all skills by this author →
GitHub

Spec Review

Review architectural specifications for completeness, consistency, and product alignment.

Updated Mar 16, 2026
Search Tags:#code quality#architecture#document analysis#specification review#cross-spec drift
One-click install
npx skills add https://github.com/ivegamsft/work-tracker --skill spec-review-ivegamsft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Spec Review
Source: https://github.com/ivegamsft/work-tracker/tree/main/.squad/skills/spec-review
Command: npx skills add https://github.com/ivegamsft/work-tracker --skill spec-review-ivegamsft

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit helps maintain the integrity of architectural specifications by reviewing them for completeness, consistency, and alignment with product intent.

Core Features & Use Cases

  • Cross-Spec Drift Detection: Identifies discrepancies between specifications and canonical documents.
  • Structural Completeness Check: Ensures specifications are well-organized and complete.
  • Cross-Reference and Alignment: Validates terminology and contracts across multiple documents.
  • Severity-Ranked Findings: Reports issues with criticality rankings for immediate action.

Quick Start

Trigger the Spec Review Skill to review the 'eclat-spec.md' document.

Frequently Asked Questions about Spec Review

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

FAQPage Schema
How do I detect cross-spec drift between architectural specifications and canonical documents?▼

To detect cross-spec drift, you can review architectural specifications using text analysis and regex to identify discrepancies between specifications and canonical product documents, yielding severity-ranked findings for immediate action.

What is the best way to check architectural specifications for structural completeness?▼

Checking architectural specifications for structural completeness involves analyzing the document organization against product intent, ensuring all required sections are present and properly structured through automated document analysis.

How do I validate terminology and contracts across multiple architecture documents?▼

Validating terminology and contracts across multiple architecture documents requires cross-reference analysis to ensure consistent alignment, utilizing git diff and text analysis to verify terms match across related product and architecture documentation.

Do I need access to product documentation to review architecture specifications for consistency?▼

Yes, reviewing architecture specifications for consistency requires access to related product and architecture documentation to validate alignment with product intent and detect cross-spec drift accurately.

How are specification review findings ranked by severity for prioritization?▼

Specification review findings are ranked by severity to prioritize immediate action, categorizing discovered discrepancies and structural issues by criticality so teams can address the most impactful problems first.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
gittowergittower
413

health-audit

Audit repository drift, code quality, and test health in git-flow-next.

Official
Advanced
ofelixdevofelixdev

spec-to-code-compliance

Compare code implementations against specifications and generate compliance reports.

Community
Advanced
gagan114662gagan114662

writing-coach

Enhance written content for clarity, style, and structure.

Community
Basic