skills.rest
terencefan
terencefanCOMMUNITY
Explore all skills by this author →
GitHub

runbook-acceptor

Verify a single runbook acceptance item with structured rules and evidence capture.

1|Updated Apr 22, 2026
Search Tags:#workflow#validation#sign-off#runbook#acceptance#team-workflow#item-level
One-click install
npx skills add https://github.com/terencefan/inority-workspace --skill runbook-acceptor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: runbook-acceptor
Source: https://github.com/terencefan/inority-workspace/tree/main/skills/runbook-acceptor
Command: npx skills add https://github.com/terencefan/inority-workspace --skill runbook-acceptor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating runbook acceptance is error-prone and time-consuming when performed inline within larger rollout workflows. This skill provides a focused, bounded acceptance sub-skill that validates only the current item’s #### 验收, enabling solo main rollout or team acceptance lane to stop at the acceptance boundary and produce auditable evidence.

Core Features & Use Cases

  • Dedicated acceptance scope for a single item’s #### 验收 to prevent scope creep.
  • Flexible operating modes: solo main rollout or team acceptance lane, with strict boundary isolation.
  • Clear evidence capture and sign-off prompts to support auditable outcomes and faster planning.

Quick Start

Lock the current item to its ####验收 scope and begin the acceptance checks immediately.

Frequently Asked Questions about runbook-acceptor

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

FAQPage Schema
How do I automate runbook acceptance and sign-off for a single item?▼

Runbook acceptance is automated by locking the workflow to a single item's validation scope, enforcing structured rules, and capturing required signatures before progression. This isolates the acceptance boundary to prevent scope creep.

What is the best way to isolate runbook validation from execution and reconnaissance tasks?▼

Runbook validation is isolated by applying strict boundary rules that exclude execution and reconnaissance phases. The process concentrates solely on the current item's acceptance checks to ensure compliance without scope creep.

Can I use item-level acceptance checks for team acceptance lane workflows?▼

Item-level acceptance checks support both solo main rollout and team acceptance lane workflows. Flexible operating modes enforce boundary isolation, ensuring the team stops at the acceptance boundary to produce auditable evidence.

How do I capture auditable evidence during the runbook sign-off phase?▼

Auditable evidence is captured during runbook sign-off through clear success criteria and structured prompts. The system enforces required signatures and records validation outcomes at the acceptance boundary.

Why does my runbook validation fail during the rollout progression phase?▼

Runbook validation fails during progression if structured acceptance rules are not met or required signatures are missing. The process enforces strict boundary isolation and compliance checks before allowing the workflow to advance.

Do I need a dedicated acceptance sub-skill to prevent scope creep in rollout workflows?▼

A dedicated acceptance sub-skill is needed to prevent scope creep by bounding validation to a single item. It stops inline rollout workflows at the acceptance boundary, enforcing structured rules and capturing auditable evidence.

Related Skills

Explore More Software Engineering Skills→
terencefanterencefan
1

runbook-team

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

Community
Advanced
hashi-demo-labhashi-demo-lab

tf-implement

Orchestrate multi-phase Terraform provisioning with sandbox testing and VCS commits.

Official
Advanced
roycolumbia-coderoycolumbia-code

gsd-ai-integration-phase

Generate AI-SPEC.md design contracts and orchestrate workflow tasks.

Community
Advanced
sayedihashimisayedihashimi
2

migrate-nullable-references

Enable Nullable Reference Types and migrate C# code with zero-runtime changes.

Community
Advanced