How do I install the Orchestrate skill?

Run npx skillmds@latest add jamie-bitflight/orchestrate-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Orchestrate safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Orchestrate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Orchestrate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Orchestrate?

Jamie-BitFlight (@jamie-bitflight) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Orchestrate by jamie-bitflight — Agent Skill

Name: Orchestrate
Rating: 4.2 (5 reviews)
Author: Jamie-BitFlight

Orchestrate

Use when orchestrating a Python development task via specialized agents. Activates on "build a Python CLI", "add a feature", "write tests", "refactor Python code", "debug Python", "code review", or any multi-agent Python workflow. Invoke as /orchestrate with a task description or alone to use conversation context.

File contents

Task

orchestrate in plugins/python3-development/skills/orchestrate/

If orchestrate is empty, derive the task from the conversation so far. If no task can be derived, ask the user to describe what they want built or changed before proceeding.

Step 1 — Read the orchestration guide (MANDATORY)

Read ../python3-development/references/python-development-orchestration.md.

Do not proceed to Step 2 until this file has been read. It contains agent selection criteria, workflow patterns, quality gates, and multi-agent chaining patterns you will need to fill in Step 2.

Step 2 — Plan the workflow

State aloud before the first Agent tool call:

Task: <one sentence>
Workflow pattern: <TDD | Feature Addition | Refactoring | Debugging | Code Review>
Agent chain: <AGENT1> → <AGENT2> → ...

If you cannot fill in workflow pattern and agent chain from the guide read in Step 1, go back and read it.

Step 3 — Execute

Agent routing — delegate rather than implement:

Python code → subagent_type="python3-development:python-cli-architect"
Tests → subagent_type="python3-development:python-pytest-architect"
Code review → subagent_type="python3-development:code-reviewer"
Architecture design → subagent_type="python3-development:python-cli-design-spec"
Requirements → subagent_type="spec-analyst"
Stdlib-only script → Skill(skill: "python3-development:stdlib-scripting")

Each delegation must include:

Outcomes: what must be true when the agent is done
Constraints: user requirements, compatibility, scope boundaries
Known issues: error messages already in context (pass-through, not pre-gathered)
File paths: where to start looking — not what you found there

Do NOT read source files before delegating. Agents search and read files for themselves — pass file paths, not file contents. Pre-gathering wastes orchestrator context and duplicates work the agent will do anyway.

Done when all agents in the stated chain have returned their outputs.

---name: orchestrate-2description: Use when orchestrating a Python development task via specialized agents. Activates on "build a Python CLI", "add a feature", "write tests", "refactor Python code", "debug Python", "code review", or any multi-agent Python workflow. Invoke as /orchestrate with a task description or alone to use conversation context.---# Taskorchestrate in plugins/python3-development/skills/orchestrate/If `orchestrate` is empty, derive the task from the conversation so far. If no task can be derived, ask the user to describe what they want built or changed before proceeding.## Step 1 — Read the orchestration guide (MANDATORY)Read `../python3-development/references/python-development-orchestration.md`.Do not proceed to Step 2 until this file has been read. It contains agent selection criteria, workflow patterns, quality gates, and multi-agent chaining patterns you will need to fill in Step 2.## Step 2 — Plan the workflowState aloud before the first Agent tool call:```textTask: <one sentence>Workflow pattern: <TDD | Feature Addition | Refactoring | Debugging | Code Review>Agent chain: <AGENT1> → <AGENT2> → ...```If you cannot fill in workflow pattern and agent chain from the guide read in Step 1, go back and read it.## Step 3 — ExecuteAgent routing — delegate rather than implement:- Python code → subagent_type="python3-development:python-cli-architect"- Tests → subagent_type="python3-development:python-pytest-architect"- Code review → subagent_type="python3-development:code-reviewer"- Architecture design → subagent_type="python3-development:python-cli-design-spec"- Requirements → subagent_type="spec-analyst"- Stdlib-only script → Skill(skill: "python3-development:stdlib-scripting")Each delegation must include:- Outcomes: what must be true when the agent is done- Constraints: user requirements, compatibility, scope boundaries- Known issues: error messages already in context (pass-through, not pre-gathered)- File paths: where to start looking — not what you found thereDo NOT read source files before delegating. Agents search and read files for themselves — pass file paths, not file contents. Pre-gathering wastes orchestrator context and duplicates work the agent will do anyway.Done when all agents in the stated chain have returned their outputs.

Frequently asked questions