drift-guard

Classify project deviations by divergence and reversibility into four response severities.

5|1|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/faroukBakari/trader-pro --skill drift-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift-guard
Source: https://github.com/faroukBakari/trader-pro/tree/main/.github/skills/drift-guard
Command: npx skills add https://github.com/faroukBakari/trader-pro --skill drift-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift Guard provides a structured framework to detect mid-flight deviations from the original plan and guide calibrated responses, helping teams avoid silent misalignment and scope creep.

Core Features & Use Cases

  • Phase-based deviation detection with continuous monitoring and signals for Blocker, Surprise, Scope pull, New concern, Approach failure, External mismatch.
  • Two-Dimensional Classification across Divergence and Reversibility to map to COSMETIC, TACTICAL, STRATEGIC, and CRITICAL severities.
  • Escalation safeguard that auto-upgrades unresolved Tactical deviations to Strategic after two failed self-resolution attempts to prevent escalation fatigue.

Quick Start

Determine if a deviation exists in the current work, classify it by divergence and reversibility, and select the appropriate response per the framework.

Frequently Asked Questions about drift-guard

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

FAQPage Schema
How do I detect mid-flight deviations in software projects before they cause scope creep?

Classify software project deviations using a two-dimensional matrix measuring divergence against reversibility. This framework maps deviations to COSMETIC, TACTICAL, STRATEGIC, or CRITICAL severities, guiding calibrated responses based on the deviation's impact and how easily it can be undone.

What is the best way to handle unresolved tactical deviations during change management?

Handle unresolved tactical deviations using an escalation safeguard that auto-upgrades them to strategic severity after two failed self-resolution attempts. This prevents escalation fatigue and ensures persistent project governance issues receive appropriate strategic attention.

When do I need a structured deviation detection framework for software engineering?

You need a structured deviation detection framework when ongoing software projects experience approach failures, external mismatches, or surprise blockers. It provides project governance by applying a divergence-reversibility classification to map concerns and maintain alignment with the original plan.

Does this deviation detection approach work for all types of project blockers?

Yes, deviation detection works for blockers, surprises, scope pulls, new concerns, approach failures, and external mismatches. It classifies these signals across divergence and reversibility dimensions to determine appropriate cosmetic, tactical, strategic, or critical responses.

How do I start applying drift classification to manage scope changes?

Start applying drift classification by determining if a deviation exists in current work, then classifying it by divergence and reversibility. Select the appropriate response per the framework's cosmetic, tactical, strategic, or critical severity mapping to guide project decisions.