Task Coordination

Coordinate related tasks, assign responsibilities, manage dependencies, and verify the combined result, using whatever people, agents, and tools your workspace has. The package installs one workflow recipe, Managed Delivery.

• Package ID: orchestration (the display name is Task Coordination)
• Depends on: Development, Observations and Handoffs, Planning
• Startup visibility: This package adds no entries to startup indexes. Its required Planning, Observations and Handoffs, and Workflow Support packages add their own entries. The coordination recipe opens when a task selects it.

These counts describe this package's own entries when their parent routes expose them in Entries and are read. Required packages add their own entries. Linked files stay on demand unless selected or required.

Install

From your installed Open Forge workspace, preview the package and its required packages:

open-forge extension install orchestration --dry-run

Review the plan. Then apply it:

open-forge extension install orchestration

The CLI installs required packages from the same catalogue. See the Extension guide for scripts using --automatic, updates, removal, or a local source.

Why it exists

Coordinating several related tasks, or several agents at once, is a different need from delivering one change. That's why it's a separate choice and not part of the Development Toolkit.

It addresses problems that appear when tasks run together: unclear responsibility, parallel changes that conflict, and interrupted work that nobody can resume.

What it installs

.agents/skills/use-workflow/references/orchestration/
  _orchestration.md      <- recipe scope entrypoint
  managed-delivery.md    <- the coordination workflow

Its dependencies install the rest. Planning and Development supply the methods it calls, and Planning also supplies the Work Records Pattern. Observations and Handoffs supplies the Observation and Handoff records and their starters. Workflow Support installs once, through those dependencies.

What each file is for

managed-delivery.md

Kind: workflow recipe. Used when: dependencies or several contributors make coordination worth it. Independent small work can use Development directly.

Goal: deliver related tasks with clear responsibilities, resumable state, and verified integration, within your authority.

Step	What the recipe asks for
1. Establish the delivery boundary	Outcome, baseline, constraints, who decides, the delivery target, and any integration or publication you're withholding.
2. Plan the dependency graph	Uses the Planning recipe, and the Work Records Pattern where no suitable structure exists.
3. Assign clear responsibility	Coordination owns shared decisions, dependencies, and integration. Each task owns one bounded outcome. One person or agent may hold every role.
4. Prepare executable assignments	Each task gets its outcome, sources, allowed and protected paths, dependencies, and completion evidence.
5. Choose safe concurrency	Parallel work only when dependencies, authority, and isolation (such as separate worktrees) allow it. Otherwise sequential.
6. Execute with local continuity	Uses the Development recipe within each task.
7. Preserve and resume deliberately	Keeps interrupted work recoverable. Seals a Handoff only for a real transfer or planned resumption.
8. Review integration candidates	Uses the Review recipe when required or when fresh scrutiny adds value. Commits only when authorized.
9. Integrate and verify	When authorized, in dependency order, with checks that expose interactions between tasks.
10. Report the real delivery state	Updates the defining sources, and names any unfinished integration or acceptance boundary.

It completes when responsibilities and state are clear, unfinished work is recoverable, completed changes have evidence, and records agree with what was delivered.

How to use it

Use Managed Delivery for these related tasks. Keep responsibilities clear, work sequentially unless concurrency is justified, and verify the combined result.

Good to know

• The package installs no model roster, hierarchy, scheduler, or tool permissions.
• Installation grants no permission to commit, integrate, publish, or contact external systems. Task completion never grants permission to merge, push, or publish.
• If you only want Observation and Handoff records, install Observations and Handoffs alone.
• Task Coordination doesn't install Project Documents or Flows and Scenarios, and isn't part of the Development Toolkit.

Next: Install this package, or update and remove Extensions.