runbook-executor

Execute runbook workflow steps and capture signed evidence records.

1|Updated Apr 22, 2026

Search Tags:#automation #workflow #evidence #execution #runbook #team

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill isolates the execution phase of runbook workflows, enabling reliable, bounded execution of the current item’s #### 执行 and structured evidence capture.

Core Features & Use Cases

Executes the current item’s execution phase in solo main rollout or team execution lane.
Captures execution evidence and writes it to the authority record with proper signing and stop boundaries.
Supports switching between authority-driven and lane-driven modes while maintaining strict scope.

Quick Start

Kick off the execution phase for the current item and begin capturing evidence.

Frequently Asked Questions about runbook-executor

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

FAQPage Schema

How do I automate runbook execution and capture evidence for each step?▼

Runbook execution automation is achieved by systematically running the current item's execution phase, capturing structured evidence, and writing it back to the authority record with signed timestamps and strict stop boundaries.

What is the best way to execute runbook steps in a team workflow lane?▼

Team execution lane mode allows you to execute runbook steps within a bounded context, systematically recording evidence and stopping at defined boundaries while maintaining strict scope between authority-driven and lane-driven modes.

How do I record execution evidence with signed timestamps during workflow automation?▼

Recording execution evidence with signed timestamps is handled automatically by the execution phase, which captures structured evidence templates and writes back execution records to the authority record upon completing the current item's step.

Can I switch between solo main rollout and team execution lane modes during a runbook?▼

Yes, you can switch between solo main rollout and team execution lane modes while maintaining strict scope, ensuring reliable and bounded execution of the runbook workflow's current item.

Why does my runbook execution stop at defined boundaries instead of completing?▼

Runbook execution stops at defined boundaries by design to ensure reliable, bounded execution of the current item, preventing scope creep and maintaining structured evidence capture within the workflow.

Do I need any specific dependencies to perform runbook execution and evidence capture?▼

No specific dependencies are required to perform runbook execution and evidence capture, as the skill operates independently using references to execute steps, capture evidence, and write back records with signed timestamps.