From task-orchestrator
Manages note schemas for MCP Task Orchestrator: create, view, edit, delete, validate in .taskorchestrator/config.yaml. Use for schema lifecycle tasks like 'create schema' or 'edit schema'.
npx claudepluginhub jpicklyk/task-orchestrator --plugin task-orchestratorThis skill uses the workspace's default tool permissions.
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.
Guides schema-tagged MCP work items through lifecycle phases by filling required notes per schema guidance and advancing queue/work/review/terminal gates.
Create and manage DeepSchemas for automatic file validation on write/edit and review rule generation using YAML requirements and JSON Schemas. Matches files via globs.
Authors UiPath Case Management caseplan.json and tasks.md from sdd.md, or generates sdd.md via Phase 0 interview if absent. For new case projects, not modifications.
Share bugs, ideas, or general feedback.
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.
Classify from $ARGUMENTS and conversation context before making any tool calls.
| Signal words | Action |
|---|---|
| "create", "build", "new", "add schema", "define", "set up" | CREATE |
| "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.
Check if .taskorchestrator/config.yaml exists by reading it.
If the file does not exist:
.taskorchestrator/config.yaml does not exist." and stop..taskorchestrator/ directory if missing, then create config.yaml with an empty note_schemas: key:
note_schemas:
If the file exists: Read and parse it. Proceed to Step 3.
Interactive Q&A flow that gathers schema requirements, generates YAML, merges into config, and optionally creates a companion lifecycle skill.
For detailed workflow, see references/create-workflow.md in this skill folder.
Read .taskorchestrator/config.yaml and display schemas in a summary table:
◆ Note Schemas — .taskorchestrator/config.yaml
| Schema Tag | Queue Notes | Work Notes | Review Notes | Total |
|---|---|---|---|---|
| feature-implementation | 2 (2 req) | 2 (2 req) | 1 (0 req) | 5 |
| bug-fix | 2 (2 req) | 2 (2 req) | — | 4 |
If the user specified a schema name, show that schema's full detail: each note with key, role, required, description, and guidance.
Read current config, display the target schema, ask what to change (add note, remove note, toggle required, change description/guidance, rename key), apply changes, write back.
If the target schema is not found in config.yaml, inform the user and offer to CREATE instead.
For detailed workflow, see references/edit-workflow.md in this skill folder.
Read current config, confirm the schema name, warn about orphaned notes on existing items, remove the key, write back.
If the target schema is not found in config.yaml, inform the user and offer to CREATE instead.
For detailed workflow, see references/delete-workflow.md in this skill folder.
Run structural and semantic checks on the config file and report issues with fix suggestions.
For detailed workflow, see references/validate-workflow.md in this skill folder.
For write operations (CREATE, EDIT, DELETE):
/mcp) for schema changes to take effect — the server caches schemas on first accessFor VIEW and VALIDATE: The output from Step 3 is the deliverable — no additional report needed.
expectedNotes is empty after creating an item with the schema tag
/mcp in Claude Code to reconnect the server, then retrySchema key doesn't match — item has no schema applied
tags field doesn't contain a string matching any note_schemas keyquery_items(operation="get", id="<uuid>"). The first tag matching a schema key wins.Duplicate schema key in config file
note_schemas: and merge themChanges not taking effect after editing config
/mcp to reconnect the MCP server subprocessExample 1: View all schemas
User says: "What schemas do I have?"
.taskorchestrator/config.yamlExample 2: Add a required note to an existing schema
User says: "Add a test-plan note to the bug-fix schema"
bug-fix schema/mcp reconnect neededExample 3: Validate config after manual editing
User says: "I edited the config by hand — check it"