ai-workflow-framework: Skill for Claude Code

Project Insights — Triage & Archive

Goal

Help the user keep INSIGHTS.md lean and actionable. Check what's been implemented, what's genuinely still open, and what's gone stale — then confirm with the user section by section before making any changes.

Step 1 — Gather context

Read these files in order:

1. INSIGHTS.md in the current project directory — the items to triage
2. Project CLAUDE.md — to check whether CLAUDE.md gap items have been filled
3. Global agent CLAUDE.md — to check whether items were promoted there already
4. Skills directory listing — to check whether skill candidates/upgrades exist:

ls /

If no global skills directory is configured, skip that check and continue with
project-local evidence.

For **Skill Upgrade** items, go one step further: read the relevant skill's `SKILL.md` briefly to check whether the described improvement is actually present (not just that the skill exists).

For **Automation Ideas** that mention a specific script or alias, check the shell aliases file or the relevant scripts directory.

Also check lightweight docs hygiene signals:
- `.reference/INDEX.md` exists and includes newly promoted files.
- `.reference` docs touched in recent work have updated `Last reviewed`.
- `.reference` metadata includes `Purpose`, `When to use`, `Source of truth`, `Owner`, `Confidence`, `Last reviewed`.
- Reusable docs in `.ai-notes` are flagged as promotion candidates.

---

## Step 2 — Triage each item

Go through every non-archived item in INSIGHTS.md and assign one status:

| Status | Meaning |
|--------|---------|
| ✅ Done | The improvement exists — skill built, CLAUDE.md updated, script implemented, issue resolved |
| ⏳ Open | Not yet implemented, still clearly relevant |
| 📤 Promote to global CLAUDE.md | A project-level CLAUDE.md gap that's universal enough to belong in the global CLAUDE.md |
| 🗑️ Stale | No longer relevant — project direction changed, different approach taken, or won't fix |