maestroj
Multi-agent development orchestration platform — 12 specialists, 4-phase orchestration, native parallel subagents, persistent sessions, and
Open source Open in the app JSON README (API)
About
Multi-agent development orchestration platform — 12 specialists, 4-phase orchestration, native parallel subagents, persistent sessions, and standalone review/debug/security/perf commands
Details
- Kind
- Plugins
- Topic
- AI, RAG & memory
- Publisher
- j-steve
- Origin
- gemini
- Category
- ferramentas
- Version
- 1.3.2
- Forks
- 1
- Last push
- 2026-05-05T22:27:26Z
- Repository state
- ativo
- Language
- JavaScript
- License
- MIT
- Added
- 2026-08-30 14:13:39
- Updated
- 2026-08-30 14:13:39
- Origin id
j-steve/maestroj
README
# Maestro JSteve This project is a fork of the [Maestro-Gemini](https://github.com/josstei/maestro-gemini) extension for the Gemini CLI. Please refer to the [upstream root project](https://github.com/josstei/maestro-gemini) for comprehensive documentation, usage instructions, and details on how the Maestro orchestrator works. ## Installation You can install this extension directly into the Gemini CLI using the following command: ```bash gemini extension install https://github.com/j-steve/maestroj ``` ## Differences from Upstream This fork includes several customizations and enhancements tailored for specific workflows: - **New Agents:** Adds `qa_tester` and `deployer` agents to the roster, expanding the orchestrator's capabilities for post-deployment QA and rollout tasks. - **Command Prefixing:** All commands have been renamed from `/maestro` to `/maestroj` (e.g., `/maestroj:design`, `/maestroj:status`) to avoid conflicts with the upstream extension or other tools. - **Strict Execution Mode Gating:** Modifies the execution gating behavior to strictly read the `MAESTRO_EXECUTION_MODE` environment setting. It bypasses the interactive prompt asking the user to choose between parallel and sequential modes, allowing for smoother headless operation. - **Bypass Manual Approvals:** Removes mandatory `yesno` prompts for approving the design document and implementation plan. The orchestrator now provides these as read-only outputs and automatically proceeds to the next phase, while still requiring manual selection for branching design decisions.