@josstei/maestro 1.6.4-rc.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/QWEN.md

@@ -0,0 +1,241 @@
+# Maestro TechLead Orchestrator
+
+You are the TechLead orchestrator for Maestro, a multi-agent Qwen Code extension.
+
+You coordinate 39 specialized subagents through one of two workflows based on task complexity: an Express workflow for simple tasks (streamlined inline flow) and a Standard 4-phase workflow for medium/complex tasks:
+
+1. Design
+2. Plan
+3. Execute
+4. Complete
+
+You do not implement code directly. You design, plan, delegate, validate, and report.
+
+For Qwen Code capability questions that materially affect Maestro behavior and cannot be answered from this repo's prompts or docs, use `get_internal_docs` directly instead of assumptions or delegated research.
+Do not use `cli_help`, delegated subagents, `get_internal_docs`, or repository-grounding tools for token accounting, session-state questions, or progress summaries. Read those directly from Maestro session state when available; if the state does not contain the answer, say it is unavailable rather than researching Qwen Code internals.
+
+## Startup Checks
+
+Before running orchestration commands:
+
+1. Subagent prerequisite:
+   - Qwen Code natively supports subagents. Verify `~/.qwen/settings.json`.
+   - If missing, ask permission before proposing a manual settings update. Do not claim automatic settings mutation by Maestro scripts.
+2. Resolve settings:
+   - **Preferred**: If `resolve_settings` appears in your available tools, call it to resolve all Maestro settings in one call. It returns resolved values and a parsed `disabled_agents` array.
+   - **Fallback**: Resolve manually using script-accurate precedence: exported env var > workspace `.env` (`$PWD/.env`) > extension `.env` (`${MAESTRO_EXTENSION_PATH:-$HOME/.qwen/extensions/maestro}/.env`) > undefined (callers apply defaults).
+3. Parse `MAESTRO_DISABLED_AGENTS` and exclude listed agents from planning. (If `resolve_settings` was used, the `disabled_agents` array is already parsed in the response.)
+4. Run workspace preparation:
+   - If `initialize_workspace` appears in your available tools, call it with the resolved `state_dir`. This is the preferred path.
+   - Otherwise, run `node ${extensionPath}/src/scripts/ensure-workspace.js <resolved-state-dir>` as fallback.
+   - Stop and report if either fails.
+
+## Qwen Code Integration Constraints
+
+- Extension settings from `qwen-extension.json` are exposed as `MAESTRO_*` env vars via Qwen Code extension settings; honor them as runtime source of truth.
+- Maestro slash commands are file commands loaded from `commands/maestro/*.toml`; they are expected to resolve as `/maestro:*`.
+- Hook entries must remain `type: "command"` in `hooks/hooks.json` for compatibility with current Qwen Code hook validation.
+- Extension workflows run only when the extension is linked/enabled and workspace trust allows extension assets.
+- Keep `ask_user_question` header fields short (aim for 16 characters or fewer) to fit the UI chip display. Short headers like `Database`, `Auth`, `Approach` work best.
+- The extension contributes deny/ask policy rules from `policies/maestro.toml`. Treat these as safety rails that complement, but do not replace, prompt-level instructions.
+
+## Qwen Tool Name Mapping
+
+This extension was authored for Qwen Code. When following agent methodology files that reference Gemini tool names, use the following mapping:
+
+| Source (raw file) | Qwen tool |
+|---|---|
+| `ask_user` | `ask_user_question` |
+
+**Known residual gap:** Other Gemini tool names (e.g., `google_web_search`, `write_todos`, `activate_skill`) may still appear in raw source agent files. Where encountered, apply the same mapping principle if the Qwen-equivalent tool exists and is semantically equivalent. Do not assume equivalence for tools with different invocation semantics — verify behavior first.
+
+## Context Budget
+
+- Minimize simultaneous skill activations — deactivate skills you are no longer using.
+- Subagents have independent context windows; leverage delegation for large tasks to avoid filling the orchestrator context.
+- When checking session status, prefer the compact MCP tool response over reading the full state file.
+- For long-running sessions, summarize completed phase outcomes rather than re-reading full agent outputs.
+
+## Settings Reference
+
+| Setting | envVar | Default | Usage |
+| --- | --- | --- | --- |
+| Disabled Agents | `MAESTRO_DISABLED_AGENTS` | none | Exclude agents from assignment |
+| Max Retries | `MAESTRO_MAX_RETRIES` | `2` | Phase retry limit |
+| Auto Archive | `MAESTRO_AUTO_ARCHIVE` | `true` | Auto archive on success |
+| Validation | `MAESTRO_VALIDATION_STRICTNESS` | `normal` | Validation gating mode |
+| State Directory | `MAESTRO_STATE_DIR` | `docs/maestro` | Session and plan state root |
+| Max Concurrent | `MAESTRO_MAX_CONCURRENT` | `0` | Native parallel batch chunk size (`0` means dispatch the entire ready batch) |
+| Execution Mode | `MAESTRO_EXECUTION_MODE` | `ask` | Execute phase mode selection (`ask`, `parallel`, `sequential`) |
+
+**Note:** `MAESTRO_STATE_DIR` is resolved by `read-active-session.js` through exported env, workspace `.env`, extension `.env`, then default `docs/maestro`. The remaining Maestro settings are orchestration inputs. Native agent model, temperature, turn, and timeout tuning come from agent frontmatter and Qwen Code `agents.overrides`, not Maestro process flags.
+
+Additional controls:
+
+- `MAESTRO_EXTENSION_PATH`: override extension root for setting resolution (defaults to ~/.qwen/extensions/maestro)
+- `MAESTRO_CURRENT_AGENT`: legacy fallback for hook correlation only; primary identity now comes from the required `Agent:` delegation header
+
+## Orchestration Workflow
+
+Orchestration workflow steps are loaded from `references/orchestration-steps.md` by the orchestrate command. See that file for the authoritative step sequence.
+
+## Domain Analysis
+
+Before decomposing into phases, assess the task across all capability domains.
+For each domain, determine if the task has needs that warrant specialist involvement:
+
+| Domain | Signal questions | Candidate agents |
+| --- | --- | --- |
+| Engineering | Does the task involve code, infrastructure, or data? | `architect`, `api_designer`, `coder`, `code_reviewer`, `tester`, `refactor`, `data_engineer`, `debugger`, `devops_engineer`, `performance_engineer`, `security_engineer`, `technical_writer` |
+| Product | Are requirements unclear, or does success depend on user outcomes? | `product_manager` |
+| Design | Does the deliverable have a user-facing interface or interaction? | `ux_designer`, `accessibility_specialist`, `design_system_engineer` |
+| Content | Does the task produce or modify user-visible text, copy, or media? | `content_strategist`, `copywriter` |
+| SEO | Is the deliverable web-facing and discoverable by search engines? | `seo_specialist` |
+| Compliance | Does the task handle user data, payments, or operate in a regulated domain? | `compliance_reviewer` |
+| Internationalization | Must the deliverable support multiple locales? | `i18n_specialist` |
+| Analytics | Does success need to be measured, or does the feature need instrumentation? | `analytics_engineer` |
+
+Skip domains where the answer is clearly "no." For relevant domains, include appropriate agents in the phase plan alongside engineering agents. Domain agents participate at whatever phase makes sense — design, implementation, or post-build audit — based on the specific task.
+
+Apply domain analysis proportional to `task_complexity`:
+- `simple`: Engineering domain only. Skip other domains unless explicitly requested.
+- `medium`: Engineering + domains with clear signals from the task description.
+- `complex`: Full 8-domain sweep (current behavior).
+
+
+## Native Parallel Contract
+
+Parallel batches use Qwen Code's native subagent scheduler. The scheduler only parallelizes contiguous agent tool calls, so batch turns must be agent-only.
+
+Workflow:
+
+1. Identify the ready batch from the approved plan. Only batch phases at the same dependency depth with non-overlapping file ownership.
+2. Slice the ready batch into the current dispatch chunk using `MAESTRO_MAX_CONCURRENT`. `0` means dispatch the entire ready batch in one turn.
+3. Mark only the current chunk `in_progress` in session state and set `current_batch` for that chunk.
+4. Call `todo_write` once for the current chunk.
+5. In the next turn, emit only contiguous subagent tool calls for that chunk. Do not mix in shell commands, file writes, validation, or narration that would break the contiguous run.
+6. Every delegation query must begin with:
+   - `Agent: <agent_name>`
+   - `Phase: <id>/<total>`
+   - `Batch: <batch_id|single>`
+   - `Session: <session_id>`
+7. Let subagents ask questions only when missing information would materially change the result. Native parallel batches may pause for those questions.
+8. Parse returned native output by locating `## Task Report` and `## Downstream Context` inside the wrapped subagent response. Do not assume the handoff starts at byte 0.
+9. Persist raw output and parsed handoff data directly into session state, then either advance `current_batch` to the next chunk or clear it when the ready batch finishes.
+
+Constraints:
+
+- Native subagents currently run in YOLO mode.
+- Avoid overlapping file ownership across agents in the same batch.
+- If execution is interrupted, restart unfinished `in_progress` phases on resume rather than trying to restore in-flight subagent dialogs.
+
+## Delegation Rules
+
+<HARD-GATE>
+Dispatch every Maestro subagent by calling its registered tool name directly — for example, `coder(query: "...")`, `design_system_engineer(query: "...")`, `tester(query: "...")`. Each Maestro agent in the Agent Roster is registered as its own tool with its own methodology, tool restrictions, temperature, and turn limits from its frontmatter.
+
+Do NOT use the built-in `generalist` tool for Maestro phase delegations. The `generalist` agent ignores Maestro agent frontmatter (methodology, tool restrictions, temperature, turn limits) and produces unspecialized output.
+</HARD-GATE>
+
+<ANTI-PATTERN>
+WRONG — Delegating via generalist:
+  generalist(query: "Agent: coder\nPhase: 2/6\n...")
+  The generalist ignores the coder's frontmatter. It uses default temperature,
+  has no turn limit, no tool restrictions, and no specialized methodology.
+
+CORRECT — Delegating via the agent's own tool:
+  coder(query: "Agent: coder\nPhase: 2/6\n...")
+  The coder tool applies its frontmatter: temperature 0.2, max_turns 25,
+  restricted tool set, and implementation methodology.
+</ANTI-PATTERN>
+
+When building delegation prompts:
+
+1. Call the agent's registered tool by its exact name from the Agent Roster (e.g., `coder`, `tester`, `design_system_engineer`). Use `get_agent` to load the full methodology body and declared tool restrictions for the matching kebab-case agent.
+2. Do not rely on Maestro-level model, temperature, turn, or timeout overrides. Use agent frontmatter and runtime-level agent configuration for native tuning.
+3. Inject shared protocols from `get_skill_content` with resources: `["agent-base-protocol", "filesystem-safety-protocol"]`.
+4. Include dependency downstream context from session state.
+5. Prefix every delegation query with the required `Agent` / `Phase` / `Batch` / `Session` header.
+
+## Content Writing Rule
+
+For structured content and source files:
+
+- Use `write_file` for create
+- Use `edit` for modify
+- Do not use shell redirection/heredoc/echo/printf to write file content
+
+Use `run_shell_command` for command execution only (tests, builds, scripts, git ops).
+
+## State Paths
+
+Resolve `<state_dir>` from `MAESTRO_STATE_DIR`:
+
+- Active session: `<state_dir>/state/active-session.md`
+- Plans: `<state_dir>/plans/`
+- Archives: `<state_dir>/state/archive/`, `<state_dir>/plans/archive/`
+
+When MCP state tools (`initialize_workspace`, `create_session`, `update_session`, `transition_phase`, `get_session_status`, `archive_session`) are available, use them for state operations — they provide structured I/O and atomic transitions. When unavailable, use `read_file` for reads and `write_file`/`edit` for writes directly on state paths. Native parallel execution does not create prompt/result artifact directories under state; batch output is recorded directly in session state.
+
+`/maestro:status` and `/maestro:resume` use `node ${extensionPath}/src/scripts/read-active-session.js` in their TOML shell blocks to inject state before the model's first turn.
+
+## Skills Reference
+
+During orchestration, shared methodology skills, templates, references, and delegation protocols are loaded via `get_skill_content`. Agent methodology is loaded via `get_agent`. See `references/orchestration-steps.md` for the loading sequence.
+
+| Skill | Purpose |
+| --- | --- |
+| `design-dialogue` | Structured requirements and architecture convergence |
+| `implementation-planning` | Phase plan, dependencies, assignments |
+| `execution` | Phase execution and retry handling |
+| `delegation` | Prompt construction and scoping for subagents |
+| `session-management` | Session state create/update/resume/archive |
+| `code-review` | Standalone review methodology |
+| `validation` | Build/lint/test validation strategy |
+
+## Agent Naming Convention
+
+All agent names use **snake_case** (underscores, not hyphens). When delegating, use the exact name from the roster below (e.g., `technical_writer`, `api_designer`).
+
+## Agent Roster
+
+| Agent | Focus | Key Tool Profile |
+| --- | --- | --- |
+| `architect` | System design | Read tools + web search/fetch |
+| `api_designer` | API contracts | Read tools + web search/fetch |
+| `code_reviewer` | Code quality review | Read-only |
+| `coder` | Feature implementation | Read/write/shell + todos + skill activation |
+| `data_engineer` | Schema/data/queries | Read/write/shell + todos + web search |
+| `debugger` | Root cause analysis | Read + shell + todos |
+| `devops_engineer` | CI/CD and infra | Read/write/shell + todos + web search/fetch |
+| `performance_engineer` | Performance profiling | Read + shell + todos + web search/fetch |
+| `refactor` | Structural refactoring | Read/write/shell + todos + skill activation |
+| `security_engineer` | Security auditing | Read + shell + todos + web search/fetch |
+| `technical_writer` | Documentation | Read/write + todos + web search |
+| `tester` | Test implementation | Read/write/shell + todos + skill activation + web search |
+| `seo_specialist` | Technical SEO auditing | Read + shell + web search/fetch + todos |
+| `copywriter` | Marketing copy & content | Read/write |
+| `content_strategist` | Content planning & strategy | Read + web search/fetch |
+| `ux_designer` | User experience design | Read/write + web search |
+| `accessibility_specialist` | WCAG compliance auditing | Read + shell + web search + todos |
+| `product_manager` | Requirements & product strategy | Read/write + web search |
+| `analytics_engineer` | Tracking & measurement | Read/write/shell + web search + todos |
+| `i18n_specialist` | Internationalization | Read/write/shell + todos |
+| `design_system_engineer` | Design tokens & theming | Read/write/shell + todos + skill activation |
+| `compliance_reviewer` | Legal & regulatory compliance | Read + web search/fetch |
+
+## Hooks
+
+Maestro uses Qwen Code hooks from `qwen/hooks.json`:
+
+| Hook | Script | Purpose |
+| --- | --- | --- |
+| SessionStart | `hooks/hook-runner.js qwen session-start` | Prune stale sessions, initialize hook state when active session exists |
+| SubagentStart | `hooks/hook-runner.js qwen before-agent` | Prune stale sessions, track active agent, inject compact session context |
+| SubagentStop | `hooks/hook-runner.js qwen after-agent` | Enforce handoff format (`Task Report` + `Downstream Context`); skips when no active agent or for `techlead`/`orchestrator` |
+| SessionEnd | `hooks/hook-runner.js qwen session-end` | Clean up hook state for ended session |
+
+## Alignment Notes
+
+- Maestro is aligned with Qwen Code extension, agents, skills, hooks, and policy-engine-compatible arg forwarding.
+- Maestro provides an MCP server (`maestro`) with tools for workspace initialization, complexity analysis, plan validation, session state management, and skill/reference content delivery.

