vc:audit-plans
The vc:audit-plans skill reviews active project plan files in a codebase repository to identify staleness, completion status, and routing accuracy. It runs an inventory validator, cross-references plans against actual codebase files using searches, classifies each plan into categories like Completed or Stale, and moves clearly finished plans to archive folders while surfacing stale artifacts for cleanup. Use this maintenance skill when plan drift has accumulated after skipped update processes, conducting periodic cleanups, or reconciling multiple plans following intensive development work.
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit /tmp/vc-audit-plans && cp -r /tmp/vc-audit-plans/.claude/skills/vc-audit-plans ~/.claude/skills/vc-audit-plansSKILL.md
# Audit Plans Use this skill to review active plan artifacts and reconcile them with the current codebase. This is a maintenance and recovery skill, not an automatic post-task hook. Optional input: a feature, folder, plan filename, or maintenance scope to prioritize. Prefer it when: - UPDATE PROCESS was skipped and active-plan cleanup drift accumulated - the user wants a periodic active-plan cleanup pass - multiple active plans need reconciliation after a burst of work ## Workflow 1. Read `references/audit-plans.md` for the full audit process. 2. Run the inventory validator: ```bash node .claude/skills/vc-audit-plans/scripts/validate-plan-inventory.mjs ``` 3. Inventory plans in `process/general-plans/active/` and `process/features/*/active/`. 3.5. Scan sibling `reports/` and `references/` dirs alongside each `active/` dir for artifacts tied to plans classified as Completed or Obsolete. Match by feature slug, date proximity (7 days), or content reference to the plan filename. 4. Cross-check each plan against the actual codebase with file existence checks and targeted `rg` searches. 5. Classify each plan as `Completed`, `Partially Done`, `Obsolete`, `Stale`, `Active`, or `Reference`. 6. Move only clearly completed or obsolete plans to the appropriate `completed/` folder. 7. Ask before deleting anything. 8. Re-run the inventory validator after moving or editing plan files. ## Output Return a concise summary table with classification, action taken, and any user decisions needed. Include stale artifact findings (reports/references tied to completed or obsolete plans) with recommended actions.
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying bottlenecks, analyzing failed deployments, investigating test failures, and creating diagnostic reports. Examples:\n\n<example>\nContext: The user needs to investigate why an API endpoint is returning 500 errors.\nuser: "The /api/users endpoint is throwing 500 errors"\nassistant: "I''ll use the debugger agent to investigate this issue"\n<commentary>\nSince this involves investigating an issue, use the Task tool to launch the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to analyze why the CI/CD pipeline is failing.\nuser: "The GitHub Actions workflow keeps failing on the test step"\nassistant: "Let me use the debugger agent to analyze the CI/CD pipeline logs and identify the issue"\n<commentary>\nThis requires analyzing CI/CD logs and test failures, so use the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user notices performance degradation in the application.\nuser: "The application response times have increased by 300% since yesterday"\nassistant: "I''ll launch the debugger agent to analyze system behavior and identify performance bottlenecks"\n<commentary>\nPerformance analysis and bottleneck identification requires the debugger agent.\n</commentary>\n</example>
EXECUTE MODE - Implementing EXACTLY what was planned. Full tool access. Can only be invoked after explicit user confirmation. Use after plan is approved.
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + INNOVATE + PLAN) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features/*/active/ only. Use after approach is decided.