integration-orchestrator
Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's tools (Jira, Linear, Notion, Figma, GitHub) with AI agents via MCP and CLI. A temporal map of phases, lock points, handoff specs, gate definitions, and QA verification gates. Distinct from `creative-brief` (static project brief) and `creative-direction` (aesthetic direction). Triggers on integration orchestrator, delivery cadence, project orchestration, when does the brief lock, how to phase creative
Profile →npx skills add rampstackco/claude-skills --skill integration-orchestrator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill generates a phased delivery orchestration plan that defines which skills run when, which artifacts lock at each gate, how handoffs occur, and how cadence is implemented in Jira, Linear, Notion, Figma, and GitHub with AI agents via MCP and CLI. It outputs a temporal map of phases, lock points, handoff specs, gate definitions, and QA verification gates, plus a platform-specific implementation guide and MCP commands for setup. It is designed to be pasted into a calendar and started on Tuesday, with phase boundaries aligning to calendar weeks when possible.
How it works
It requires inputs: Project type, Team composition, Tool stack, Timeline target, Existing constraints, AI agent participation, and Risk profile. It defines seven orchestration considerations: Phasing (which phases run sequentially or overlap), Gates (approval moments with measurable criteria, blockers, and pass criteria), Lock points (when artifacts become immutable and how changes propagate), Handoffs (phase-to-phase transfers with artifacts), Team-size modulation (scaling the cadence and review density), Tool-stack implementation (how phases/gates map to Jira/Linear/Notion/Figma/GitHub and MCPs), and Automation and QA verification (automatic QA gates via Playwright/Chrome/Windows/mobile MCP). It also provides seven common cadences for various project types, with examples of phase durations and gate behavior. The plan specifies actions in each platform (e.g., Epics and custom fields in Jira; Projects and cycles in Linear; database rows in Notion; library folders in Figma; branch protection, PR templates, and CODEOWNERS in GitHub) and notes where MCPs can automate steps and where manual work remains.
When to use
- Starting a new brand build, rebrand, or campaign to sequence work
- Mid-flight projects where the brief is revisited and downstream work is disrupted
- Setting up a team’s agent-driven workflow with MCPs and CLI integration
- Multi-team handoffs that have broken down between brand, design, and engineering
- Establishing QA verification gates so Done is measurable, not self-reported
- Migrating from ad-hoc orchestration to a documented cadence
- Onboarding a new PM or design lead onto an active project lacking sequencing
- Adding platforms/tools and re-mapping cadence
What it can touch
The skill outlines orchestration for tools Jira, Linear, Notion, Figma, GitHub, and uses MCPs (where available) to implement phases, gates, and handoffs. It specifies which MCP operations can be executed and where manual UI work remains, adapting to the capabilities of each platform.
Caveats
Measurable gate criteria and lock behavior are defined within the plan (e.g., specific acceptance criteria for gates). It notes limitations where MCP automation is unavailable (e.g., certain Figma Dev Mode capabilities) and indicates when manual steps are required. It does not itself execute changes in tooling; it prescribes the steps and configurations for the team to implement.
# Integration Orchestrator A brief tells a team what to make. Creative direction tells them what it should feel like. Neither tells them when each decision locks, who reviews what, or what stops the next phase from starting before the prior one is done. That is the gap this skill fills. The output is a phased orchestration plan the PM can paste into a calendar Monday morning and start running Tuesday. Phases, gates, lock points, handoffs, QA verification rules, and a platform-specific implementation guide for whatever stack the team actually uses (Jira, Linear, Notion, Figma, GitHub, agile sprints). --- ## What this skill is A creative-direction project has three layers. The brief layer defines scope, audience, deliverables, constraints, success criteria. The direction layer defines tone, aesthetic, relationship, and sensory ambition. Both produce written artifacts. Neither answers the temporal question: when does the brief lock, when does identity lock, when does copy lock, who reviews each, what gets blocked while a gate is open, what happens when a downstream task discovers the brief is wrong, and what makes "Done" mean tested rather than self-reported. This skill produces that
- What this skill is
- When to use
- When NOT to use
- Required inputs
- The framework: 7 considerations for orchestration
- 1. Phasing
- 2. Gates
- 3. Lock points
- 4. Handoffs
- 5. Team-size modulation
- 6. Tool-stack implementation
- 7. Automation and QA verification
- Common project-type cadences
- Failure patterns
What does the integration-orchestrator skill do?
Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's tools (Jira, Linear, Notion, Figma, GitHub) with AI agents via MCP and CLI. A temporal map of phases, lock points, handoff specs, gate definitions, and QA verification gates. Distinct from `creative-brief` (static project brief) and `creative-direction` (aesthetic direction). Triggers on integration orchestrator, delivery cadence, project orchestration, when does the brief lock, how to phase creative
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill integration-orchestrator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.