create-item

Solid

Create an MCP work item from conversation context. Scans existing containers to anchor the item in the right place (Bugs, Features, Tech Debt, Observations, etc.), infers type and priority, creates single items or work trees, and pre-fills required notes. Use this whenever the conversation surfaces a bug, feature idea, tech debt item, or observation worth tracking persistently. Also use when user says "track this", "log this bug", "create a task for", or "add this to the backlog".

AI & Automation 193 stars 22 forks Updated today MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
76
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 ``` query_items(operation="overview", includeChildren=true) ``` Classify the existing structure: | Pattern | Classification | |---------|---------------| | Depth-0 item with category-named children (Bugs, Features, etc.) | **Hierarchical** — project root exists | | Category-named items at depth 0, no project root | **Flat** — use category containers directly | | No items at all | **Empty** — offer to create project root | --- ## Step 3 — Container anchoring ### Category mapping | Item type | Target category container | Signal keywords | |-----------|--------------------------|-----------------| | Bug / error / crash / unexpected behavior | Bugs | bug, error, crash, broken, failure, wrong, exception | | Feature / enhancement...

Details

Author
jpicklyk
Repository
jpicklyk/task-orchestrator
Created
1 years ago
Last Updated
today
Language
Kotlin
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category