plan-manage

Coordinate plan lifecycle workflows across .claude/.plans with create, review, execute, archive, and abandon operations.

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/ReefBytes-Owner/Manifest --skill plan-manage-reefbytes-owner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-manage
Source: https://github.com/ReefBytes-Owner/Manifest/tree/main/configs/claude/skills/plan-manage
Command: npx skills add https://github.com/ReefBytes-Owner/Manifest --skill plan-manage-reefbytes-owner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and coordinates the full lifecycle of planning work across the .claude/.plans repository, reducing manual drift and misalignment across teams.

Core Features & Use Cases

  • Create, review, execute, archive, and abandon plans within .claude/.plans with optional parallel-agent orchestration.
  • Cross-agent collaboration: integrates with multiple agents for validation, synthesis, and decision-making.
  • Issue-tracking integration and lifecycle automation: links plans to issues, tracks progress, and archives completed work.
  • Production-ready templates and governance: standardizes plan creation, progress reporting, and completion criteria.

Quick Start

Run the plan-management workflow to create, review, and execute a plan for a selected task in your project.

Frequently Asked Questions about plan-manage

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

FAQPage Schema
How do I manage project plan lifecycles across multiple agents?

Project plan lifecycle management coordinates create, review, execute, archive, and abandon workflows across agents using the .claude/.plans repository to reduce manual drift and team misalignment.

What is the best way to track execution status across parallel agents?

Execution tracking across parallel agents is handled through integrated issue-tracking, cross-repo labeling, and automated status updates within the .claude/.plans directory structure.

Can I integrate issue tracking with my existing plan management workflows?

Yes, issue-tracking integration links plans directly to issues, tracks execution progress automatically, and archives completed work using standardized templates and governance rules.

Does plan lifecycle automation support cross-repo labeling and validation?

Plan lifecycle automation supports cross-repo labeling, robust validation, logging, and error handling to ensure plan parsing and status tracking remain accurate across repositories.

When should I abandon a plan instead of archiving it in the workflow?

You should abandon a plan when execution tracking reveals blockers or invalid requirements, while archiving is reserved for plans that meet all completion criteria and validation checks.