playbook-gate

Name: playbook-gate
Availability: InStock
Author: m2ai-jp

Block Edit/Write actions when playbook.active is null across executors.

Updated Aug 27, 2026

Search Tags:#playbook #guard #block edits #phase-dependency #pretool #pre-tool

Ready to run

npx skills add https://github.com/M2AI-jp/thanks4claudecode-fresh --skill playbook-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playbook-gate
Source: https://github.com/M2AI-jp/thanks4claudecode-fresh/tree/main/.claude/skills/playbook-gate
Command: npx skills add https://github.com/M2AI-jp/thanks4claudecode-fresh --skill playbook-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents any Edit/Write actions when playbook.active is null, enforcing discipline and preventing untracked work.

Core Features & Use Cases

Playbook guard: Blocks edits when playbook is missing or inactive.
Executor & depends guards: Enforces allowed executors and checks phase dependencies.
Role resolution: Translates abstract roles into concrete executors based on toolstack and playbook meta.

Quick Start

This gate runs as a PreTool guard and can be invoked by prompts that trigger editing or writing.

Frequently Asked Questions about playbook-gate

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

FAQPage Schema

How do I prevent edits when a playbook isn't active?▼

Playbook Gate blocks Edit/Write actions when playbook.active is null in state.md, enforcing that all changes occur within an active playbook. It runs as a PreTool guard to intercept editing attempts and validate playbook presence before allowing modifications.

What happens when I try to write without an active playbook?▼

The gate denies the Write action and halts execution. Playbook Gate validates playbook.active status; if null, the edit is blocked, ensuring no untracked work proceeds outside playbook discipline.

How does phase dependency checking work in playbook guards?▼

Playbook Gate validates phase progression by checking phase dependencies through depends-check.sh logic. It confirms the current phase allows the requested action before permitting edits, preventing out-of-order operations.

Can I restrict edits to specific executors or roles?▼

Yes. Playbook Gate enforces executor and role permissions by resolving abstract roles into concrete executors based on toolstack and playbook metadata, then validating whether the current executor is allowed to perform the edit.

Does this guard work with multiple executors?▼

Playbook Gate applies to pre-tool and post-tool events across multiple executors, enforcing consistent playbook and phase validation regardless of which executor attempts the edit.

How do I archive completed playbooks after edits?▼

After Playbook Gate permits edits and tasks complete, archive workflows move finished playbooks out of the active state. This follows the same playbook metadata validation to ensure only properly-tracked work gets archived.