lifecycle-audit

Audit historical project files to classify lifecycle state and implementation status.

3|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/zoraxl/team-brain --skill lifecycle-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lifecycle-audit
Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/lifecycle-audit
Command: npx skills add https://github.com/zoraxl/team-brain --skill lifecycle-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the accumulation of messy, unorganized historical data in project repositories by auditing and classifying legacy brainstorms, plans, and PRs.

Core Features & Use Cases

  • Lifecycle Classification: Automatically labels files based on their implementation status, such as confirmed-implemented or superseded.
  • Safe Migration: Proposes organized moves for inbox and plan files into namespace-aware structures before applying changes.
  • Use Case: Use this when you have a cluttered inbox of old ideas and need to identify which ones were actually implemented and which can be safely archived to keep your workspace clean.

Quick Start

Run the lifecycle audit skill to scan the current repository and report on all unclassified brainstorms and plans.

Frequently Asked Questions about lifecycle-audit

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

FAQPage Schema
How do I audit and clean up old project plans and brainstorms in my repository?

To audit and clean up historical project files, this skill scans repository inbox and planning directories to classify brainstorms and plans by implementation status, then proposes organized moves into namespace-aware structures for safe archiving.

What is the best way to classify legacy repository files by their implementation status?

Classifying legacy repository files by implementation status involves verifying implementation evidence against GitHub PR history and repository logs, then automatically labeling files as confirmed-implemented, superseded, or actionable for metadata backfill.

How does lifecycle classification work for unclassified historical plans?

Lifecycle classification for unclassified historical plans works by cross-referencing repository logs and GitHub PR history to verify implementation evidence before proposing file system modifications or archiving actions.

Do I need read access to GitHub PR history to audit repository workflows?

Yes, you need read access to repository logs and GitHub PR history to verify implementation evidence before the audit skill can confidently classify historical brainstorms and plans or propose any file system modifications.

Can I safely archive old brainstorms without losing track of implemented ideas?

You can safely archive old brainstorms because the audit skill verifies implementation evidence against PR history first, classifying files as confirmed-implemented or superseded before proposing any namespace-aware file migrations.

What are the limitations of automating repository workflow cleanup?

A key limitation of automating repository workflow cleanup is that the audit skill only proposes file system modifications rather than applying them directly, requiring manual review of suggested metadata backfills and namespace-aware directory moves.