ReinaMacCredy/maestro

Maestro Bundle routes requests into the right maestro tier and manages the SPEC, NOTES, and VERIFY bundle lifecycle. Use it when work needs a bundle to open, resume, close, or recall across sessions.

Maestro Design settles unknowns before implementation by recalling prior decisions, exploring one fork at a time, and recording each choice with its rationale. Use it when scope, authority, or architecture is still unclear.

Maestro Improve turns filed lessons into the smallest doctrine edit that would have prevented them. Use it to group pending lessons by target, commit one evidence-linked change per target, and process accepted or rejected lessons without deleting history.

Maestro Verify cross-checks coverage, runs VERIFY scenarios, and records a verdict for close, commit, install, push, release, or archive gates. It also captures durable lessons into decisions and avoids claiming remote state from local evidence.

Maestro Work drives one accepted implementation unit with a test-first loop. Use it to keep changes inside the agreed scope, prove the behavior with a falsifying test, and report results with evidence.