Drift
Description
Read the Genesis build phases document: docs/architecture/genesis-v3-build-phases.md Read the git log for the last 60 days: git log --oneline --since="60 days ago" Read the current directory structure (excluding docs/). For each build phase: 1. What does the plan say should be implemented? 2. What evidence exists in the codebase that it IS implemented? 3. What is missing? 4. What exists in the code that is NOT in any plan? (scope creep or discovery?) Output a structured drift report: - I
Installation
Installs to ~/.claude/commands/wingedguardian-genesis-agi-drift.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/WingedGuardian/GENesis-AGI/HEAD/.claude/commands/drift.md -o ~/.claude/commands/wingedguardian-genesis-agi-drift.md Restart Claude Code, or start a new session, for it to be picked up.
Full documentation available on GitHub
View Source RepositoryRelated Skills
Awesome Go
A curated list of awesome Go frameworks, libraries and software
Development next.js
| The React Framework | 138360 | 1503 | 1 |
Development sharing-skills
skill for guidance.
Development root-cause-tracing
Use when errors occur deep in execution and you need to trace back to find the original trigger.
Development Template Skill
Minimal skeleton for a new skill project structure.
Development Third-party Notices
THE FOLLOWING SETS FORTH ATTRIBUTION NOTICES FOR THIRD PARTY SOFTWARE THAT MAY BE CONTAINED IN PORTIONS OF THI
Development