playbook

Run the playbook skill and choose Create mode. It walks you through naming the tactic, building an ordered stage list with types and agents, adding verification criteria and variables, then validates and writes the YAML to .lineup/tactics/.

Stage types are clarify, research, clarification-gate, plan, implement, verify, document, and explain. Agents are researcher, architect, developer, reviewer, documenter, and teacher, with conventional pairings like plan-architect and implement-developer.

Yes. Built-in tactics shipped with the plugin are read-only, but creating a project tactic with the same name in .lineup/tactics/ overrides the built-in. The skill warns you when a name conflicts with a built-in tactic.

Variables are defined with snake_case names, descriptions, and defaults, then referenced in stage prompts as ${variable_name}. The orchestrator prompts the user for values at runtime, and the skill validates that every reference resolves to a defined variable.

Semantic checks warn without blocking when a verify stage lacks criteria, an implement stage has no preceding plan stage, a plan stage lacks an approval gate, or variables are unused. These are recommendations, not errors.