How do I install the Controlflow Orchestration skill?

Run npx skillmds@latest add gabrielmoreira/controlflow-orchestration 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 Controlflow Orchestration 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 Controlflow Orchestration?

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 Controlflow Orchestration free to use?

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

Who published Controlflow Orchestration?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Controlflow Orchestration by gabrielmoreira

Name: Controlflow Orchestration
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

File contents

ControlFlow Orchestration (Cursor)

Overview

Execute an approved plan with explicit state, disciplined gates, bounded retries, and local evidence. Does not use VS Code agent/runSubagent.

Local Contract

Start from plans/<task-slug>-plan.md; use controlflow-planning if missing.
Confirm strict plan review before non-trivial execution.
Track current phase, last verification, blocker, and next action.

Workflow

Confirm plan path, phase, target files, validation command, approval needs.
Verify review routing: SMALL → plan audit; MEDIUM/LARGE → assumption verifier; LARGE → executability verifier; HIGH risk → assumption verifier.
If review blocks, revise plan before implementation.
Serialize phases unless write ownership is clearly disjoint.
Delegation: For each phase executor_agent, prefer Task to the matching .cursor/agents/controlflow-*.md subagent. Parent must not implement when an implementer subagent is assigned.
Use references/failure-taxonomy.md and references/runtime-policy.json for retry/replan.
Gate destructive actions behind explicit user approval (Cursor AskQuestion when appropriate).
After each phase, run phase checklist; update plan lifecycle sections.
Save artifacts under plans/artifacts/<task-slug>/.

Task Delegation Examples

Phase role	subagent_type
CodeMapper	`controlflow-code-mapper`
Researcher	`controlflow-researcher`
Core implementer	`controlflow-core-implementer`
UI implementer	`controlflow-ui-implementer`
Platform	`controlflow-platform-engineer`
Docs	`controlflow-technical-writer`
Browser test	`controlflow-browser-tester`
Code review gate	`controlflow-code-reviewer`

Fallback: Execute the role instructions in the parent session using the matching skill; record that fallback in the plan ## Decision Log.

Stop-the-Line

Stop when verification fails, assumptions break, security risk appears, or approval is missing. Classify failures per failure taxonomy before retry.

References

references/runtime-policy.json
references/failure-taxonomy.md
references/phase-checklist.md
docs/agent-engineering/CURSOR-SUPPORT.md

---name: controlflow-orchestrationdescription: Use when executing an approved multi-phase plan in Cursor, with gates, approvals, retries, and Task delegation to controlflow subagents.--- # ControlFlow Orchestration (Cursor) ## Overview Execute an approved plan with explicit state, disciplined gates, bounded retries, and local evidence. Does not use VS Code `agent/runSubagent`. ## Local Contract - Start from `plans/<task-slug>-plan.md`; use `controlflow-planning` if missing. - Confirm strict plan review before non-trivial execution. - Track current phase, last verification, blocker, and next action. ## Workflow 1. Confirm plan path, phase, target files, validation command, approval needs. 2. Verify review routing: `SMALL` → plan audit; `MEDIUM`/`LARGE` → assumption verifier; `LARGE` → executability verifier; `HIGH` risk → assumption verifier. 3. If review blocks, revise plan before implementation. 4. Serialize phases unless write ownership is clearly disjoint. 5. **Delegation:** For each phase `executor_agent`, prefer Task to the matching `.cursor/agents/controlflow-*.md` subagent. Parent must not implement when an implementer subagent is assigned. 6. Use `references/failure-taxonomy.md` and `references/runtime-policy.json` for retry/replan. 7. Gate destructive actions behind explicit user approval (Cursor AskQuestion when appropriate). 8. After each phase, run phase checklist; update plan lifecycle sections. 9. Save artifacts under `plans/artifacts/<task-slug>/`. ## Task Delegation Examples | Phase role | subagent_type | | ---------- | ------------- | | CodeMapper | `controlflow-code-mapper` | | Researcher | `controlflow-researcher` | | Core implementer | `controlflow-core-implementer` | | UI implementer | `controlflow-ui-implementer` | | Platform | `controlflow-platform-engineer` | | Docs | `controlflow-technical-writer` | | Browser test | `controlflow-browser-tester` | | Code review gate | `controlflow-code-reviewer` | **Fallback:** Execute the role instructions in the parent session using the matching skill; record that fallback in the plan `## Decision Log`. ## Stop-the-Line Stop when verification fails, assumptions break, security risk appears, or approval is missing. Classify failures per failure taxonomy before retry. ## References - `references/runtime-policy.json` - `references/failure-taxonomy.md` - `references/phase-checklist.md` - `docs/agent-engineering/CURSOR-SUPPORT.md`

Frequently asked questions

Controlflow Orchestration