orchestration-workflow
A weather card built from a command, an agent with a preloaded skill, and a second skill: each part has one job.
- Kind
- Workflow
- Works with
- Claude Code
- Source
- shanraisshan/claude-code-best-practice @ 6d0844baf620
- Path
- orchestration-workflow/orchestration-workflow.md
- License
- MIT
- Jobs
- Automation
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Orchestration Workflow This document describes the **Command → Agent (with skill) → Skill** orchestration workflow, demonstrated through a weather data fetching and SVG rendering system. <table width="100%"> <tr> <td><a href="../">← Back to Claude Code Best Practice</a></td> <td align="right"><img src="../!/claude-jumping.svg" alt="Claude" width="60" /></td> </tr> </table> ## System Overview The weather system demonstrates two distinct skill patterns within a single orchestration workflow: - **Agent Skills** (preloaded): `weather-fetcher` is injected into the `weather-agent` at startup as domain knowledge - **Skills** (independent): `weather-svg-creator` is invoked directly by the command via the Skill tool This showcases the **Command → Agent → Skill** architecture pattern, where: - A command orchestrates the workflow and handles user interaction - An agent fetches data using its preloaded skill - A skill creates the visual output independently ## Component Summary | Component | Role | Example | |-----------|------|---------| | **Command** | Entry point, user interaction | [`/weather-orchestrator`](../.claude/commands/weather-orchestrator.md) | …