skill-authoring-workflowlisted

# Skill Authoring Workflow Use this skill when creating or updating a skill in this repository. ## Discovery 1. Read any relevant existing skills first: - `operations/task-management` - `operations/task-driven-development` - `engineering/git-conventions` - `engineering/isolated-worktree` - Any existing skill in the same category 2. Infer requirements from the current conversation when the user has already described the workflow. 3. Clarify only if the skill location, scope, or trigger scenarios are genuinely ambiguous. ## Task Tracking 1. Before creating a task, read [`config/clickup-defaults.json`](config/clickup-defaults.json) and default to **`skillsRepositoryTasks`** (Skills Product Backlog) unless the user names another list. 2. Create a ClickUp task there unless the user provides an existing task. - List ID: `901614473129` (also recorded in `config/clickup-defaults.json`) - Use an action-first, sentence-case name. - Include why the skill is needed and acceptance criteria. 3. Use the task **custom ID** in commit messages (for example `AI-36`). If the user supplies a ticket ID, use that — never use ClickUp internal IDs like `86d3mw1pt` in commits. 4. Set the task to the active working status when implementation starts. - Prefer `in progress` if the list supports it. - Use `in development` when `in progress` is not a valid status. 5. Do not mark the task complete when implementation is merely finished. - Mark it complete only when t