runbook-team

Coordinate team-based runbook execution across reconnaissance, execution, and acceptance lanes.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/terencefan/inority-workspace --skill runbook-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runbook-team
Source: https://github.com/terencefan/inority-workspace/tree/main/skills/runbook-team
Command: npx skills add https://github.com/terencefan/inority-workspace --skill runbook-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a runbook's team-based execution when the authority runbook is ready, ensuring explicit user intent, role-aligned agents, and auditable handoffs to reduce misexecution and boost governance.

Core Features & Use Cases

  • Structured team roles for reconnaissance, execution, and acceptance aligned with runbook stages.
  • Two-step startup protocol that first loads child skills and then applies real scope, ensuring readiness before action.
  • Clear naming, context boundaries, and supervision rules to maintain authority and traceability across the runbook.

Quick Start

Activate the runbook-team skill only after the authority runbook is ready and the user explicitly confirms entering team execution.

Frequently Asked Questions about runbook-team

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

FAQPage Schema
How do I coordinate runbook execution across multiple team roles?

Runbook team execution coordinates collaboration across reconnaissance, execution, and acceptance lanes through explicit role assignments, ensuring structured handoffs and auditable governance throughout the workflow.

What is the two-step startup protocol for runbook team workflows?

The two-step startup protocol first loads child skills to verify readiness, then applies the real execution scope, ensuring all context boundaries and supervision rules are established before spawning agents.

When should I enter team mode for runbook orchestration?

Enter team mode when the authority runbook is ready, ambiguity and risk are low, and you explicitly request supervising the process through control-plane commands to spawn, monitor, and close agents with traceability.

Does runbook team execution require a completed authority runbook first?

Yes, the authority runbook must be fully ready before activation. This prerequisite ensures role-aligned agents operate within clear context boundaries, reducing misexecution and maintaining governance authority.

What's the best way to supervise agents in a runbook collaboration workflow?

Use control-plane commands to spawn, monitor, and close agents with traceability. Clear naming conventions and supervision rules maintain authority and ensure auditable handoffs across reconnaissance, execution, and acceptance stages.

Why does runbook team execution use separate lanes for reconnaissance and acceptance?

Separate lanes align with distinct runbook stages, ensuring reconnaissance gathers information, execution performs actions, and acceptance verifies results, which collectively reduces misexecution and boosts governance.