runbook-solo

Coordinate solo execution of authority runbooks with item locking and role constraints.

1|Updated Apr 22, 2026

Search Tags:#workflow #planning #coordination #execution #runbook #acceptance #solo

Ready to run

npx skills add https://github.com/terencefan/inority-workspace --skill runbook-solo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: runbook-solo
Source: https://github.com/terencefan/inority-workspace/tree/main/skills/runbook-solo
Command: npx skills add https://github.com/terencefan/inority-workspace --skill runbook-solo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the execution of an authority runbook in solo mode, establishing a single control point, strict item locking, and clear transitions between the execution and acceptance steps.

Core Features & Use Cases

Solo progression with two distinct sub-skills: runbook-executor and runbook-acceptor, maintaining boundaries to prevent cross-over into reconnaissance.
Item locking and state validation to ensure each item is completed before advancing, with alignment to the authority runbook results.
Recon boundaries: Solo mode defers recon until back in the planning state, ensuring stability and traceability.
Identity and signing: Enforces solo role and post-action sign-offs for responsible conclusions.

Quick Start

Initiate solo progression only after the authority runbook has converged and the user explicitly confirms entering solo mode.

Frequently Asked Questions about runbook-solo

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

FAQPage Schema

How do I execute a solo runbook workflow with a single control point?▼

You can run a solo runbook workflow by initiating progression after the authority runbook converges and the user explicitly confirms entering solo mode. The Skill coordinates serial progression using the executor and acceptor sub-skills.

What is solo mode in runbook execution and how does it work?▼

Solo mode is a runbook execution state using a single control point to coordinate serial progression. It enforces explicit role constraints, item-lock rules, and boundaries, limiting actions to execution and acceptance while deferring reconnaissance.

When do I need to use item locking during runbook coordination?▼

You need item locking during runbook coordination to ensure each item is completed before advancing to the next step. State validation aligns with authority runbook results to maintain stability and traceability.

Can I perform reconnaissance while executing an authority runbook in solo mode?▼

No, you cannot perform reconnaissance during solo mode execution. The Skill enforces recon boundaries, deferring all reconnaissance activities until the workflow transitions back to the active planning state.

Does solo runbook execution require user confirmation before starting?▼

Yes, solo runbook execution requires explicit user confirmation before starting. Additionally, the authority runbook must be fully converged, and the system enforces solo role identity and post-action sign-offs for responsible conclusions.

What are the limitations of using a single controller for runbook coordination?▼

Limitations of single-controller runbook coordination include strict boundaries that prevent cross-over into reconnaissance until the planning state becomes active again. It enforces serial progression, restricting execution and acceptance to sequential item completion.