playbook-init

Delegate new task requests to the pm SubAgent for playbook creation and state updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/M2AI-jp/thanks4claudecode-fresh --skill playbook-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-init
Source: https://github.com/M2AI-jp/thanks4claudecode-fresh/tree/main/.claude/skills/playbook-init
Command: npx skills add https://github.com/M2AI-jp/thanks4claudecode-fresh --skill playbook-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guarantees that every new task starts through the mandated pm SubAgent, ensuring a formal kickoff and consistent data collection.

Core Features & Use Cases

  • PM delegation: Always route task start through the pm SubAgent.
  • Handover orchestration: Trigger understanding-check, create a playbook skeleton, and pass review.
  • State synchronization: Update state.md to reflect current playbook status and branch.

Quick Start

Invoke the Skill(skill='playbook-init') or run /playbook-init to begin a new task.

Frequently Asked Questions about playbook-init

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

FAQPage Schema
How do I ensure task requests go through a formal pm delegation process?

Task initiation through playbook-init forces delegation to the pm SubAgent, guaranteeing formal kickoff. When a task request arrives with keywords like 'make,' 'implement,' 'modify,' or 'add' in playbook=null state, the Skill triggers the Hook → Skill → SubAgent chain, routing all new tasks through pm for understanding-check, playbook creation, reviewer validation, and state synchronization.

When should I use playbook-init to start a new task?

Invoke playbook-init when beginning any new task requiring structured handover and data collection. The Skill applies when the system enters playbook=null state and task requests contain action verbs. Use it to guarantee every task starts with pm SubAgent involvement instead of direct handling, ensuring consistent prerequisite checks and playbook skeleton creation.

What does playbook-init do after task delegation to pm?

After delegating to the pm SubAgent, playbook-init enforces a complete handover chain: understanding-check validation, playbook skeleton creation, reviewer sign-off, and state.md updates reflecting current playbook status and branch. The Skill prohibits self-handling and ensures all state synchronization occurs through the pm SubAgent.

Can I use playbook-init to bypass the pm SubAgent for quick tasks?

No. Playbook-init is designed to prohibit self-handling and enforce pm SubAgent delegation on every task initiation. The Skill guarantees formal kickoff routing; it does not support bypassing the pm workflow, even for small requests. Direct handling is blocked when playbook=null and task verbs trigger the delegation chain.

How does playbook-init synchronize task state across the workflow?

Playbook-init updates state.md to reflect current playbook status and branch after pm SubAgent completes understanding-check, playbook creation, and reviewer validation. This state synchronization occurs automatically as part of the delegated handover chain, ensuring consistent data collection and task orchestration visibility.

What happens if I invoke playbook-init without action keywords in my request?

Playbook-init only triggers the pm delegation chain when task requests contain action verbs like 'make,' 'implement,' 'modify,' or 'add' in playbook=null state. Without these keywords, the Skill prerequisites are not met and delegation does not occur. The Hook → Skill → SubAgent chain requires both the trigger condition and the appropriate task verb syntax.