dustoff

Evaluate dormant project state and generate a prioritized re-entry plan.

421|49|Updated Jul 3, 2014
One-click install
npx skills add https://github.com/joshukraine/dotfiles --skill dustoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dustoff
Source: https://github.com/joshukraine/dotfiles/tree/main/claude/.claude/skills/dustoff
Command: npx skills add https://github.com/joshukraine/dotfiles --skill dustoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you assess and create a prioritized re-entry plan for a project that has been dormant for months, identifying what's stale or broken and how far the project's tooling has drifted from current conventions.

Core Features & Use Cases

  • Project Assessment: Evaluate the project's lifecycle stage, tooling drift, and health.
  • Re-entry Plan: Generate a prioritized plan for reactivating the project.
  • Tracking: Optionally capture the plan as a tracking issue for future reference.
  • Use Case: After a long absence from a project, use this Skill to quickly understand the project's current state and create a plan to get it back into active development.

Quick Start

Run the dustoff skill to assess your dormant project and generate a re-entry plan.

Frequently Asked Questions about dustoff

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

FAQPage Schema
How do I assess codebase health and tooling drift in a dormant project?

To assess codebase health, you evaluate the project's lifecycle stage and identify tooling drift from current conventions. This generates a prioritized re-entry plan to reactivate the dormant codebase.

What is the best way to create a re-entry plan for an inactive codebase?

The best way to create a re-entry plan is to analyze the repository, identify tooling drift, and generate a prioritized list of issues. This plan guides the reactivation of an inactive codebase.

Can I track the project assessment results as an issue for future reference?

Yes, you can optionally capture the generated re-entry plan as a tracking issue. This ensures the project assessment results and prioritized recovery steps are documented for future reference.

Does this project assessment tool require access to the repository?

Yes, the project assessment requires access to the project's repository and the current conventions stored under the .claude directory. This access is needed to accurately evaluate tooling drift.

How do I identify what is stale or broken in a dormant project?

You identify what is stale or broken by running an evaluation of the dormant project. This checks for tooling drift, lifecycle stage issues, and generates a prioritized re-entry plan.