drift-analysis

Identify and quantify drift between documentation, plans, and code.

951|110|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/avifenesh/awesome-slash --skill drift-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drift-analysis
Source: https://github.com/avifenesh/awesome-slash/tree/main/plugins/drift-detect/skills/drift-analysis
Command: npx skills add https://github.com/avifenesh/awesome-slash --skill drift-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift Analysis helps teams identify misalignments between documented plans and actual implementation, enabling proactive corrections and a clearer path to reconstruction.

Core Features & Use Cases

  • Detects plan drift between README, PLAN.md, roadmaps, and code changes.
  • Generates prioritized reconstruction plans with actionable steps.
  • Produces drift reports that inform product strategy, documentation, and sprint planning.
  • Real-world use case: compare project documentation with code state to surface overdue milestones and missing features.

Quick Start

Run drift analysis on the current project data to generate a reality-check report.

Frequently Asked Questions about drift-analysis

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

FAQPage Schema
How do I detect documentation and code drift in my repository?▼

Documentation and code drift is detected by analyzing milestones, readme features, and implementation gaps to reveal misalignments and produce a prioritized reconstruction plan.

What is plan drift analysis in software engineering?▼

Plan drift analysis identifies and quantifies misalignments between documented plans like roadmaps and actual code changes to surface overdue milestones and missing features.

How do I generate a prioritized reconstruction plan for missing features?▼

A prioritized reconstruction plan is generated by running a drift analysis on your repository's issues, docs, and code to compare project documentation with the current code state.

Does drift analysis work with standard markdown documentation and roadmaps?▼

Drift analysis works with standard markdown documentation by comparing README files, PLAN.md documents, roadmaps, and code changes to quantify implementation gaps.

Can I use drift reports to inform sprint planning and product strategy?▼

Drift reports inform product strategy, documentation updates, and sprint planning by surfacing overdue milestones and generating actionable steps for proactive corrections.