skill-orchestrator

Engineering Community

Repo stars 435
Author repo nvim

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Route commands to appropriate workflows based on task type and status. Invoke when executing /task, /research, /plan, /implement…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Context Loading”, “Trigger Conditions”, “Core Responsibilities”, “1. Task Lookup”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-orchestrator directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Context Loading / Trigger Conditions / Core Responsibilities” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Orchestrator Skill

Central routing intelligence for the task management system.

Context Loading

Load context on-demand when needed:

@.opencode/context/orchestration/orchestration-core.md - Routing, delegation, session tracking
@.opencode/context/orchestration/state-management.md - Task lookup and status validation
@.opencode/context/index.json - Full context discovery index

Trigger Conditions

This skill activates when:

A slash command needs task-type-based routing
Task context needs to be gathered before delegation
Multi-step workflows require coordination

Core Responsibilities

1. Task Lookup

Given a task number, retrieve full context:

1. Read specs/state.json
2. Find task by project_number
3. Extract: task_type, status, project_name, description, priority
4. Read TODO.md for additional context if needed

2. Task-Type-Based Routing

Route to appropriate skill based on task type:

Task Type	Research Skill	Implementation Skill
general	skill-researcher	skill-implementer
meta	skill-researcher	skill-implementer
markdown	skill-researcher	skill-implementer

Note: Additional languages (latex, typst) are available via extensions in .opencode/extensions/.

3. Status Validation

Before routing, validate task status is not terminal:

if status in [completed, abandoned, expanded]:
  ABORT "Task is in terminal state [$status]"

All operations (research, plan, implement, revise) are allowed from any non-terminal status.

4. Context Preparation

Prepare context package for delegated skill:

{
  "task_number": 259,
  "task_name": "task_slug",
  "task_type": "general",
  "status": "planned",
  "description": "Full task description",
  "artifacts": {
    "research": ["path/to/research.md"],
    "plan": "path/to/plan.md"
  },
  "focus_prompt": "Optional user-provided focus"
}

Execution Flow

1. Receive command context (task number, operation type)
2. Lookup task in state.json
3. Validate status for operation
4. Determine target skill by task_type
5. Prepare context package
6. Invoke target skill via Task tool
7. Receive and validate result
8. Return result to caller

Return Format

{
  "status": "completed|partial|failed",
  "routed_to": "skill-name",
  "task_number": 259,
  "result": {
    "artifacts": [],
    "summary": "..."
  }
}

Error Handling

Task not found: Return clear error with suggestions
Invalid status: Return error with current status and allowed operations
Skill invocation failure: Return partial result with error details

MUST NOT (Postflight Boundary)

After routing to a skill, this skill MUST NOT:

Edit source files - All work is done by routed skills/agents
Run build/test commands - Verification is done by routed skills/agents
Update task status - Status updates are done by routed skills
Create artifacts - Artifact creation is done by routed skills/agents

The orchestrator is a routing-only skill. It:

Looks up task context
Routes to appropriate skill based on task_type
Passes through the routed skill's return

Reference: @.opencode/context/standards/postflight-tool-restrictions.md

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Engineering
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @benbrastmckie · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-orchestrator.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Orchestrator Skill

Central routing intelligence for the task management system.

## Context Loading

Load context on-demand when needed:
- `@.opencode/context/orchestration/orchestration-core.md` - Routing, delegation, session tracking
- `@.opencode/context/orchestration/state-management.md` - Task lookup and status validation
- `@.opencode/context/index.json` - Full context discovery index

## Trigger Conditions

This skill activates when:
- A slash command needs task-type-based routing
- Task context needs to be gathered before delegation
- Multi-step workflows require coordination

## Core Responsibilities

### 1. Task Lookup

Given a task number, retrieve full context:
```
1. Read specs/state.json
2. Find task by project_number
3. Extract: task_type, status, project_name, description, priority
4. Read TODO.md for additional context if needed
```

### 2. Task-Type-Based Routing

Route to appropriate skill based on task type:

| Task Type | Research Skill | Implementation Skill |
|-----------|---------------|---------------------|
| general | skill-researcher | skill-implementer |
| meta | skill-researcher | skill-implementer |
| markdown | skill-researcher | skill-implementer |

**Note**: Additional languages (latex, typst) are available via extensions in `.opencode/extensions/`.

### 3. Status Validation

Before routing, validate task status is not terminal:

```
if status in [completed, abandoned, expanded]:
  ABORT "Task is in terminal state [$status]"
```

All operations (research, plan, implement, revise) are allowed from any non-terminal status.

### 4. Context Preparation

Prepare context package for delegated skill:
```json
{
  "task_number": 259,
  "task_name": "task_slug",
  "task_type": "general",
  "status": "planned",

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Context Loading → Trigger Conditions → Core Responsibilities → 1. Task Lookup → 2. Task-Type-Based Routing → 3. Status Validation
terms    -> Note · Edit source files · Run build/test commands · Update task status · Create artifacts · routing-only
files/cmd -> @.opencode/context/orchestration/orchestration-core.md · @.opencode/context/orchestration/state-management.md · @.opencode/context/index.json · .opencode/extensions/
body sha256 -> 466df34f0221