The how-to for the Maestro feature loop — the product contract a cluster of tasks delivers against. A task links to its feature with `maestro task create --feature <id>`; this skill owns the feature's own lifecycle. For the task loop itself see the `maestro-task` skill; for the QA artifacts the ga

Use when the work is design or brainstorming rather than implementation - turning a rough idea into decided design-of-record before any task is built. Covers mapping the problem from the real code, walking open questions one decision at a time, and locking each fork as a Decision record with running reasoning in the feature's notes.md. Reach for it on design, architecture, brainstorm, or spec-authoring requests in a Maestro repo.

Initial setup and harness tuning protocol for a Maestro-enabled repository.

Verification protocol for Maestro tasks and feature work.

Capture a real-scenario behavior contract for a feature before edits start. Run at feature accept; the accept gate blocks until baseline.md exists, and the ship gate proves every behavioral scenario against it.

Replay the affected baseline scenarios after each implementation wave and record proven slices for a feature. The ship gate requires a counting slice (scenarios + evidence) for every behavioral [bl-NNN] in the baseline.