create-item

# create-item — Container-Anchored Work Item Creation Create MCP work items intelligently from conversation context. This skill handles container anchoring, tag inference, structure decisions, and note pre-population so you don't have to. --- ## Step 1 — Infer intent from conversation Determine from context (or from `$ARGUMENTS` if provided): - **Title** — what is the work item? - **Type** — bug / feature / tech debt / observation / action item / general task - **Priority** — high / medium / low (default: medium) - **Scope** — single item, or feature with 2+ clear distinct subtasks? If title or type cannot be inferred with confidence, use `AskUserQuestion` with concrete options. Do not ask open-ended questions. --- ## Step 2 — Scan containers Resolve the project rootId first: check session context for a rootId injected by the SessionStart hook, or read `.taskorchestrator/config.yaml`'s top-level `project.rootId` (a file read, not an MCP call). **If a rootId is known:** ``` query_items(operation="overview", anchorId="<rootId>", includeChildren=true) ``` Category containers (Bugs, Features, Tech Debt, etc.) are expected as direct children of the project root — anchor new items there. **Exception:** `agent-observation` items always stay at global depth 0, outside any project root, regardless of whether a rootId is known — they're process-global, not project-scoped. **If no rootId is known**, fall back to an unscoped scan and the classification below (this is also the e...