Use when the user asks about plan drift, reality check, comparing docs to code, project state analysis, roadmap alignment, implementation gaps, or needs guidance on identifying discrepancies between documented plans and actual implementation state.
SkillScore87Maintained
Automatic
◆Project Management pack
Last verified 8/14/2026
What it changes
Passed 19 of 22 test cases with the skill, and 11 of 22 without it.
Without skill48%
With skill87%
Checks it passed that the model alone missed
Yields a calculated priority score of 36.
Assigns semantic synthesis to Claude Opus.
Uses header string '### Short-Term (This Month)'.
and 6 more in the full report
9 fixed11 passed either way3 still failing0 broke
Pass-rate lift
+39 pp
Tokens
+57%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 8/14/2026v120 of 23 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
What metadata field line follows Severity in the markdown template for a Drift Analysis section?
What was checked, without and with the skill
Checked
Without skill
With skill
Includes line format '**Detected In**: {source}'.
Missed
Passed
case-13 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md318 linessingle file
Drift Analysis
Knowledge and patterns for analyzing project state, detecting plan drift, and creating prioritized reconstruction plans.
Architecture Overview
/drift-detect
│
├─→ collectors.js (pure JavaScript)
│ ├─ scanGitHubState()
│ ├─ analyzeDocumentation()
│ └─ scanCodebase()
│
└─→ plan-synthesizer (Opus)
└─ Deep semantic analysis with full context
Data collection: Pure JavaScript (no LLM overhead)
Semantic analysis: Single Opus call with complete context
Drift Detection Patterns
Types of Drift
Plan Drift: When documented plans diverge from actual implementation
PLAN.md items remain unchecked for extended periods
Roadmap milestones slip without updates
Sprint/phase goals not reflected in code changes
Documentation Drift: When documentation falls behind implementation
New features exist without corresponding docs
README describes features that don't exist
API docs don't match actual endpoints
Issue Drift: When issue tracking diverges from reality