maestro-plan

Orchestrate parallel codebase explorations into plan.json and TASK-*.json files.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill maestro-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-plan
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/maestro-plan
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill maestro-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maestro-plan automates the labor-intensive process of exploring a codebase from multiple angles and turning those findings into a verified, actionable execution plan so teams don't manually synthesize discoveries, dependencies, and task breakdowns.

Core Features & Use Cases

  • CSV wave pipeline: Two-phase workflow where Wave 1 runs parallel exploration agents and Wave 2 runs a sequential planning agent that emits plan.json and TASK-*.json.
  • Parallel exploration + sequential planning: Uses spawn_agents_on_csv to scale exploration with concurrency controls, then consolidates findings for deterministic plan generation and validation.
  • Plan validation and guardrails: Produces grep-verifiable convergence criteria, read_first requirements, discovery append-only board, gap-mode support, and a revision loop to ensure plan quality.
  • Use Case: Quickly generate a phased execution plan for a development phase by exploring architecture, implementation patterns, integration points, and risks, then producing task definitions for execution.

Quick Start

Invoke maestro-plan for the target phase with appropriate flags (for example: run maestro-plan for phase 3 with --auto and --concurrency 4 to produce plan.json and TASK files).

Frequently Asked Questions about maestro-plan

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

FAQPage Schema
How do I turn parallel codebase explorations into an actionable execution plan?

Multi-agent codebase exploration automates this by running parallel discovery agents across architecture and integration points, then synthesizing findings into a verified execution plan with task definitions and convergence criteria.

What is a CSV-based source-of-truth workflow for software planning?

A CSV-based source-of-truth workflow uses a tasks.csv file to orchestrate multi-agent explorations, enforce append-only discovery boards, manage concurrency controls, and produce deterministic plan.json outputs for phase-based software planning.

How do I generate task definitions from multi-agent codebase discovery?

You generate task definitions by running a two-phase pipeline where parallel exploration agents append discoveries to a board, then a sequential planning agent consolidates findings into TASK-*.json files with grep-verifiable convergence criteria.

Can I control concurrency when spawning parallel exploration agents on a codebase?

Yes, multi-agent orchestration supports concurrency controls through spawn_agents_on_csv, allowing you to scale parallel exploration agents and manage gap-mode handling during the codebase discovery phase.

How does plan validation work for multi-agent codebase exploration?

Plan validation enforces grep-verifiable convergence criteria, read_first requirements, and a revision loop to ensure the sequential planner produces a high-quality, actionable execution plan from parallel agent discoveries.

What's the best way to automate phase-based software planning with multiple agents?

Automated phase-based planning uses a two-wave pipeline where Wave 1 runs parallel exploration agents for discovery and Wave 2 runs a sequential planner to emit plan.json and task files, ensuring verified plan generation without manual synthesis.