Agent skill · operations · aiskillstore
check-plan
Audit implementation progress against a plan, verify completed work, identify remaining tasks, and validate quality. Use when user asks to check plan status, verify implementation, see what's left to do, or validate plan completion.
Why this skill is useful
Provides a structured audit process for implementation verification that includes specific commands and quality checks not commonly known.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Check Plan Implementation Instructions Perform comprehensive audit of implementation progress against a plan, verify quality of completed work, and generate actionable task list for remaining items. Phase 1: Setup & Discovery Step 1: Identify the Plan Ask user which plan to check (or identify from context) Read the plan file from .plans/ Understand all plan items and requirements Step 2: Get Git Context (if applicable) This helps understand scope of changes made. Step 3: Identify All Affected Files Create comprehensive list: 1. Files mentioned in the plan 2. Files shown in git status 3. Files that might be affected (use Glob/Grep) Create todo list with one item per file to check. Phase 2: Systematic File-by-File Audit For EACH file in the todo list: Step 1: Read the File Use Read tool to examine current state Check memory/context for any previous notes about this file Step 2: Map to Plan Items Identify which plan step(s) relate to this file: Which implementation steps mention this file? What changes were supposed to be made? What requirements from the plan apply here? Step 3: Verify Implementation Check if planned changes are present: ✅ DONE: Implementation matches plan requirements ⚠️ PARTIAL: Some work done, but incomplete ❌ NOT DONE: No implementation yet 🔍 NEEDS REVIEW: Implementation exists but may not match plan For each file, assess: Are planned features implemented? Is code quality good? Are types used correctly (no any)? Does it follow CLAUDE.md guidelines? Is it complete or partial? Step 4: Quality Verification Check implementation quality: Correctness: Does it work as planned? Types: Proper typing, no any, using existing types? Naming: Follows conventions from plan? Architecture: Matches planned design? Completeness: All details from plan step implemented? Step 5: Record Assessment Store in memory: Step 6: Update Todo Mark file as checked in the todo list. Phase 3: REMOVAL SPEC Verification CRITICAL: Verify old code was actually removed. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/check-plan