القائمة
Use when a frontend workflow needs a high-quality LLM brain for orchestration — send a structured prompt, get a structured response, reuse the session across workflow phases
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a grounded idea needs to be grilled into a formal spec — runs a relentless one-decision-at-a-time requirement interview, resolving mechanical questions via workers and putting only real decisions to the user, then dispatches mma-spec. Not for grounding a raw idea (use mma-explore first) or for work where a spec already exists (use mma-plan).
Use when you have an ad-hoc implementation or research task WITHOUT a plan file on disk and you want it to run on a cheap worker instead of consuming main-context tokens
Use when a plan or spec file exists on disk (any markdown with task headings — .mma/plans/*.md, a TODO list, a spec doc) and you need to implement one or more tasks from it sequentially in one worker session
Use when a raw idea or problem needs grounding before it's designed — captures a braindump, fans out divergent internal-codebase investigation + external research + prior-learnings recall in parallel, then synthesises the results into a written exploration.md (Background · Current State · Rough Direction). Not for "where is X" single-answer questions (use mma-investigate).
Claude Code command: /mma-flow — MMA-native design-to-merged-code SDLC playbook that resumes from durable artifacts
Use when you're about to design or attempt something and want to know what THIS project already learned — ask a vague conceptual question (no tags or keywords needed); a read-only worker searches the learnings graph and returns the relevant prior lessons + how they relate. Fire before re-treading ground that may already have been explored. NOT for recording a new learning (mma-journal-record), codebase questions (mma-investigate), or external research (mma-research).
| name | mma-orchestrate |
| description | Use when a frontend workflow needs a high-quality LLM brain for orchestration — send a structured prompt, get a structured response, reuse the session across workflow phases |
| when_to_use | A multi-phase workflow (explore → spec → plan → execute) needs an intelligent orchestrator that maintains session context across phases. Each call sends a self-contained prompt; the agent processes it and returns structured output the calling system parses directly. |
| version | 0.0.0-unreleased |
The orchestrate endpoint provides a session-persistent, high-quality LLM agent for multi-phase workflow orchestration. Unlike worker routes (audit, delegate, review), the orchestrate agent has no reviewer, no worktree, and no findings structure — it takes a prompt and returns the output the caller needs.
Core principle: The frontend owns the workflow state; MMA provides the LLM continuity. Each prompt is self-contained; session reuse provides project context across phases.
Use when:
Don't use when:
mma-delegatemma-reviewmma-auditPOST /task?cwd=<abs-path>
{
"type": "orchestrate",
"prompt": "Synthesize the exploration results into a requirements specification...",
"outputFormat": "json"
}
| Field | Type | Required | Notes |
|---|---|---|---|
type | "orchestrate" | yes | Discriminator |
prompt | string | yes | The full instruction for this workflow phase |
outputFormat | string | no | Hint for desired output format (e.g. "json", "markdown") |
sessionIds | object | no | { implementer: "<session-id>" } — reuse a prior session |
contextBlockIds | string[] | no | IDs from mma-context-blocks (max 2) |
Worker tier defaults to
main(falls back tocomplexifagents.mainis not configured). SendagentTierto override if needed. Review is always skipped — there is no reviewer phase.
To maintain context across workflow phases, capture the session ID from the first response and pass it back:
# Phase 1: Exploration
RESULT=$(curl ... -d '{"type":"orchestrate","prompt":"Explore the codebase for auth patterns..."}' ...)
SESSION_ID=$(echo "$RESULT" | jq -r '.sessions.implementer.sessionId')
# Phase 2: Specification (reuse session)
RESULT=$(curl ... -d '{"type":"orchestrate","prompt":"Based on your exploration, write a spec...","sessionIds":{"implementer":"'"$SESSION_ID"'"}}' ...)
@include _shared/auth.md @include _shared/polling.md @include _shared/response-shape.md