maestro-mission

Convert approved heavy-mode Maestro specs into decomposed child tasks with verification.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-mission
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-mission
Source: https://github.com/Leonardo-Corte/local-social-smm-agent/tree/main/reference/github-agent-orchestration/maestro/skills/bundled/maestro-mission
Command: npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-mission

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts an approved heavy-mode Maestro spec into a decomposed, executable mission with child tasks, so large work can be planned and shipped safely in manageable PR-sized steps.

Core Features & Use Cases

  • Heavy-to-mission bridge: Builds a mission from a heavy spec (from mode: heavy) and decomposes it into outcome-based child tasks.
  • Plan-mode guardrails: Runs an explicit entry planning workflow using EnterPlanMode/ExitPlanMode to prevent side effects during drafting.
  • Phase-based verification: Attaches validation checkpoints using the maestro-verify protocol so each task ends with the canonical verification step.

Quick Start

Use maestro-mission to create a mission from your heavy spec so the first child task is ready to be claimed for implementation.

Frequently Asked Questions about maestro-mission

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

FAQPage Schema
How do I decompose a heavy specification into executable tasks?

Task decomposition for heavy specs works by converting an approved heavy-mode Maestro specification into a mission with outcome-based child tasks. This bridges large multi-surface work into manageable PR-sized steps for safe implementation.

How do I break down a large spec into PR-sized batches safely?

Breaking down a large spec into PR-sized batches safely requires batching heavy spec phases into outcome-based child tasks using plan-mode guardrails. EnterPlanMode and ExitPlanMode prevent side effects during drafting while ensuring tasks remain verifiable.

Do I need an approved heavy-mode spec to start mission planning?

Yes, mission planning requires an approved heavy-mode Maestro specification as input. The skill applies specifically when a heavy spec spans multiple vertical slices or phases requiring decomposition into verifiable child tasks.

How does phase verification work for decomposed mission tasks?

Phase verification attaches validation checkpoints to each task using the maestro-verify protocol. This enforces a canonical verification step at the end of every decomposed child task before the mission proceeds safely.

Where are decomposed missions and child tasks persisted?

Decomposed missions and child tasks are persisted to .maestro/missions/missions.jsonl and .maestro/tasks/tasks.jsonl respectively. This JSONL storage maintains mission state and task records for ongoing execution tracking.