drift-analysis
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.
Profile →npx skills add agent-sh/agentsys --skill drift-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 - Stale issues that no longer apply - Completed work without closed issues - High-priority items neglected **Scope Drift**: When project scope expands beyond original plans - More feat
- Architecture Overview
- Drift Detection Patterns
- Types of Drift
- Detection Signals
- Prioritization Framework
- Priority Calculation
- Time Bucket Thresholds
- Priority Weights (Default)
- Cross-Reference Patterns
- Document-to-Code Matching
- Common Mismatches
- Output Templates
- Drift Report Section
- Gap Report Section
What does the drift-analysis skill do?
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.
How do I install it?
Run `npx skills add agent-sh/agentsys --skill drift-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agent-sh/agentsys, a repository with 923 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.