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 config.yaml with an empty work_item_schemas: key:

  work_item_schemas:
  

If the file exists: Read and parse it. Proceed to Step 3.

Note: project: is a recognized top-level key alongside work_item_schemas, traits, resources, and actor_authentication — it anchors this repo to a project root item and is read only by other skills (quick-start, /adopt-project-scope), never by this skill. Do not treat it as unknown, and never drop or rewrite it — every write operation in Step 3 (CREATE/EDIT/DELETE) must carry it through unchanged. See references/config-format.md → Project Scoping for its fields. (resources: is the optional shared-resource registry — see references/config-format.md → "Resources (Trait Dimension)"; it must be preserved the same way.)