riper-orchestrator

riper-orchestrator

Overview

Coordinate RIPER phase execution using role-specific agents and evidence-first handoffs. This skill guides the parent agent through structured delegation to research, planning, execution, and review phases.

Important: The orchestrator is a leaf skill — it cannot call delegate_task itself. It provides phase-by-phase instructions that guide the parent agent to invoke the correct subagent at each step.

When to Use

• Use for non-trivial work that benefits from explicit phase handoffs and checkpoints.
• Use when you need to delegate scoped tasks to subagents with clear role boundaries.
• Always trigger for multi-file edits, physics/application logic changes, or anything that touches shared state.
• Don't use for simple tasks (< 20 lines, single file) — just execute directly.

Trigger phrases (MANDATORY — these are non-negotiable)

When the user says any of the following, you MUST follow the complete RIPER flow with all four agents:

• "full riper" or "riper orchestration"
• "use riper" or "follow riper"
• "use agents" or "use subagents" or "delegate"
• "use the associated skills" or "use all the skills"

These phrases mean the user explicitly wants the full phase flow. Skipping any phase when these are present is a process violation.

Mandatory close process

After review phase completes and before declaring work done, you MUST:

1. Load documentation-maintainer — Update ROADMAP.md, docs/File-Structure-Reference.md, docs/Project-Constraints.md, README.md to reflect implementation changes. These are always-on per AGENTS.md governance rules 4, 5, 7.
2. Load roadmap-updater — Reconcile ROADMAP.md checkpoints with completed work. Add new checkpoints, update status progression, preserve decision context.

This is NOT optional. AGENTS.md governance rule 4 states "Keep ROADMAP.md and relevant docs aligned with actual implementation state" and rule 5 states "Keep docs/File-Structure-Reference.md aligned." These are always-on governance rules, not conditional tasks.