plan-backlog

Scan planning directories and roadmap for backlog hygiene issues.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill plan-backlog-leocosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-backlog
Source: https://github.com/leocosta/octopus/tree/main/skills/plan-backlog
Command: npx skills add https://github.com/leocosta/octopus --skill plan-backlog-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan the repo's planning directories and roadmap for hygiene issues — orphan plans, plans for completed RMs outside archive, duplicates for one RM, broken internal links, roadmap entries without a plan, and stale plans. Read-only by default; --fix applies reversible moves to plans/archive/.

Core Features & Use Cases

  • Inspect planning directories (plans/, docs/plans/) and roadmap file to surface hygiene issues
  • Flag orphan, concluded, duplicate, broken-link, roadmap-orphan, and stale entries
  • Optional --fix to relocate concluded plans to an archive, preserving history via git mv
  • Generate reports for hygiene digests and integrate with a weekly or monthly cycle

Quick Start

Run the plan-backlog command to generate a live backlog hygiene report.

Frequently Asked Questions about plan-backlog

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

FAQPage Schema
How do I detect orphan plans and stale items in my project roadmap?

You can detect orphan plans by scanning planning directories like plans/ and docs/roadmap.md to identify orphan, concluded, duplicate, broken-link, and stale entries. The tool outputs a structured, severity-based report highlighting roadmap orphans and hygiene issues.

What is backlog hygiene and why does it matter for planning directories?

Backlog hygiene is the practice of maintaining planning directories by identifying orphan, concluded, duplicate, broken-link, and stale items. It ensures your roadmap and plans/ folders remain accurate, preventing outdated entries from obscuring active project status.

How do I archive concluded plans without losing git history?

Archive concluded plans without losing git history by running the scan with an optional --fix flag. This executes reversible git mv operations to relocate completed plans into a plans/archive/ directory, preserving the full commit history of the moved files.

Does the backlog hygiene scan modify my planning files by default?

The backlog hygiene scan is read-only by default and does not modify any files. It only generates a structured report of orphan, duplicate, and stale entries, requiring an explicit --fix flag to apply reversible archival moves to plans/archive/.

Can I generate a recurring backlog hygiene report for a weekly planning cycle?

Yes, you can generate recurring backlog hygiene reports for a weekly or monthly planning cycle. The scan produces structured hygiene digests of detected issues, supporting seamless integration into your regular reporting and development workflow.

What types of broken links and duplicate entries does a backlog hygiene check identify?

A backlog hygiene check identifies broken internal links within planning files, duplicate plans associated with a single RM, and roadmap orphans lacking corresponding plans. It also flags concluded plans remaining outside the plans/archive/ directory.