speckit-drift

Analyzes spec-to-code drift and generates a structured report and JSON.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-drift-b0yz4kr14
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-drift
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-drift
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-drift-b0yz4kr14

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the risk of quietly drifting away from your specification by showing exactly where requirements are implemented, missing, or contradicted by the current codebase.

Core Features & Use Cases

  • Requirement-to-code drift analysis: Compares spec requirements (FR-, SC-, acceptance scenarios) against implementation to find alignment vs divergence.
  • Unspecced code detection: Flags commands, services, entities/models, and tests that exist without spec coverage.
  • Actionable drift outputs: Produces both a human-readable report and a machine-readable JSON report suitable for review and automation.

Quick Start

Run the speckit-drift analysis to generate a drift-report for your current codebase and specs.

Frequently Asked Questions about speckit-drift

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

FAQPage Schema
How do I detect spec drift between requirements and my current codebase?

Spec drift is detected by comparing spec markdown requirements like FR-* and acceptance scenarios against implementation code to identify missing implementations and uncovered commands or services. This analysis generates a structured drift report and JSON artifact.

What is requirements traceability analysis for specification-driven development?

Requirements traceability analysis matches functional requirements and acceptance scenarios from spec markdown to corresponding commands, services, entities, and test coverage. It identifies alignment, missing implementations, and unspecced code within the codebase.

How do I find unspecced code that exists without spec coverage?

Unspecced code detection flags commands, services, entities, and tests that exist in the implementation without corresponding spec coverage. It correlates the spec-kit expected structure under .specify with the codebase to find these gaps.

Does speckit-drift output a machine-readable JSON report for automation?

speckit-drift outputs a machine-readable JSON artifact alongside a human-readable drift report. Both outputs are suitable for review processes and automation workflows by parsing the .specify structure and correlating it with implementation code.

Can I analyze acceptance scenarios and match them to test coverage?

Acceptance scenarios from spec markdown are matched to test coverage during the drift analysis. The process correlates specified scenarios with the implementation to show exactly where requirements are covered or contradicted.

What are the limitations of spec-to-code divergence analysis?

Divergence analysis applies specifically to specification-driven workflows using the spec-kit expected structure under .specify. It requires spec markdown containing FR/SC and acceptance scenarios to properly correlate with the implementation codebase.