maestro-pipeline-test
Maestro Pipeline Smoke Test
This skill exercises all maestro CLI commands in a single end-to-end run. It creates a throwaway feature, walks through every pipeline stage, tests every tool group via CLI, and produces a pass/fail report.
The test is designed to be fast and non-destructive. The smoke-test feature it creates can be cleaned up afterward.
Before You Start
Call maestro ping --json to confirm the maestro CLI is reachable. If it fails, stop and tell the user -- nothing else will work.
Setup: Switch to br backend
The pipeline runs on the br (Beads Rust) task backend by default. Record the current backend, then switch to br:
| Step | Action | Verify |
|---|---|---|
| 0.1 | maestro config-get --key taskBackend --json |
Record original value (may be "fs" or "br") |
| 0.2 | maestro config-set --key taskBackend --value br |
No error |
| 0.3 | maestro ping --json |
taskBackend is "br" AND integrations.br is true |
More from reinamaccredy/maestro
conductor
Implementation execution for context-driven development. Trigger with ci, /conductor-implement, or /conductor-* commands. Use when executing tracks with specs/plans. For design phases, see designing skill. For session handoffs, see handoff skill.
10maestro-revert
Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
9maestro-new-track
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
8init
Generates AGENTS.md and CLAUDE.md files using the WHAT/WHY/HOW framework. Explores the codebase and produces minimal (<100 line) context files with progressive disclosure.
8maestro-setup
Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
7tracking
>
7