Aircall Dev Flow Maestro

The per-ticket dev loop for work that maestro owns: ticket → worktree → implement → debug → gate → MR, with a maestro ownership check before any worktree is created and `maestro adopt` after the MR exists. Use when the ticket is already a maestro task, when a virtuoso may be live on it, or when the work should stay reachable by `maestro resume` later. For a one-off ticket in this session with no maestro involvement, use `aircall-dev-flow` instead.

kentoje Updated 2 repo stars
SCR-20260627-ugeq

File contents

kentoje/dotfiles commit 5ae41c1d33

Frequently asked questions

npx get-skill add kentoje/aircall-dev-flow-maestro