generated-cleanup

To automate artifact retirement, this Skill scans project-generated files, groups outdated candidates based on lifecycle staleness, and proposes cleanup actions. It uses file frontmatter metadata and lint reports to recommend retirement before any archiving operations occur.

Artifact lifecycle management involves tracking generated project files from creation to retirement. You need cleanup tracking when managing program-generated artifacts becomes complex, requiring automated identification of stale content to maintain documentation maturity and operational hygiene.

You identify stale artifacts by running the Skill to parse frontmatter metadata and analyze artifact lint reports. It evaluates lifecycle states to classify outdated files, grouping them into retirement candidate sets for PMO practitioners to review.

Yes, the artifact-generator dependency is required. This Skill builds upon generated artifacts to evaluate their lifecycle state, relying on the upstream generation process to provide the foundational files and metadata necessary for staleness analysis and retirement proposals.

No, you cannot execute archiving directly. The Skill only recommends cleanup actions requiring operator approval before executing. It groups candidates and proposes retirement strategies, ensuring human oversight before any actual artifact deletion or archiving occurs.

The best way to manage content maturity is scanning generated artifacts to classify their lifecycle state and staleness. This Skill supports PMO practitioners by automatically grouping retirement candidates and proposing targeted cleanup actions to maintain program hygiene.