spectra-drift

Detect drift between Spectra changes and the current codebase state.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MomoChenisMe/test-sdd-workflow --skill spectra-drift-momochenisme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-drift
Source: https://github.com/MomoChenisMe/test-sdd-workflow/tree/main/spectra-test/.claude/skills/spectra-drift
Command: npx skills add https://github.com/MomoChenisMe/test-sdd-workflow --skill spectra-drift-momochenisme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires spectra, and includes scripts (resource) components.

What problem does it solve?

This Skill detects drift between a Spectra change and the current codebase state, identifying issues like time dormancy, broken design anchors, and task collisions.

Core Features & Use Cases

  • Drift Detection: Identifies drifts such as time dormancy, broken design anchors, and task collisions.
  • Contextual Analysis: Provides a report with a plain-language conclusion and detailed technical information.
  • Interactive Recommendations: Offers actionable recommendations based on the severity of the drift.

Quick Start

Run /spectra-drift <change-name> to detect drift for a specific change.

Frequently Asked Questions about spectra-drift

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

FAQPage Schema
How do I detect codebase drift caused by pending changes?

To detect codebase drift, you can run a drift detection analysis that compares pending changes against the current codebase state to identify time dormancy, broken design anchors, and task collisions. This generates a report with actionable recommendations.

What is drift detection in change management?

Drift detection in change management is the process of identifying discrepancies between planned changes and the actual codebase state. It analyzes issues like time dormancy, broken design anchors, and task collisions to provide a contextual report with technical details and recommendations.

Do I need the spectra CLI to run drift reporting?

Yes, you need the spectra CLI installed to run drift reporting. The Skill requires the spectra command-line interface to analyze codebase state, detect task collisions, and generate actionable drift reports.

How do I analyze broken design anchors and task collisions?

You can analyze broken design anchors and task collisions by running a drift detection command with your specific change name. The analysis examines time dormancy and anchor integrity, outputting a detailed technical report with severity-based recommendations.

What's the best way to report drift between changes and codebase state?

The best way to report drift is to use an automated drift detection tool that compares changes against codebase state and generates a plain-language conclusion alongside detailed technical information, offering interactive recommendations based on drift severity.