Execute plan.json tasks in parallel waves with CSV-driven state.
npx skills add https://github.com/catlog22/Maestro-Flow --skill maestro-execute
Please help me install this Agent Skill. Skill: maestro-execute Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/maestro-execute Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill maestro-execute
Maestro-execute automates the execution of phased implementation plans by turning plan.json task definitions into a CSV-driven, wave-executed workflow so teams can complete multi-step engineering phases reliably and faster. It eliminates manual coordination of sequential dependencies, hand-off context, and per-task verification by running agents or CLIs in controlled parallel waves with resume and checkpoint support.
Execute maestro-execute for the desired phase with concurrency and auto-commit options to run wave-by-wave parallel task execution and generate the results and context report.
High-intent search queries and answers about installing and using this skill.
Automate parallel task execution by converting plan.json definitions into a CSV-driven workflow, running tasks in pre-computed waves while preserving strict ordering and propagating cross-wave context.
Wave-based execution groups independent tasks into parallel runs within each wave while maintaining strict wave ordering, allowing multiple agents or CLIs to execute concurrently before advancing to the next wave.
CSV state management uses tasks.csv as the canonical master state for task status, findings, and modified files, enabling breakpoint resume by detecting completed tasks and skipping dependent tasks on failure.
Concurrency limits and auto-commit support are configurable execution options that control parallel task runs and automate git commits per task during wave-by-wave execution sessions.
When a task fails, the execution pipeline marks dependent tasks as skipped, applies retry limits, prompts for blocked tasks, and logs failures to an append-only discovery board for auditability.
Yes, plan.json provides the pre-computed wave definitions and task structures that the execution pipeline reads to build tasks.csv, which then serves as the source of truth for state management.
GDSDNOrchestrate software epic execution with wave-based parallel story processing and quality gates.
catlog22Analyze codebases into CSV tasks and decision artifacts via multi-wave agents.
hackefellerPartition independent tasks into dependency waves with validation barriers.
charly3pinsDispatch fresh subagents per task with isolated contexts and post-task code reviews.
