speclink-drift

Detect and analyze drift in Speclink changes against the current codebase state.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speclink-drift
Source: https://github.com/MomoChenisMe/speclink/tree/main/.agents/skills/speclink-drift
Command: npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Drift Detection: Identifies time dormancy, broken design anchors, and task collisions.
  • Analysis: Provides a detailed report on drift, including severity and recommendations.
  • Interactivity: Offers interactive recommendations for handling drift issues.

Quick Start

Run /speclink-drift to analyze and detect drift in your Speclink change.

Frequently Asked Questions about speclink-drift

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

FAQPage Schema
What is Speclink drift detection and how does it identify codebase analysis issues?

Speclink drift detection identifies discrepancies between a Speclink change and the current codebase state. It analyzes the codebase to detect time dormancy, broken design anchors, and task collisions, providing a detailed report with severity levels and recommendations.

How do I detect task collisions and broken design anchors in my codebase?

You can detect task collisions and broken design anchors by running the drift analysis command. The analysis compares your specified change against the current codebase state to locate these specific structural conflicts and reports them interactively.

How do I get recommendations for handling time dormancy in Speclink changes?

To get recommendations for handling time dormancy, execute the drift detection command. The Skill evaluates the change against your codebase, identifies dormancy issues, and provides interactive recommendations and severity ratings to guide your resolution.

Can I use this drift detection Skill without installing external dependencies?

Yes, you can use this drift detection Skill without external dependencies. It operates independently using its built-in scripts to analyze your Speclink changes and codebase state, requiring no additional package installations to generate reports.

What is the best way to manage change drift when updating a codebase?

The best way to manage change drift is to perform a comprehensive codebase analysis comparing the proposed change with the current state. This detects time dormancy, broken anchors, and task collisions early, providing actionable recommendations to address severity issues.

Why does my Speclink change have broken design anchors after a codebase update?

Broken design anchors occur because of drift between your Speclink change and the updated codebase state. As the codebase evolves, previously defined anchors may become invalid, which the drift detection analysis identifies and recommends how to handle.