generated-cleanup

Identify and recommend retirement for stale project artifacts from file frontmatter and lint reports.

Updated Jun 5, 2026

Search Tags:#project management #lifecycle management #artifact cleanup #retirement proposal #artifact retirement

Ready to run

npx skills add https://github.com/cody-hutson/pmo-platform --skill generated-cleanup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generated-cleanup
Source: https://github.com/cody-hutson/pmo-platform/tree/main/operations/skills/generated-cleanup
Command: npx skills add https://github.com/cody-hutson/pmo-platform --skill generated-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires artifact-generator, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically scans project-generated artifacts, groups candidates for retirement, and proposes cleanup actions before any archiving occurs.

Core Features & Use Cases

Artifact Scan: Scans all project-generated artifacts in specified locations.
Group Candidates: Classifies artifacts into retirement candidate groups based on their lifecycle state and staleness.
Cleanup Proposal: Recommends cleanup actions requiring operator approval before executing.

Quick Start

Run the 'generated-cleanup' skill to automatically review and propose retirement for outdated project artifacts.

Frequently Asked Questions about generated-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate artifact retirement proposals for outdated project files?▼

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.

What is artifact lifecycle management and when do I need cleanup tracking?▼

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.

How do I identify stale artifacts using frontmatter metadata and lint reports?▼

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.

Do I need the artifact-generator dependency to propose artifact cleanup actions?▼

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.

Can I execute file archiving directly during the artifact retirement process?▼

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.

What is the best way to manage content maturity for program-generated artifacts?▼

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.