/adapt-workflow
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
$ npx -y skills add sharpdeveye/maestro --skill adapt-workflow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/adapt-workflow
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
SKILL.md
adapt-workflow.SKILL.mdname: adapt-workflow
description: "Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context."
argument-hint: "[target context]"
category: utility
version: 2.0.0
user-invocable: true
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first. Additionally gather: what the workflow is being adapted to.
---
Adapt a working workflow for a different context.
Adaptation Assessment
| Dimension | Current | Target | Impact | |-----------|---------|--------|--------| | Model provider | ? | ? | Prompt format, capabilities, pricing | | Model tier | ? | ? | Context window, reasoning ability | | Deployment env | ? | ? | Latency, availability, compliance | | Team structure | ? | ? | Monitoring, escalation, ownership | | Data sensitivity | ? | ? | Guardrails, logging, access controls |
Provider Adaptation
- **Prompt format**: Adjust for provider-specific features
- **Context limits**: Resize context budget for different window sizes
- **Capability gaps**: Identify features available in one provider but not another
- **Pricing model**: Recalculate cost estimates
- **API differences**: Update tool calling interfaces, error handling, retry logic
Environment Adaptation
- **Latency requirements**: Adjust timeout values, caching strategy
- **Compliance**: Add or adjust guardrails, logging, and data handling
- **Scale**: Adjust concurrency limits, batch sizes
- **Monitoring**: Adapt alerting thresholds
Adaptation Checklist
- [ ] All provider-specific APIs updated
- [ ] Context budget recalculated for target model
- [ ] Cost estimates updated with target pricing
- [ ] Guardrails adjusted for target compliance requirements
- [ ] Tests updated and passing in target environment
- [ ] Documentation updated for target team
Recommended Next Step
After adaptation, run `/evaluate` to verify the workflow performs correctly in the target environment, then `/diagnose` for a full health check.
**NEVER**:
- Assume prompts work identically across providers
- Copy production config to development without adjusting guardrails
- Adapt without updating the evaluation suite
- Skip cost re-estimation
Read more
name: adapt-workflow description: "Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context." argument-hint: "[target context]" category: utility version: 2.0.0 user-invocable: true
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first. Additionally gather: what the workflow is being adapted to.
---
Adapt a working workflow for a different context.
Adaptation Assessment
| Dimension | Current | Target | Impact | |-----------|---------|--------|--------| | Model provider | ? | ? | Prompt format, capabilities, pricing | | Model tier | ? | ? | Context window, reasoning ability | | Deployment env | ? | ? | Latency, availability, compliance | | Team structure | ? | ? | Monitoring, escalation, ownership | | Data sensitivity | ? | ? | Guardrails, logging, access controls |
Provider Adaptation
- **Prompt format**: Adjust for provider-specific features
- **Context limits**: Resize context budget for different window sizes
- **Capability gaps**: Identify features available in one provider but not another
- **Pricing model**: Recalculate cost estimates
- **API differences**: Update tool calling interfaces, error handling, retry logic
Environment Adaptation
- **Latency requirements**: Adjust timeout values, caching strategy
- **Compliance**: Add or adjust guardrails, logging, and data handling
- **Scale**: Adjust concurrency limits, batch sizes
- **Monitoring**: Adapt alerting thresholds
Adaptation Checklist
- [ ] All provider-specific APIs updated
- [ ] Context budget recalculated for target model
- [ ] Cost estimates updated with target pricing
- [ ] Guardrails adjusted for target compliance requirements
- [ ] Tests updated and passing in target environment
- [ ] Documentation updated for target team
Recommended Next Step
After adaptation, run `/evaluate` to verify the workflow performs correctly in the target environment, then `/diagnose` for a full health check.
**NEVER**:
- Assume prompts work identically across providers
- Copy production config to development without adjusting guardrails
- Adapt without updating the evaluation suite
- Skip cost re-estimation
Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and 6 more.
Repo: sharpdeveye/maestro
Other skills on maestro.
- /accelerate
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Open skill - /agent-workflow
Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and guardrails.
Open skill - /amplify
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Open skill - /calibrate
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Open skill - /capture
Capture a session summary — what was done, what decisions were made, and what to do next.
Open skill - /chain
Use when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.
Open skill