coppice

Promote SUSPECT archive items to ACTIVE, PIONEER, or NURSE when revival conditions are met.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive revival tasks by reactivating items in the SUSPECT archive when revival conditions are satisfied in the current project state, ensuring continuity of work that would otherwise be lost.

Core Features & Use Cases

  • Revive eligible archived items when dependencies and decisions are ready
  • Maintain a live activity feed of promoted items with rationale
  • Integrate with the SUSPECT_ARCHIVE.md root bank to guide decisions

Quick Start

Promote items from the SUSPECT archive by running the revival workflow when conditions are met.

Frequently Asked Questions about coppice

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

FAQPage Schema
How do I revive archived project items when dependencies become ready?

Archive revival restores SUSPECT archive items to active workflows when revival conditions are satisfied, ensuring continuity of work across multiple repositories. It consults the root bank to verify dependency readiness before reactivating components into ongoing development.

How does archive revival classify reactivated components in a development workflow?

Archive revival classifies reactivated components by updating their status to ACTIVE, PIONEER, or NURSE as appropriate. This classification is determined by consulting the SUSPECT_ARCHIVE.md root bank and evaluating current project states and dependency readiness.

Can I reactivate archived items across multiple repositories and project states?

Yes, you can reactivate archived items across multiple repositories and project states. The revival workflow evaluates ongoing development workflows globally to determine if revival conditions are satisfied for archived components re-entering as dependencies or decisions become ready.

What is a SUSPECT archive in software project management?

A SUSPECT archive is a root bank, maintained in docs/SUSPECT_ARCHIVE.md, that holds deferred project components until their dependencies or decisions are ready. It preserves continuity by tracking items eligible for future revival into active workflows.

When should I not use automated archive revival for project components?

You should not use automated archive revival when explicit revival criteria are not yet satisfied in the current project state. The workflow requires dependencies and decisions to be fully ready before promoting SUSPECT items back into active consideration.