What problem does it solve? Hand-authoring a project-local playbook JSON file is error-prone: ids can collide with existing playbooks, skill names can be misspelled, and required fields like keywords and examples are easy to omit, leaving a file that fails schema validation or never matches natural-language requests. This Skill walks you through each required field, validates every input against the live playbook and skill catalogs, and confirms the written file actually loads before reporting success. ## Core Features & Use Cases - Guided field-by-field wizard: Prompts for id, name, description, keywords, examples, and an ordered list of at least two skills, re-prompting with verbatim reasons whenever validation fails. - Live catalog validation: Checks id slug format and uniqueness against the merged built-in plus project playbook catalog, and validates each skill name against the generated skill catalog used by natural-language matching. - Self-validating writes: Writes project/.playbooks/<id>.json via a deterministic script, then re-validates the file through the playbook loader before declaring success. - Use Case: You want a custom release workflow chaining your plan, implement, and test skills. Run the wizard, answer the prompts, and receive a confirmed-loadable playbook invocable by id or matched from free-text requests. ## Quick Start Ask the agent to help you create a new project-local playbook and follow the guided prompts for id, name, description, keywords, examples, and the ordered skill chain.