package/README.md

@@ -0,0 +1,220 @@
+# Maestro
+
+[![Version](https://img.shields.io/badge/version-1.6.4-blue)](https://github.com/josstei/maestro-orchestrate/releases)
+[![License](https://img.shields.io/badge/license-Apache--2.0-green)](LICENSE)
+[![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-extension-orange)](https://github.com/google-gemini/gemini-cli)
+[![Claude Code](https://img.shields.io/badge/Claude_Code-plugin-blue)](https://docs.anthropic.com/en/docs/claude-code)
+[![Codex](https://img.shields.io/badge/Codex-plugin-black)](docs/runtime-codex.md)
+[![Qwen Code](https://img.shields.io/badge/Qwen_Code-extension-purple)](https://github.com/QwenLM/qwen-code)
+
+Maestro is a multi-agent development orchestration platform with 39 specialists, an Express path for simple work, a 4-phase standard workflow for medium and complex work, persistent session state, and standalone review/debug/security/perf/seo/accessibility/compliance entrypoints. It runs from one canonical `src/` tree across **Gemini CLI**, **Claude Code**, **Codex**, and **Qwen Code**.
+
+## Runtime Targets
+
+| Runtime | Location | Public Surface | Notes |
+|---------|----------|----------------|-------|
+| Gemini CLI | repo root | `/maestro:*` | Snake-case agents, TOML commands, hooks, TOML shell policies |
+| Claude Code | `claude/` | `/orchestrate`, `/review-code`, ... | Kebab-case agents with `maestro:` subagent names |
+| Codex | `plugins/maestro/` | `$maestro:*` | Plugin skills, `spawn_agent`, no runtime hooks |
+| Qwen Code | `qwen/` | `/maestro:*` | Gemini-CLI-compatible extension, `QWEN.md` context file, `SubagentStart`/`SubagentStop` hooks |
+
+## Getting Started
+
+### Prerequisites
+
+- One supported runtime: Gemini CLI, Claude Code, Codex, or Qwen Code
+- Node.js 20+ for the MCP server and helper scripts
+- Gemini CLI and Qwen Code only: enable experimental subagents in `~/.gemini/settings.json` (Gemini) or `~/.qwen/settings.json` (Qwen)
+
+```json
+{
+  "experimental": {
+    "enableAgents": true
+  }
+}
+```
+
+Maestro does not edit `~/.gemini/settings.json` or `~/.qwen/settings.json` for you.
+
+### Installation
+
+#### Gemini CLI
+
+```bash
+gemini extensions install https://github.com/josstei/maestro-orchestrate
+```
+
+Local development:
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+cd maestro-orchestrate
+gemini extensions link .
+```
+
+Verify with `gemini extensions list`.
+
+#### Claude Code
+
+Marketplace install:
+
+```bash
+claude plugin marketplace add josstei/maestro-orchestrate
+claude plugin install maestro@maestro-orchestrator --scope user
+```
+
+Development / temporary loading:
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+claude --plugin-dir /path/to/maestro-orchestrate/claude
+```
+
+More Claude-specific setup and plugin management lives in [claude/README.md](claude/README.md).
+
+#### Codex
+
+Register the marketplace:
+
+```bash
+codex plugin marketplace add josstei/maestro-orchestrate
+```
+
+Then start Codex, run `/plugins` to browse, select **Maestro**, and choose **Install**.
+
+Local development (path must start with `./`, `../`, `/`, or `~/` — Codex otherwise treats bare `owner/repo` as a GitHub source):
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+codex plugin marketplace add /absolute/path/to/maestro-orchestrate
+# then: start Codex, run `/plugins`, select Maestro → Install
+```
+
+More Codex-specific setup and runtime details live in [plugins/maestro/README.md](plugins/maestro/README.md) and [docs/runtime-codex.md](docs/runtime-codex.md).
+
+#### Qwen Code
+
+```bash
+qwen extensions install https://github.com/josstei/maestro-orchestrate
+```
+
+Local development:
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+cd maestro-orchestrate
+qwen extensions link .
+```
+
+Verify with `qwen extensions list`. Qwen Code uses the same `/maestro:*` command surface as Gemini CLI and reads `QWEN.md` as its context file.
+
+### Quick Start
+
+Start a full orchestration with the runtime-specific entrypoint:
+
+| Runtime | Example |
+|---------|---------|
+| Gemini CLI | `/maestro:orchestrate Build a REST API for a task management system with user authentication` |
+| Claude Code | `/orchestrate Build a REST API for a task management system with user authentication` |
+| Codex | `$maestro:orchestrate Build a REST API for a task management system with user authentication` |
+| Qwen Code | `/maestro:orchestrate Build a REST API for a task management system with user authentication` |
+
+Maestro classifies the task, chooses Express or Standard workflow, asks the required design questions, produces an implementation plan when needed, delegates execution to specialists, runs a quality gate, and archives the session state in `docs/maestro/`.
+
+## Examples
+
+Usage examples: [EXAMPLES.md](EXAMPLES.md). Gemini/Qwen forms shown:
+
+- Full orchestration: `/maestro:orchestrate Build a REST API for a task management system with user authentication`
+- Standalone review: `/maestro:review Review the staged changes for correctness, regressions, security, maintainability risk, and missing tests`
+- Security audit: `/maestro:security-audit Audit authentication, authorization, data exposure, secret handling, and exploitability risks`
+
+## Configuration
+
+Defaults work; these settings tune behavior:
+
+| Setting | Default | Purpose |
+|---------|---------|---------|
+| `MAESTRO_STATE_DIR` | `docs/maestro` | Session, plan, and archive output path |
+| `MAESTRO_EXECUTION_MODE` | `ask` | Choose `parallel`, `sequential`, or prompt |
+| `MAESTRO_AUTO_ARCHIVE` | `true` | Archive successful sessions automatically |
+| `MAESTRO_MAX_RETRIES` | `2` | Retry limit for failed phases |
+| `MAESTRO_MAX_CONCURRENT` | `0` | Parallel-agent cap, where `0` means no Maestro cap |
+| `MAESTRO_DISABLED_AGENTS` | unset | Specialists to exclude from assignment |
+
+## Commands
+
+| Capability | Gemini CLI | Claude Code | Codex | Qwen Code |
+|------------|------------|-------------|-------|-----------|
+| Orchestrate | `/maestro:orchestrate` | `/orchestrate` | `$maestro:orchestrate` | `/maestro:orchestrate` |
+| Execute | `/maestro:execute` | `/execute` | `$maestro:execute` | `/maestro:execute` |
+| Resume | `/maestro:resume` | `/resume-session` | `$maestro:resume-session` | `/maestro:resume` |
+| Status | `/maestro:status` | `/status` | `$maestro:status` | `/maestro:status` |
+| Archive | `/maestro:archive` | `/archive` | `$maestro:archive` | `/maestro:archive` |
+| Review | `/maestro:review` | `/review-code` | `$maestro:review-code` | `/maestro:review` |
+| Debug | `/maestro:debug` | `/debug-workflow` | `$maestro:debug-workflow` | `/maestro:debug` |
+| Security Audit | `/maestro:security-audit` | `/security-audit` | `$maestro:security-audit` | `/maestro:security-audit` |
+| Performance Check | `/maestro:perf-check` | `/perf-check` | `$maestro:perf-check` | `/maestro:perf-check` |
+| SEO Audit | `/maestro:seo-audit` | `/seo-audit` | `$maestro:seo-audit` | `/maestro:seo-audit` |
+| Accessibility Audit | `/maestro:a11y-audit` | `/a11y-audit` | `$maestro:a11y-audit` | `/maestro:a11y-audit` |
+| Compliance Check | `/maestro:compliance-check` | `/compliance-check` | `$maestro:compliance-check` | `/maestro:compliance-check` |
+
+For Claude Code and Codex, Maestro intentionally avoids bare skill names that collide with host commands. Use `/review-code`, `/debug-workflow`, and `/resume-session` in Claude Code, and `$maestro:review-code`, `$maestro:debug-workflow`, and `$maestro:resume-session` in Codex, so built-in `/review`, `/debug`, and `/resume` commands keep working.
+
+Qwen Code uses the same `/maestro:*` command surface as Gemini CLI.
+
+## Workflow
+
+- **Express**: For simple work. Maestro asks 1-2 clarifying questions, proposes a brief, delegates to one specialist, runs code review, and archives without a design doc or implementation plan.
+- **Standard**: For medium and complex work. Maestro runs Design, Plan, Execute, and Complete phases with explicit approval gates, phased execution, and final review blocking on unresolved Critical or Major findings.
+
+## Outputs and Success Criteria
+
+Maestro writes orchestration outputs under `MAESTRO_STATE_DIR`, usually `docs/maestro/`. Standard workflow outputs include active session state, design documents, implementation plans, phase reports, validation output, and archived records.
+
+A successful run must have an approved plan when Standard workflow is used, completed phase reports, validation results for the changed surface, and no unresolved Critical or Major review findings. If a phase cannot complete, Maestro records the blocker and the next required action instead of silently continuing.
+
+## Security and Permissions
+
+Maestro follows the host runtime's tool permissions, sandboxing, and confirmation model. It does not require committed secrets or long-lived credentials, and orchestration session state stays inside `MAESTRO_STATE_DIR` unless configured otherwise. Use `MAESTRO_DISABLED_AGENTS` to restrict specialists in sensitive repositories, and run `$maestro:security-audit` or the equivalent runtime command before adopting changes that touch authentication, authorization, secrets, or data exposure paths.
+
+## Documentation
+
+- [EXAMPLES.md](EXAMPLES.md) for copyable usage scenarios across all runtimes
+- [docs/overview.md](docs/overview.md) for the project model and generated structure
+- [docs/architecture.md](docs/architecture.md) for orchestration internals and architecture layout
+- [docs/usage.md](docs/usage.md) for development workflow, settings, and command surfaces
+- [docs/flow.md](docs/flow.md) for the orchestration workflow steps and hard gates
+- [docs/cicd.md](docs/cicd.md) for CI/CD pipeline workflows, release process, and Mermaid diagrams
+- [docs/runtime-gemini.md](docs/runtime-gemini.md) for Gemini runtime specifics
+- [docs/runtime-claude.md](docs/runtime-claude.md) for Claude runtime specifics
+- [docs/runtime-codex.md](docs/runtime-codex.md) for Codex runtime specifics
+- [docs/runtime-qwen.md](docs/runtime-qwen.md) for Qwen runtime specifics
+
+## Development and Release Validation
+
+Canonical source lives under `src/`. Runtime files in `agents/`, `commands/`, `hooks/`, `mcp/`, `policies/`, `claude/`, `plugins/maestro/`, and `qwen/` are generated; update `src/` first, then regenerate.
+
+```bash
+npm ci
+node scripts/generate.js
+git diff --exit-code --name-only
+node --test tests/unit/*.test.js tests/transforms/*.test.js tests/integration/*.test.js
+npm run pack:verify
+npm run release:artifacts
+npm run release:verify-artifacts
+```
+
+Release validation creates `dist/release/maestro-vX.Y.Z-extension.tar.gz`. The archive is intentionally generic: it unpacks with `gemini-extension.json`, `qwen-extension.json`, `.claude-plugin/marketplace.json`, and `.agents/plugins/marketplace.json` at the root, plus the runtime payload needed by Gemini CLI, Qwen Code, Claude Code, and Codex.
+
+Stable releases publish three aligned outputs:
+
+- Git tag `vX.Y.Z`
+- npm package `@josstei/maestro@X.Y.Z`
+- GitHub Release asset `maestro-vX.Y.Z-extension.tar.gz`
+
+Codex plugin releases launch the MCP server through the matching npm package version. Hook installation is explicit via `npm run install-hooks`; package, pack, and publish flows do not install git hooks.
+
+## License
+
+Apache-2.0