drift-analysis
A planning aid that identifies discrepancies between project documentation and the actual implementation state.
Install
mkdir -p .claude/skills/drift-analysis && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2563" && unzip -o skill.zip -d .claude/skills/drift-analysis && rm skill.zipInstalls to .claude/skills/drift-analysis
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Detect plan drift between documentation and implementation
- →Identify roadmap milestones overdue by 30+ days
- →Analyze codebase for undocumented features
- →Prioritize drift items using severity and category weights
- →Generate reconstruction plans with time-bound action items
How it works
The skill uses collectors.js to extract state from GitHub, documentation, and code, then passes this context to an Opus-based synthesizer for semantic analysis and prioritization.
Inputs & outputs
When to use drift-analysis
- →Identify discrepancies between docs and code
- →Conduct project state analysis
- →Verify roadmap alignment
- →Audit implementation gaps
About drift-analysis
This skill acts as a reality check for software projects. It analyzes the current state of the codebase against existing documentation to flag implementation gaps and drift from the project roadmap.
This skill should be used 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.
When not to use it
- →Analyzing individual stale issues without looking for patterns
- →Performing real-time code execution or deployment
Prerequisites
Limitations
- →Requires consistent documentation structure to be effective
- →Low-confidence indicators may produce false positives
How it compares
Unlike manual audits, this skill automates cross-referencing between documentation and code using fuzzy matching and predefined drift indicators.
Compared to similar skills
drift-analysis side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| drift-analysis (this skill) | 2 | 8mo | No flags | Intermediate |
| feature-planning | 1 | 1y | No flags | Intermediate |
| validate-implementation-plan | 0 | 6mo | No flags | Advanced |
| create-plan | 36 | 11mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by avifenesh
View all by avifenesh →You might also like
feature-planning
mhattingpete
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
validate-implementation-plan
b-mendoza
Audits an implementation plan for requirements traceability, avoidable complexity, risky assumptions, and evidence gaps. Use when reviewing an AI-generated or human-authored plan, design proposal, implementation outline, task breakdown, or architecture plan and the user wants a standalone audit repo
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
confidence-check
SuperClaude-Org
Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)