deadwood

Classify and archive codebase components that no longer serve the intended topology.

1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/JDHayesBC/Awareness --skill deadwood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deadwood
Source: https://github.com/JDHayesBC/Awareness/tree/main/.claude/skills/deadwood
Command: npx skills add https://github.com/JDHayesBC/Awareness --skill deadwood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies components that no longer serve the intended topology and provides a safe, structured approach to archive, flag, or remove them, preventing drift and maintenance debt.

Core Features & Use Cases

  • Topology-aligned classification: distinguishes ACTIVE, PIONEER, NURSE, DIVERGENT, SUSPECT, and DEADWOOD statuses.
  • Archival workflow: safely move items to root bank or set aside for revival and review.
  • Decision framework: explicit criteria for when to archive, mark, or remove items.
  • Use Case: After drift is surfaced by canopy, identify candidates and schedule them for archival actions.

Quick Start

Run the deadwood classification after canopy to identify drifted components and schedule them for archiving.

Frequently Asked Questions about deadwood

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

FAQPage Schema
How do I archive code that no longer fits my project topology?

To archive code that no longer fits your project topology, you apply a classification taxonomy that categorizes components into statuses like ACTIVE or DEADWOOD, safely moving drifted items to an archive or scheduling them for removal.

What is the best way to classify code components for archival workflows?

The best way to classify code components for archival workflows is to use a topology-aligned taxonomy, distinguishing items as ACTIVE, PIONEER, NURSE, DIVERGENT, SUSPECT, or DEADWOOD to decide whether to archive, mark, or remove them.

When do I need to run code cleanup and archival workflows on my codebase?

You need to run code cleanup and archival workflows when canopy surfaces drift or weight across code, docs, and configurations, indicating components no longer serve the intended project topology and require structured removal.

Can I archive configurations and documentation, or just source code?

Yes, you can archive configurations and documentation. The archival workflow operates across code, docs, and configurations within a codebase, ensuring all drifted components are classified and preserved for revival or removal.

What are the limitations of using a classification taxonomy for code cleanup?

A limitation of using a classification taxonomy for code cleanup is that it requires drift or weight to be surfaced beforehand by canopy, meaning it cannot independently detect topology misalignment without prior analysis.