maestro-next

Route development intents to execution channels by task type and complexity.

76|5|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catlog22/pi-maestro-flow --skill maestro-next
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-next
Source: https://github.com/catlog22/pi-maestro-flow/tree/main/.pi/skills/maestro-next
Command: npx skills add https://github.com/catlog22/pi-maestro-flow --skill maestro-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly classify a development request and choose the right execution channel, so you do not waste time sending a task into the wrong workflow.

Core Features & Use Cases

  • Intent routing: Interprets the user's goal and maps it to the most suitable development action, such as analysis, planning, execution, review, testing, or a lightweight companion route.
  • Complexity assessment: Distinguishes between simple one-off changes and multi-step work, then recommends the appropriate path for speed or control.
  • Workflow orchestration: Supports development scenarios that need confirmation, staged execution, or handoff to a broader multi-step process.
  • Use case: A developer asks for a quick code tweak, a full implementation plan, or a multi-step review-and-fix cycle, and this Skill routes each request correctly.

Quick Start

Give the maestro-next skill your development intent and let it classify the request into the right execution channel.

Frequently Asked Questions about maestro-next

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

FAQPage Schema
How do I route development intents to the correct execution channel?

Workflow orchestration supports multi-step development scenarios by recommending paths that need confirmation, staged execution, or handoff to a broader process, ensuring complex tasks receive proper control rather than a single run.

What is the best way to classify a development request for multi-step orchestration?

Complexity assessment distinguishes between simple one-off changes and multi-step work, then recommends the appropriate execution path. This ensures quick code tweaks use lightweight routes while full implementation plans trigger orchestrated workflows.

Can I use intent routing for both lightweight edits and full implementation plans?

Yes, intent routing applies to software engineering workflows involving lightweight edits, single-step runs, and multi-step orchestration. It evaluates your request's lifecycle stage to choose between a quick companion route and a structured multi-step process.

Does this workflow orchestration approach run execution loops itself?

Workflow orchestration supports multi-step development scenarios by recommending paths that need confirmation, staged execution, or handoff to a broader process, ensuring complex tasks receive proper control rather than a single run.