playbook-composer

Compose reusable multi-stage operating models with stages, handoffs, decision rights, and quality gates.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/rickvang/Persona-Library --skill playbook-composer-rickvang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playbook-composer
Source: https://github.com/rickvang/Persona-Library/tree/main/.agents/skills/playbook-composer
Command: npx skills add https://github.com/rickvang/Persona-Library --skill playbook-composer-rickvang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating a repeatable outcome across multiple Personas, Skills, Tools, and artifacts requires an explicit operating model; without one, stages, ownership, state, and failure recovery stay implicit and unverifiable. ## Core Features & Use Cases - Playbook Composition: Design a new reusable Playbook with ordered stages, entry/exit criteria, owners, shared state, decision rights, quality gates, and failure recovery paths. - Update and Repair: Compare a requested change against an existing Playbook, return the smallest change set, or inspect a Playbook for defects in stage contracts, gates, and evidence without silently rewriting it. - Use Case: When a job-search workflow needs repeatable stages for intake, application packet drafting, review, and submission with named approvers and fallback behavior, use this Skill to compose the Playbook contract before any run begins. ## Quick Start Use $playbook-composer to design a reusable Playbook for my multi-stage review workflow with defined owners, handoffs, and quality gates.

Frequently Asked Questions about playbook-composer

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

FAQPage Schema
How do I create a reusable multi-stage playbook for a team workflow?▼

Activate the skill with a defined outcome, users, constraints, and success measure. It decomposes the work into stages with owners, entry and exit criteria, handoffs, decision rights, and quality gates, returning a bounded proposal rather than executing anything.

When should I use a playbook instead of a single persona consultation?▼

Use a playbook when a repeatable outcome needs multiple stages, participants, handoffs, shared state, approvals, or failure recovery. Do not use it for one-off tasks, single persona consultations, standalone skill definitions, or simple tool lookups.

Can the playbook composer execute or run a playbook it designs?▼

No. The skill only composes, updates, evaluates, or repairs the Playbook model. Runtime execution of an already-defined Playbook is explicitly out of scope, and it never claims a stage actually ran.

Does the skill modify playbook records directly?▼

By default it returns a read-only proposal. A durable record update requires explicit authorization and a named target, after which it applies the smallest change and runs change-impact reconciliation exactly once.

What happens when a participant or tool is unavailable during playbook design?▼

Unavailable participants, tools, or dependencies are recorded as visible gaps with safe fallbacks rather than assumed available. The design stops at the verified boundary and reports the exact gap instead of continuing as if it succeeded.