skills.rest
datamonsterr
datamonsterrCOMMUNITY
Explore all skills by this author →
GitHub

speckit-sync-analyze

Compare spec requirements against code to identify drift and unspecced code.

Updated Apr 12, 2026
Search Tags:#specification#reporting#spec#alignment#drift#code-coverage#analyze
One-click install
npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-sync-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-sync-analyze
Source: https://github.com/datamonsterr/mycoai_projects/tree/main/.agents/skills/speckit-sync-analyze
Command: npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-sync-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze drift between specifications and implementation. This command compares your spec requirements (FR-, SC-, acceptance scenarios) against the actual codebase to identify where they've diverged.

Core Features & Use Cases

  • Discover Specs: Find all spec files in the project.
  • Analyze Implementation: Determine alignment between spec requirements and code/components.
  • Detect Unspecced Code: Surface code areas not covered by any spec for review.

Quick Start

Run the speckit-sync-analyze command to generate a drift report for your project.

Frequently Asked Questions about speckit-sync-analyze

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

FAQPage Schema
How do I detect drift between my project specifications and codebase?▼

Spec-code drift analysis compares spec requirements (FR-*, SC-*, acceptance criteria) against the actual codebase to validate mappings and identify unspecced code areas where your implementation has diverged from written specifications.

What is the best way to find unspecced code in a repository?▼

Finding unspecced code involves analyzing the codebase against existing specifications to surface code areas not covered by any spec, ensuring all implementation has corresponding requirements mapped for review.

How does spec-code alignment analysis validate acceptance criteria?▼

Spec-code alignment analysis validates acceptance criteria by mapping them to corresponding code, tests, and entities, checking the mappings between specifications and actual implementation to ensure full requirement coverage.

Do I need a specific directory structure to analyze specification drift?▼

Yes, specification drift analysis requires a project with a .specify/ directory and a compatible spec-kit structure to accurately compare multiple specs and code modules across the codebase.

Can I check alignment across multiple specs and code modules at once?▼

Yes, you can analyze alignment across multiple specs and code modules simultaneously by validating mappings between all spec requirements and their corresponding code, tests, and entities to produce a comprehensive drift report.

Why are my specification requirements not matching the implemented code?▼

Specification requirements may not match implemented code due to spec-code drift, which occurs when development changes outpace spec updates; running a drift analysis identifies these exact alignment gaps and unspecced code.

Related Skills

Explore More Software Engineering Skills→
ins-encoins-enco

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and coverage gaps.

Official
Advanced
joshsmithxrmjoshsmithxrm
5

spec-audit

Audit specifications against codebases to identify drift, gaps, and undocumented behavior.

Community
Advanced
tsunami28tsunami28

create-verify-test-coverage

Measure line coverage and validate acceptance criteria tests before release.

Community
Advanced
CatsofsufferingCatsofsuffering
5

verify-module

Scan module directories to validate documentation presence and structural integrity.

Community
Intermediate