playbookslisted

# Playbook Management The user wants to manage project-specific playbooks that customize how agents work in this project. ## Protocol 1. **Parse arguments**: `$ARGUMENTS` - If empty or "list": Show all playbooks in table format - If starts with "add": Create a new playbook interactively - If starts with "view": Show full content of named playbook - If starts with "remove": Delete named playbook with confirmation - If "help": Show playbook format and examples ### List Operation Glob `.orchestray/playbooks/*.md`. If the directory does not exist or no `.md` files are found, report: "No playbooks found. Use `/orchestray:playbooks add <name>` to create one." For each file found, read the first line (`# Playbook: <name>`), the `## When` section, and the `## Applies To` section. Display a table: ``` | Name | Triggers | Applies To | |------|----------|------------| | {name} | {when summary, first line only} | {applies to or "all"} | ``` Below the table, show: "{N} playbook(s) found." Then show usage hints: - `add <name>` -- Create a new playbook - `view <name>` -- Show full playbook contents - `remove <name>` -- Remove a playbook - `help` -- Show format and examples ### Add Operation Parse the playbook name from arguments (the word after "add"). If no name is provided, ask the user for one. Create `.orchestray/playbooks/` directory if it does not exist. Check if `.orchestray/playbooks/<name>.md` already exists. If so, report: "Playbook '{name}' already exi