skills.rest
kaptinlin
kaptinlinCOMMUNITY
Explore all skills by this author →
GitHub

spec-gap-analyzing

Survey SPECS and implementation to produce a structured ANALYSIS.md gap analysis.

23|2|Updated Jun 9, 2025
Search Tags:#planning#architecture#analysis#specs#gap-analysis#code-alignment
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill spec-gap-analyzing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-gap-analyzing
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/spec-gap-analyzing
Command: npx skills add https://github.com/kaptinlin/gozod --skill spec-gap-analyzing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify gaps between SPECS and code and generate a concrete ANALYSIS.md at the project root to guide implementation scope, priorities, and structure.

Core Features & Use Cases

  • Survey SPECS and implementation to build a complete picture of requirements and current state.
  • Analyze gaps between spec and code, categorize them (Missing, Partial, Divergent, Untested), and prioritize.
  • Generate ANALYSIS.md at project root detailing scope, priority, structure, dependencies, and integration considerations.

Quick Start

Invoke the spec-gap-analyzing skill to survey SPECS and code, then generate ANALYSIS.md at the project root.

Frequently Asked Questions about spec-gap-analyzing

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

FAQPage Schema
How do I analyze gaps between project specs and code implementation?▼

Spec gap analysis involves surveying your SPECS directory and implementation modules to identify mismatches. This skill categorizes discrepancies as Missing, Partial, Divergent, or Untested, then generates a structured ANALYSIS.md file at your project root detailing scope and priorities.

What is the best way to document missing requirements and code alignment issues?▼

Documenting code alignment issues is best done by generating an ANALYSIS.md file at your project root. This structured plan captures scope, priorities, structure, dependencies, and integration considerations for your implementation workflow.

How do I generate a structured implementation plan from existing specifications?▼

To generate an implementation plan from specifications, survey your SPECS folder and current codebase. The skill compiles a comprehensive ANALYSIS.md plan at the project root without requiring any runtime execution.

Does this gap analysis approach require running my application code?▼

This gap analysis approach requires no runtime execution. It relies purely on visiting your SPECS directory and implementation modules to compile a comprehensive plan and output the ANALYSIS.md document.

Can I categorize and prioritize untested or divergent features in my codebase?▼

You can categorize and prioritize untested or divergent features by analyzing gaps between your specs and code. The skill identifies these discrepancies and outputs a prioritized structure in the generated ANALYSIS.md file.

When do I need to create an ANALYSIS.md file for software architecture planning?▼

Creating an ANALYSIS.md file for architecture planning is needed when identifying gaps between SPECS and implementation. It captures scope, priorities, structure, and dependencies to shape your subsequent implementation work.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

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

Community
Advanced
BurburtonBurburton

architecture-doc-sync

Synchronize architecture documents with implementation changes and generate a traceability report.

Community
Advanced
ImLpImLp

trace

Trace upstream and downstream module dependencies to generate a structured dependency map.

Community
Advanced
zcacereszcaceres
7

test

Identify untested branches, error paths, and boundary conditions in test suites.

Community
Intermediate