plan-manage

Orchestrate plan lifecycle flows across local repositories and issue trackers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage implementation plans and track cross-cutting work within the claude ecosystem by organizing planning, execution, and review flows.

Core Features & Use Cases

  • Orchestrates plan lifecycles (list, create, review, execute, archive, abandon) with optional parallel-agent support for complex tasks.
  • Integrates with local plan directories (.claude/.plans) and issue trackers to update status, labels, and progress automatically.
  • Provides templates and logging to preserve audit trails and ensure reproducible planning and execution.

Quick Start

Use plan-manage to create a new plan from a user description or an issue number, then monitor execution progress and finalize the plan.

Frequently Asked Questions about plan-manage

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

FAQPage Schema
How do I orchestrate plan lifecycles across local repositories and issue trackers?

You orchestrate plan lifecycles by managing create, review, execute, archive, and abandon flows. This coordinates cross-team planning tasks across local repositories and issue tracking, handling multi-agent consensus, templates, and execution progress automatically.

What is parallel-agent support for plan execution management?

Parallel-agent support for plan execution management allows multiple agents to work on complex cross-cutting tasks simultaneously. It applies to cross-team planning workflows, ensuring multi-agent consensus during the create, review, and execute phases of the plan lifecycle.

How do I automate issue tracking updates and status labeling during software development workflows?

You automate issue tracking updates by orchestrating plan execution flows that integrate directly with issue trackers. This handles status tracking, file updates, and issue labeling automatically, ensuring audit trails and reproducible planning across local plan directories.

Can I use plan templates for cross-team planning tasks in the claude ecosystem?

Yes, you can use plan templates for cross-team planning tasks within the claude ecosystem. The orchestration provides templates and logging to preserve audit trails, ensuring reproducible planning and execution while satisfying production-grade validation requirements.

Does plan-manage work without external dependencies for workflow orchestration?

Yes, plan-manage works without external dependencies for workflow orchestration. It operates entirely within the claude ecosystem using local plan directories (.claude/.plans) and optional parallel-agent integration, requiring no additional components to manage end-to-end plan lifecycles.

When should I abandon a plan instead of archiving it during workflow orchestration?

You abandon a plan during workflow orchestration when execution is no longer viable, whereas archiving preserves completed plans for audit trails. Both flows handle status tracking and issue labeling, maintaining reproducible planning history across local repositories.