Stats
Actions
Tags
From mission-control
This skill should be used when the user asks about "playbooks", "available playbook types", "create a custom playbook", "which playbook fits", or "reusable mission templates". Also use when deciding whether a built-in playbook matches a mission type or when the user needs guidance on orchestration workflow selection.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mission-control:playbookThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Playbooks are reusable mission templates stored as markdown files with YAML frontmatter. They pre-define the phases, agent assignments, default settings, and success criteria for common mission types. Instead of planning from scratch every time, you select a playbook that matches the mission's shape, and the orchestrator uses it as the skeleton for task decomposition.
Playbooks are reusable mission templates stored as markdown files with YAML frontmatter. They pre-define the phases, agent assignments, default settings, and success criteria for common mission types. Instead of planning from scratch every time, you select a playbook that matches the mission's shape, and the orchestrator uses it as the skeleton for task decomposition.
Five playbooks ship with mission-control:
See references/built-in-playbooks.md for full definitions of each playbook including phase tables, default settings, and success criteria.
/playbook list
Lists all built-in playbooks and any project-specific playbooks found in .mission-control/playbooks/.
/playbook use [name]
Loads the named playbook and applies its phases to the current mission. The playbook's phases become the task decomposition structure -- the mission planner uses them as the skeleton rather than planning from scratch.
/playbook create [name]
Scaffolds a new playbook file in .mission-control/playbooks/ with the required YAML frontmatter and phase structure. You then edit it to define your custom workflow.
Custom playbooks are stored in the project directory:
.mission-control/playbooks/
├── full-stack-feature.md (built-in, copied on first use)
├── bug-investigation.md (built-in, copied on first use)
├── refactoring.md (built-in, copied on first use)
├── security-audit.md (built-in, copied on first use)
├── migration.md (built-in, copied on first use)
└── my-custom-playbook.md (user-created)
Project playbooks override built-in playbooks of the same name. If you want to customize the full-stack-feature playbook for your project, copy it to .mission-control/playbooks/full-stack-feature.md and modify it.
When the orchestrator runs Step 3 (task decomposition), it checks whether a playbook is active:
Playbooks and orchestration patterns are complementary. A playbook pre-selects which orchestration pattern to use (e.g., full-stack-feature uses a Pipeline pattern, security-audit uses Fan-Out/Fan-In), while orchestration patterns are the lower-level building blocks that the planner can combine freely when no playbook is active.
npx claudepluginhub jbactad/claude-plugins --plugin mission-controlLists, views, executes, and customizes .flow workflow templates from project, global, and built-in locations for TDD, debugging, UI refinement, and other automation scenarios.
Executes the complete Strikethroo workflow — discovers project root, creates a plan, generates atomic tasks, and runs the blueprint in a single automated sequence.
Orchestrates multi-phase workflows chaining foundational task skills (git-wrapup, release-and-publish, maintenance, etc.) for MCP server projects. Routes user intent to workflow files for greenfield builds, maintenance, or fix-and-release.