ai-workflow-framework: Skill for Claude Code

Project Cleanup — Enhanced

Complete project maintenance: Validation → Audit → Cleanup → Application.

Each phase presents numbered sub-tasks. User replies with task numbers to run (1,3,5, all, or skip), then those tasks execute sequentially with pauses for confirmation before application.

---

Preparation — Read all files

Before producing any proposal, read:

• TODO.md — full file
• SESSION.md — full file (KEY LEARNINGS + all chronological entries)
• INSIGHTS.md — full file
• CLAUDE.md — for gaps and content audit
• .gitignore — verify local-only working directories are excluded appropriately
• .reference/INDEX.md — verify it exists and is current
• .reference/ folder — list all files and check their metadata

Also identify:

• Project .claude/skills/ directory
• Global skills directory (if configured for cross-project reuse)

---

Phase 1 — VALIDATION (Check doc consistency)

Sub-tasks:

1. SESSION.md link audit — Check for broken/outdated file references
2. INSIGHTS.md file validation — Verify referenced files exist
3. .reference/ health check — Verify metadata complete + fresh (Last reviewed ≤ 30 days)
4. CLAUDE.md gap detection — Check if "CLAUDE.md Gaps" from INSIGHTS are documented
5. Broken internal refs in skills — Find stale paths in skill files

→ Which validation tasks to run? Reply: 1, 2, 3, 1,3,5, all, or skip

After user replies:

For each selected task, perform the audit and report findings:

• Task 1: List broken SESSION.md links + suggested corrections
• Task 2: List missing files/folders referenced in INSIGHTS.md
• Task 3: List .reference/ files with missing/stale metadata
• Task 4: List CLAUDE.md gaps NOT yet documented
• Task 5: List skill files containing stale .ai-notes/ paths

Present one task result at a time. After all selected tasks complete, ask:

Validation complete. Proceed to Phase 2 (Audit)?
→ Reply: yes, or skip to Phase 3/4

---

Phase 2 — AUDIT (Check INSIGHTS integrity)