cleanup-artifacts
Cleanup Artifacts — Orchestrator
Meta — Single-agent orchestration with built-in critic gate. Audits and grooms the project's .agents/ tree, classifying every artifact and (with explicit per-category confirmation) MOVING stale/orphan/legacy/ephemeral files to a dated archive. Never deletes.
Core Question: "Is this artifact still load-bearing for the project, or is it accumulated cruft from a skill run that finished weeks ago?"
Critical Gates — Read First
- MOVE, never delete. Even after explicit operator confirmation, the destructive action is
mvinto.agents/skill-artifacts/.archive/[YYYY-MM-DD]/. A separate--purge-archiveflag (out of scope for v1) is the only path to actual deletion. This guarantees recoverability. - HARD-NEVER paths. The skill MUST refuse to touch any of these, even if they appear stale:
brand/— canonical brand identity (lifecycle: canonical)research/— canonical audience + market record (lifecycle: canonical)architecture/— canonical system blueprint (lifecycle: canonical).git/and.gitmodules— version control state- any submodule directory (entries in
.gitmodules) .agents/manifest.json— infrastructure, regenerated bymanifest-sync.ts.agents/experience/— Q&A substrate, append-only by every skill.agents/skill-artifacts/meta/roadmap.mdandtasks.md— session anchors
- Default mode is
--dry-run. No file is moved without an explicit--applyflag AND per-category operator confirmation.
More from hungv47/meta-skills
task-breakdown
Decomposes a spec or architecture into buildable tasks with acceptance criteria, dependencies, and implementation order for AI agents or engineers. Produces `.agents/skill-artifacts/meta/tasks.md`. Not for clarifying unclear requirements (use discover) or designing architecture (use system-architecture). For code quality checks after building, see fresh-eyes.
79discover
Conversational discovery — adapts from quick scoping (3-5 questions) to deep interviews (multi-round). Talk until we're clear, then build. Produces inline decisions; optionally saves spec.md or scope contract. Not for multi-perspective debate (use agents-panel). Not for decomposing work (use task-breakdown). Not for diagnosing a known metric decline or root-causing a problem (use diagnose).
76agent-room
Multi-agent discussion rooms — debate or poll a problem from multiple perspectives. Standalone or invoked by other skills as a sub-routine. Mode=debate: N agents argue in rounds, converge. Mode=poll: N agents independently analyze, aggregate by consensus. Not for implementation (use system-architecture). Not for verification (use review-chain). For clarifying requirements first, see discover. For decomposing work after a decision, see task-breakdown.
67review-chain
Post-implementation quality check via fresh-eyes review. Chain: Implement → Review (independent agent) → Resolve (if issues). Max 2 rounds. Auto-triggers for security-sensitive and data-mutation code. Not for code refactoring (use code-cleanup). Not for decision analysis (use agent-room).
61navigate
Artifact status + multi-phase orchestration. Scan what exists, check freshness, compose and track complex workflows across sessions. Not for skill routing (the agent does that proactively).
57fresh-eyes
Post-implementation quality check via fresh-eyes review. Chain: Implement → Review (independent agent) → Resolve (if issues). Max 2 rounds. Auto-triggers for security-sensitive and data-mutation code. Not for code refactoring (use code-cleanup). Not for decision analysis (use agents-panel).
16