manage-schemas

# Manage Schemas — Note Schema Lifecycle Create, view, edit, delete, and validate note schemas in `.taskorchestrator/config.yaml`. Schemas define which notes agents must fill at each workflow phase before advancing items. --- ## Step 1 — Determine Intent Classify from `$ARGUMENTS` and conversation context before making any tool calls. | Signal words | Action | |---|---| | "create", "build", "new", "add schema", "define", "set up" | CREATE | | "recommend", "advise", "design", "what schema should I use", "help me choose", a described workflow with no schema name | CREATE (advisor path) | | "show", "view", "list", "what schemas", "display" | VIEW | | "edit", "modify", "change", "update", "add note to", "remove note from" | EDIT | | "delete", "remove schema", "drop" | DELETE | | "validate", "check", "verify", "lint" | VALIDATE | If `$ARGUMENTS` contains both an action and a schema name (e.g., "view bug-fix"), extract both. If intent cannot be determined, ask via `AskUserQuestion` with options: Create, View / Validate, Edit, Delete. > Validate is grouped with View — both are read-only operations on the config file. --- ## Step 2 — Config Bootstrap Check if `.taskorchestrator/config.yaml` exists by reading it. **If the file does not exist:** - For **VIEW** or **VALIDATE**: report "No schemas configured — `.taskorchestrator/config.yaml` does not exist." and stop. - For **CREATE**, **EDIT**, or **DELETE**: create the `.taskorchestrator/` directory if missing, then create `...