@sascha384/tic 1.6.0 → 1.8.0

package/skills/tic-config/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: tic-config
+description: Use when initializing projects, checking configuration, or changing backends/iterations
+---
+
+# tic Configuration
+
+Use these tools to initialize and configure tic projects.
+
+## Tools
+
+### init_project
+
+Creates a `.tic/` directory in the current project. Call this first if other tools fail with "Not a tic project".
+
+### get_config
+
+Returns project configuration:
+- `backend` — current backend type (local, github, gitlab, azure, jira)
+- `statuses` — available status values
+- `types` — available work item types
+- `iterations` — configured iterations
+- `currentIteration` — active iteration filter
+- `capabilities` — what the backend supports
+
+**Always call this first** to understand what types, statuses, and iterations are available before creating or updating items.
+
+### set_backend
+
+Switch between backends: `local`, `github`, `gitlab`, `azure`, `jira`.
+
+The backend is auto-detected from git remotes, but can be overridden.
+
+### set_iteration
+
+Set the current iteration filter. This affects which items appear in `list_items` and `search_items` unless `all: true` is passed.
+
+## Capabilities
+
+The `capabilities` object from `get_config` tells you what the backend supports:
+
+```json
+{
+  "relationships": true,    // parent/child, dependencies
+  "customTypes": true,      // configurable work item types
+  "customStatuses": true,   // configurable statuses
+  "iterations": true,       // iteration/sprint support
+  "comments": true,         // commenting on items
+  "fields": {
+    "priority": true,
+    "assignee": true,
+    "labels": true,
+    "parent": true,
+    "dependsOn": true
+  }
+}
+```
+
+Check capabilities before using optional fields — not all backends support all features.

package/skills/tic-items/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: tic-items
+description: Use when creating, updating, listing, searching, or deleting work items
+---
+
+# tic Work Items
+
+Use these tools to manage work items across any backend.
+
+## Before You Start
+
+Call `get_config` first to understand:
+- Available `types` (e.g., epic, issue, task)
+- Available `statuses` (e.g., backlog, todo, in-progress, done)
+- Available `iterations`
+- Backend `capabilities` (which fields are supported)
+
+## Tools
+
+### list_items
+
+List work items with optional filters:
+- `type` — filter by work item type
+- `status` — filter by status
+- `iteration` — filter by iteration
+- `all` — show all iterations (ignores current iteration filter)
+
+Use filters rather than fetching all and filtering locally.
+
+### show_item
+
+Get full details of a work item by ID. Returns all fields including description, comments, and a `url` for opening in browser/editor.
+
+### search_items
+
+Text search across title and description. Supports the same filters as `list_items`.
+
+### create_item
+
+Create a new work item. Required field:
+- `title` — work item title
+
+Optional fields (check capabilities first):
+- `type` — defaults to first available type
+- `status` — defaults to first available status
+- `priority` — low, medium, high, critical
+- `assignee` — who owns this
+- `labels` — comma-separated tags
+- `iteration` — which sprint/milestone
+- `parent` — ID of parent item
+- `depends_on` — array of IDs this item depends on
+- `description` — full details
+
+### update_item
+
+Update an existing work item. Required field:
+- `id` — work item ID
+
+All other fields are optional — only pass what you want to change.
+
+To clear a parent relationship, pass `parent: null`.
+
+### delete_item / confirm_delete
+
+**Two-step deletion for safety:**
+
+1. Call `delete_item` with the ID — returns a preview showing:
+   - The item being deleted
+   - Children that will be unparented
+   - Dependents that will lose this dependency
+
+2. Call `confirm_delete` with the same ID to execute
+
+This prevents accidental data loss. Always preview before confirming.
+
+### add_comment
+
+Add a timestamped comment to a work item. Only available if backend supports comments (check `capabilities.comments`).
+
+- `id` — work item ID
+- `text` — comment content
+- `author` — optional, defaults to system
+
+## Example Workflow
+
+```
+1. get_config → understand available types/statuses
+2. list_items with type: "task", status: "todo" → see open tasks
+3. create_item with title, type, priority → create new item
+4. update_item with id, status: "in-progress" → update status
+5. add_comment with id, text → add progress note
+```

package/skills/tic-relationships/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: tic-relationships
+description: Use when working with parent-child hierarchies or dependencies between items
+---
+
+# tic Relationships
+
+Use these tools to navigate and manage work item hierarchies and dependencies.
+
+## Prerequisites
+
+Check `capabilities.relationships` from `get_config` — not all backends support relationships.
+
+## Tools
+
+### get_item_tree
+
+Get all work items as a hierarchical tree structure. Children are nested under their parents.
+
+Best for understanding overall project structure. Supports same filters as `list_items`:
+- `type`, `status`, `iteration`, `all`
+
+### get_children
+
+Get direct children of a specific work item.
+
+- `id` — parent work item ID
+
+Returns array of child work items.
+
+### get_dependents
+
+Get items that depend on (are blocked by) a specific work item.
+
+- `id` — work item ID
+
+Returns array of dependent work items. Useful for understanding impact before completing or deleting an item.
+
+## Setting Relationships
+
+### Parent-Child
+
+Set during `create_item` or `update_item`:
+- `parent: "123"` — set parent to item 123
+- `parent: null` — clear parent (make root-level)
+
+Children appear indented under their parent in tree views.
+
+### Dependencies
+
+Set during `create_item` or `update_item`:
+- `depends_on: ["123", "456"]` — this item is blocked by items 123 and 456
+
+Dependencies indicate work that must complete before this item can proceed.
+
+## Validation
+
+The backend enforces:
+- **No circular parents** — item cannot be its own ancestor
+- **Referential integrity** — referenced items must exist
+
+## Cleanup on Delete
+
+When an item is deleted:
+- Children have their `parent` cleared (become root-level)
+- The item is removed from other items' `depends_on` lists
+
+The `delete_item` preview shows these affected items before you confirm.
+
+## Warnings
+
+When completing an item (`status: "done"`), tic warns if:
+- Item has open children
+- Item has unresolved dependencies
+
+These are warnings, not blockers — you can proceed if appropriate.