Scooter Lacroix Maestro
- 8 repo stars
- Updated April 19, 2026
- scooter-lacroix/Maestro
Maestro is a Claude Code plugin that structures chat-based coding into spec-driven planning, agent orchestration, review, memory, and live tooling control.
About
Maestro is a Claude Code plugin bundle from scooter-lacroix that reframes conversational coding as a disciplined pipeline: specifications drive what agents do next, code intelligence grounds suggestions in the repo, and orchestration layers coordinate review, memory, and tooling. Developers drowning in fragmented skills and one-off prompts can treat Maestro as a workflow spine—closer to an integrated methodology than a lone integration skill. The catalog metadata emphasizes analysis, automation, spec-driven delivery, testing, and system-level enforcement, which maps well to operators who still want TDD habits and traceable decisions without hiring a platform team. Install when you are actively building with agents and need planning, execution, and review to stay linked rather than when you only need a single linter or deploy hook. Complexity sits at intermediate to advanced because you are adopting a framework, not flipping one feature on.
- Unifies spec-driven planning, code intelligence, and agent orchestration in one structured workflow
- Built-in review, memory, and live tooling control beyond plain chat
- TDD- and track-based workflow with metacognitive / critical-thinking framing in the plugin bundle
- Keywords span automation, enforcement, framework, and unified workflow for Claude Code
- Single-plugin bundle (pluginCount: 1) aimed at productivity across the dev cycle
Scooter Lacroix Maestro by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install scooter-lacroix-maestro@scooter-lacroix/MaestroAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 8 |
|---|---|
| Last updated | April 19, 2026 |
| Repository | scooter-lacroix/Maestro ↗ |
What it does
Who want chat-based coding turned into spec-driven plans, agent orchestration, review, memory, and TDD-friendly enforcement instead of ad-hoc prompts.
Who is it for?
Best when you're shipping agent-heavy products and want spec-driven discipline and orchestration inside Claude Code.
Skip if: Skip if you only need one-off API wrappers or a lightweight skill with no workflow framework.
What you get
You get a repeatable Maestro workflow where plans, agents, review, and tooling stay aligned across sessions.
- Installed Maestro plugin bundle in Claude Code
- Spec-aligned agent sessions with orchestration and memory patterns
- Review and tooling control integrated into daily coding flow
By the numbers
- pluginCount: 1
- repository: scooter-lacroix/Maestro
- catalog stars snapshot: 5
Recommended Plugins
0pg Cc MarketplacePersonal Claude Code plugins collection
1shot Labs Squadron Comms PluginVoice communication system with ElevenLabs TTS for multi-agent coordination in Claude Code3
23blocks Os Ai MaestroAI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging.733
3commas Io Commas ClaudeThis is a repo with shared agents and skills used company-wide4
884js Agent Plugins1 plugin
A5c Ai BabysitterBabysitter enforces obedience to agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration1.6kHow it compares
Full agent workflow platform in one plugin bundle, not a single-task integration skill.
FAQ
Who is Maestro for?
Maestro is for developers using Claude Code who want structured, spec-driven agent workflows instead of unstructured chat coding.
When should I use Maestro?
Use Maestro when you are in active Build work and need planning, orchestration, review, and memory tied together across agent sessions.
How do I add Maestro to my agent?
Register the scooter-lacroix/Maestro Claude Code plugin marketplace entry in Claude Code, install the bundle (1 plugin), then follow the repo workflow for spec-driven and TDD-oriented sessions.