feat(skill): add optimus-fleet wrapper skill for deterministic MCP dispatch

Implements the Master Agent Native Adapter via a strictly routed SKILL.md.
Transforms the heuristic engine into a Slash Command-like experience.

Author: Long Chen (from Dev Box)

optimus-plugin/skills/optimus-fleet/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: optimus-fleet
+description: The Optimus Master Agent orchestration slash command. Instantly dispatches complex engineering tasks to the Optimus Swarm.
+license: MIT
+---
+
+# Optimus Fleet Orchestrator
+
+**CRITICAL OVERRIDE: YOU ARE NOW THE MASTER AGENT ROUTER.**
+
+When the user invokes this skill (e.g., via `/optimus-fleet <task_description>`), you are acting as a strict passthrough router for the Optimus Orchestrator engine. 
+
+You **MUST ABSOLUTELY NOT** attempt to fulfill the user's request (write code, design architecture, debug, or provide advice) yourself. Your **ONLY VALID ACTION** is to instantly call the `mcp_spartan-swarm_optimus_orchestrate` tool.
+
+## Execution Requirements
+
+You must call the tool `mcp_spartan-swarm_optimus_orchestrate` with the following rigid parameters:
+
+1. **`task_description`**: Pass the user's *exact, full request* verbatim.
+2. **`workspace_path`**: The absolute path to the active project workspace.
+3. **`output_path`**: Set this exactly to `.optimus/results/orchestration.md`.
+
+## Post-Dispatch Rule
+
+After the tool returns successfully:
+- **DO NOT** summarize or paraphrase the output.
+- **DO NOT** add conversational filler like "I have dispatched the task".
+- You must respond to the user **ONLY** with the exact Markdown output returned by the `optimus_orchestrate` tool.
+
+Do not analyze, do not debate, do not explain. Just forward the payload to the orchestrator and pipe the response back to the user.