rfc-orchestrator

Orchestrate RFC ticket workflows with strict state transitions and GitHub automation.

1|Updated Jan 22, 2026

Search Tags:#automation #workflow #GitHub #RFC #PR #orchestrate

Ready to run

npx skills add https://github.com/guardian-intelligence/apm2 --skill rfc-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rfc-orchestrator
Source: https://github.com/guardian-intelligence/apm2/tree/main/documents/skills/rfc-orchestrator
Command: npx skills add https://github.com/guardian-intelligence/apm2 --skill rfc-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, automated orchestration framework for RFC-based ticket workflows. It coordinates Opus-only agents, enforces strict state transitions, and ensures traceable progress across PRs until all tickets for an RFC are merged.

Core Features & Use Cases

Synchronous review triggering: triggers security and quality reviews only when a ticket requires updates.
Controlled agent dispatch: ensures a fresh subagent is spawned for each ticket to prevent defensive context buildup.
One-ticket-at-a-time workflow: focuses work on a single RFC until its tickets are merged.
Use Case: a large RFC with multiple tickets progresses through discovery, review, implementation, and merge one ticket at a time, with automatic handoffs on context exhaustion.

Quick Start

Use the rfc-orchestrator skill to initiate orchestration for RFC-ORCHESTRATOR with TARGET_RFC set to TCK-XXXXX.

Frequently Asked Questions about rfc-orchestrator

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

FAQPage Schema

How do I orchestrate RFC ticket workflows with GitHub PRs and automated agents?▼

RFC ticket workflows are orchestrated by coordinating Opus-only agents, enforcing strict state transitions, and maintaining a monotone ledger across PRs until all tickets merge. It triggers synchronous reviews and dispatches fresh subagents for each ticket.

What is the best way to automate RFC reviews and implementation handoffs?▼

Automated RFC reviews and handoffs are triggered synchronously when a ticket requires updates, using GitHub automation tools and cargo xtask. Fresh subagents are spawned per ticket to prevent defensive context buildup during implementation.

Do I need Opus-only agents to run synchronous RFC orchestration?▼

Yes, synchronous RFC orchestration requires the Opus-only model. It enforces strict state transitions and coordinates agent subcomponents within a single RFC context at a time, relying on synchronous task execution for traceable progress.

Can I process multiple RFCs at the same time using workflow orchestration?▼

No, RFC orchestration operates within a single RFC context at a time. It focuses work on one-ticket-at-a-time workflows, progressing through discovery, review, implementation, and merge until all tickets for that RFC are merged.

Why does my RFC agent lose context during long ticket workflows?▼

Context exhaustion occurs during long ticket workflows, triggering automatic handoffs. The orchestrator spawns a fresh subagent for each ticket to prevent defensive context buildup and maintains a monotone ledger across PRs for traceability.

How do I start RFC-driven ticket orchestration for a specific target ticket?▼

To start RFC-driven ticket orchestration, initiate the skill with TARGET_RFC set to your specific ticket identifier like TCK-XXXXX. This triggers the synchronous workflow to progress the ticket through review, implementation, and merge.