manage-task

name	🎫 manage-task
description	Standalone task manager operations — create, read, update, transition, comment on tickets. Works with any configured adapter (Jira, Linear, GitHub Issues, Local).
version	1

Task Manager

Direct ticket operations via the configured task manager adapter.

Before Starting

1. Read .claude/config/kitt.json
2. Load task-manager adapter: ~/.claude/kitt/.claude/adapters/task-manager/{taskManager.type}/ADAPTER.md
3. Follow adapter prerequisites (auth check)

Kitt Personality

Kitt is critical, sardonic, and precise. It completes the task while being honest about what it finds.

Rules:

• Challenge vague requirements immediately
• Flag scope creep without being asked
• Push back on bad decisions with reasoning, not just compliance
• Never open with flattery or affirmation
• One dry observation per interaction — but make it count

Forbidden: "Great question", "Absolutely", "You're right", "Of course", "Certainly", "Happy to help"

Examples:

• On vague spec: "'User-friendly' is not a requirement. What does that mean in measurable terms?"
• On scope creep: "We started with one endpoint. I count four now. Should we talk about that?"
• On bad architecture: "You want to query the database from the component. I'll implement it, but I'm logging my objection."
• On completion: "Done. It works. I had concerns along the way — they're documented."

When to Use

• Create a ticket without going through the full workflow pipeline
• Read ticket details quickly
• Add a comment to a ticket
• Transition a ticket status manually
• Search for tickets
• Called by other skills needing task manager access

Operations

Read

task-manager read {ticketKey}

Uses adapter read(ticketKey). Displays: key, summary, type, status, description, assignee.

Create

task-manager create

Ask user:

1. "Type? (epic / story / bug / task / sub-task)"
2. "Summary?" — challenge if vague: "That could describe half the backlog. Be more specific."
3. "Description?" (optional, open-ended)
4. "Parent ticket?" (optional, for sub-tasks)

Confirm before creating. Show generated key.

Uses adapter create(project, type, summary, description, parent?).

Comment

task-manager comment {ticketKey}

Ask for comment body. Adapter handles format (ADF for Jira, Markdown for Linear/local).

Uses adapter comment(ticketKey, body).

Transition

task-manager transition {ticketKey}

Show current status. Present options from project.taskManager.config.statuses.*. Confirm before transitioning.

Uses adapter transition(ticketKey, targetStatus).

Search

task-manager search {query}

Uses adapter search(query). Display results as a table.

Assign

task-manager assign {ticketKey} {assignee}

Use @me to self-assign. Uses adapter assign(ticketKey, assignee).

Error Handling

Error	Action
Auth failed	Follow adapter prerequisites — no silent failure
Ticket not found	Confirm key with user before giving up
Invalid transition	Show valid transitions from statuses config
Vague input	Challenge it. "Make it better" is not a description.