maestro-design
openbooklet.com/s/maestro-designopenbooklet.com/s/[email protected]GET /api/v1/skills/maestro-designUse 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.
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
Initial setup and harness tuning protocol for a Maestro-enabled repository.
Task workflow layer for operating Maestro - create, claim, advance, block, and verify tasks, plus the rarer terminal verbs and the on-request harness self-improvement loop. For the feature contract tasks deliver against, see the maestro-feature skill.
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.
Auto-indexed from ReinaMacCredy/maestro
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.