orkestrera

Dispatch subagents across plan cycles and evaluate outcomes with PROGRESS.md gates.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/jgabor/agentera --skill orkestrera
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orkestrera
Source: https://github.com/jgabor/agentera/tree/main/skills/orkestrera
Command: npx skills add https://github.com/jgabor/agentera --skill orkestrera

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orkestrera coordinates plan-driven work by coordinating multiple skills as subagents, ensuring tasks are dispatched, executed, and evaluated in a controlled, loop-driven flow.

Core Features & Use Cases

  • Dispatches subagents to perform tasks across a plan, enabling multi-skill collaboration
  • Enforces plan-driven evaluation with inspektera, PROGRESS.md, and artifact governance
  • Manages multi-cycle execution, retry handling, and context-aware gating to ensure quality
  • Provides gating and health checks to safely chain orchestration across complex workflows

Quick Start

Invoke orkestrera to bootstrap a plan and orchestrate multi-skill execution.

Frequently Asked Questions about orkestrera

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multi-skill automation to execute a complex plan?

Multi-skill automation is coordinated by dispatching subagents across multiple cycles, evaluating outcomes to ensure quality. Orkestrera chains tasks through plan-driven skills while enforcing PROGRESS.md verification and artifact governance.

What is plan-driven orchestration and how does it manage multi-cycle execution?

Plan-driven orchestration dispatches subagents to perform tasks and evaluates outcomes across multiple execution cycles. It chains tasks through designated skills, enforcing strict gates and loop guards to prevent runaway execution while maintaining quality.

How do I prevent runaway execution in automated task dispatch workflows?

Runaway execution is prevented by applying a loop guard and strict gating during task dispatch. The orchestration flow requires staleness checks and PROGRESS.md verification before allowing subsequent cycles to proceed.

Do I need a PROGRESS.md file for plan-driven orchestration to verify task completion?

Yes, a PROGRESS.md file is required for plan-driven orchestration to verify task completion. The orchestration flow enforces strict gating that requires PROGRESS.md verification and staleness checks before evaluating subagent outcomes.

Can I chain multiple skills together to handle complex multi-skill workflows?

Yes, you can chain multiple skills together to handle complex workflows. Orkestrera coordinates multi-skill collaboration by dispatching subagents through inspirera, planera, realisera, inspektera, and other skills across multiple cycles.

What are the limitations of using loop-driven orchestration for task verification?

Loop-driven orchestration limitations include the strict enforcement of gates, requiring PROGRESS.md verification and staleness checks. The loop guard restricts execution cycles, which may halt workflows if verification fails or artifacts become stale.