maestro

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.

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.

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.

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.

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.

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.