maestro

Coordinates multidisciplinary engineering tasks from intake to completion across specified frameworks and tools.

7|Updated May 6, 2026

Search Tags:#workflow #planning #orchestration #inertia #intake #adonisjs #japa

Ready to run

npx skills add https://github.com/lncitador/adonisjs-maestro --skill maestro-lncitador

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maestro
Source: https://github.com/lncitador/adonisjs-maestro/tree/main/skills/maestro
Command: npx skills add https://github.com/lncitador/adonisjs-maestro --skill maestro-lncitador

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maestro coordinates the orchestration of full-cycle engineering work: classify the request, choose the right domain/framework skills, enforce planning/build/publish gates, and carry the task from intake to done without replacing the specialized skills it coordinates.

Core Features & Use Cases

Classifies incoming requests and selects the appropriate domain/framework skills.
Enforces planning, build, and publish gates, and tracks progress from intake to completion.
Coordinates specialized skills (e.g., AdonisJS, Lucid, Inertia, Japa) to deliver end-to-end work.

Quick Start

Initialize a task with maestro to coordinate intake, planning, and execution across required skills.

Frequently Asked Questions about maestro

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

FAQPage Schema

How do I orchestrate full-cycle engineering tasks across AdonisJS, Lucid, and Inertia?▼

Orchestrate full-cycle engineering tasks by initializing a request to classify work, load domain skills, and enforce planning, build, and publish gates from intake to done across AdonisJS, Lucid, Inertia, and Japa.

What is the best way to coordinate planning and build gates for a multi-framework workflow?▼

The best way to coordinate planning and build gates is to classify incoming requests, select appropriate domain skills, and enforce sequential phases that track progress from intake through completion without replacing specialized skills.

Can I use workflow orchestration to manage intake and publishing without replacing my specialized skills?▼

Yes, workflow orchestration coordinates and classifies requests while enforcing gates, tracking progress from intake to publishing without replacing the specialized AdonisJS, Lucid, Inertia, or Japa skills it manages.

How does request classification work for AdonisJS and Japa engineering workflows?▼

Request classification for AdonisJS and Japa workflows works by evaluating incoming tasks, selecting the appropriate domain or framework skills, and enforcing planning, build, and publish gates to track progress to completion.

Do I need separate skills for AdonisJS, Lucid, and Inertia to handle full-cycle work?▼

You need separate domain skills for AdonisJS, Lucid, and Inertia to handle full-cycle work, as orchestration loads and coordinates these specialized skills to enforce gates and deliver end-to-end tasks.

When should I not use an orchestration layer for my engineering workflow?▼

You should not use an orchestration layer for your engineering workflow if a task does not span multiple stages like intake, planning, build, verify, publish, or done, or if it requires only a single specialized skill.