plan-manager

Manage plan lifecycles via CLI with validation and staleness checks.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill plan-manager-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-manager
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/plan-manager
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill plan-manager-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Deterministic plan governance and lifecycle consistency for Claude workflows by providing a CLI-driven interface to manage active plans, surface stale work, and prevent drift.

Core Features & Use Cases

  • CLI-driven lifecycle: list, show, create, check, complete, and abandon plans with validation and audit trails.
  • Staleness detection and surfacing at the start of sessions to prevent outdated work from proceeding.
  • Re-read-before-decision and show-before-modify safeguards to ensure correct task direction and state transitions.

Quick Start

Run the CLI to list current plans, then show a plan before performing any lifecycle changes.

Frequently Asked Questions about plan-manager

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

FAQPage Schema
How do I manage plan lifecycle and prevent workflow drift via CLI?

Plan lifecycle management via CLI uses a deterministic workflow to list, create, complete, and abandon plans while enforcing validation and audit trails to prevent state drift. It enforces a CLI-first approach and prohibits direct plan file edits.

How does staleness detection work for active task tracking?

Staleness detection for task tracking runs integrity checks at session start to surface outdated plans before work proceeds. This prevents stale work from advancing by requiring a re-read-before-decision safeguard.

What is the best way to audit a plan governance workflow?

Auditing a plan governance workflow is best handled through a CLI-driven interface that logs errors for auditability and enforces show-before-modify safeguards. Every lifecycle transition is validated and recorded.

Can I edit plan files directly when using a CLI workflow?

Direct plan file edits are prohibited in this CLI workflow to maintain deterministic governance and lifecycle consistency. All plan modifications must go through the CLI to ensure proper validation and audit logging.

Do I need any specific dependencies to run a deterministic plan management script?

No external dependencies are required to run the deterministic plan management script. It operates independently using internal scripts and references, reading guidelines directly to enforce lifecycle control and governance.

When should I use a CLI-driven plan lifecycle tool over manual task tracking?

Use a CLI-driven plan lifecycle tool over manual task tracking when deterministic governance, audit trails, and staleness detection are required. It prevents drift and enforces validation across listing, showing, and completing plans.