Menu
Orchestrate multi-step, multi-agent workflows with HITL gates.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guide users through adding a new connector action to a Copilot Studio agent. Connector actions require UI-based connection setup, so this skill walks users through the Copilot Studio portal steps, then delegates to edit-action for YAML modifications.
Generate and insert an Adaptive Card into a Copilot Studio topic using AdaptiveCardPrompt. Use when the user asks to add an adaptive card, rich card, form card, info card, confirmation card, or interactive card to a topic.
Add generative answer nodes (SearchAndSummarizeContent or AnswerQuestionWithAI) to a Copilot Studio topic. Use this instead of /add-node when the user asks to add grounded answers, knowledge search, generative answers, or AI-powered responses — these nodes require specific patterns (ConditionGroup follow-up, knowledge source references, autoSend, responseCaptureType) that /add-node does not cover.
Add a knowledge source (public website or SharePoint) to a Copilot Studio agent. Use when the user asks to add a knowledge source, documentation URL, website, or SharePoint site for the agent to search.
Add or modify a node in an existing Copilot Studio topic. Use when the user asks to add a question, message, condition, variable, or other node to a topic. Do NOT use this for generative answers or knowledge search — use /add-generative-answers instead.
Add child agents, connected agents, or other multi-agent patterns to a Copilot Studio agent. Use when the user asks to create a sub-agent, child agent, connected agent, or call another agent.
| name | copilot-studio-conductor |
| description | Orchestrate multi-step, multi-agent workflows with HITL gates. |
| argument-hint | <what to create or change> |
Trigger: User request spans multiple agents (e.g., "create a topic and deploy it", "fix the issue and verify it works", "scaffold an agent and configure knowledge").
Decomposes multi-step requests into sequenced tasks that are delegated to specialist agents (Author, Manage, Test, Troubleshoot) with HITL gates between each step.
circe-memory.md (if it exists) — understand current project state..github/circe-conventions.md — load mandatory rules.Match the user's request to a predefined workflow:
| Pattern | Workflow |
|---|---|
| "create X and deploy" / "add X and push" | Create & Deploy |
| "fix X and test" / "debug X and verify" | Fix & Verify |
| "create X, deploy, and test" / "full cycle" | Full Cycle |
| "scaffold agent and configure" / "new agent from scratch" | Scaffold & Configure |
| "create a BC agent" / "collections agent" / "sales agent" / "support agent" | BC Agent Setup — read /copilot-studio:bc-agent-blueprints for the matching blueprint |
| None of the above | Custom Workflow — analyze and propose |
Before executing anything, present the plan with numbered steps, agent assignments, and HITL gates. Wait for user confirmation.
For each step:
If a step fails:
After the final step:
/copilot-studio:update-memory with the workflow resultsWhen delegating to a specialist agent, provide:
Task: [specific action to perform]
Context: [user's original request and intent]
Project state: [from circe-memory.md — schema name, GenerativeActionsEnabled, etc.]
Previous steps: [what was already done in this workflow]
Decisions: [relevant DRs from this session]
── CIRCE EVIDENCE ──────────────────
Skills loaded: copilot-studio-conductor
Workflow executed: [workflow name] ([N] steps)
Agents delegated: [list]
HITL gates passed: [N/total]
Decision Records created: [list or "none"]
Memory updated: Sí/No
────────────────────────────────────