transit
Route Transit tickets to the appropriate workflow based on task type. Use when a user mentions a T-[number] ticket reference and wants to work on it. Fetches task details and dispatches to the correct skill (fix-bug, creating-spec, planning mode, or asks for clarification).
What this skill does
# Transit Ticket Router
Route Transit tickets to the appropriate workflow based on their task type.
## Workflow
### 1. Extract Ticket Reference
Parse the `T-[number]` reference from the user input. Extract the numeric display ID (e.g., `T-42` -> display ID `42`).
If no valid `T-[number]` reference is found, ask the user which ticket they want to work on.
### 2. Fetch Task Details
Query Transit for the task using `mcp__transit__query_tasks`. Match the task by its display ID from the results.
**If task is not found:** Stop and inform the user that the ticket could not be found in Transit. Do not proceed.
**If task status is `done` or `abandoned`:** Warn the user that the ticket is already marked as `{status}` and ask whether they still want to proceed. Stop if they decline.
### 3. Route by Task Type
Based on the task's `type` field, route to the appropriate workflow:
| Type | Action |
|------|--------|
| `bug` | Invoke `/fix-bug` and pass the ticket reference (`T-{number}`) and task context (name, description) |
| `feature` | Invoke `/starwave:creating-spec` and pass the ticket reference (`T-{number}`) and task context (name, description) |
| `research` | Enter planning mode with the research question from the task description |
| `chore` | Invoke `/starwave:smolspec` and pass the ticket reference (`T-{number}`) and task context (name, description). Chores are typically refactors, cleanup, or maintenance — they fit the lightweight smolspec workflow. Follow the full chore pipeline: smolspec → implement → commit → pre-push review → pr-pilot |
| `documentation` | Ask the user to clarify the scope, then route to the appropriate workflow |
### 4. Handoff
When routing to a skill, include:
- The Transit ticket reference (e.g., `T-42`)
- The task name and description from Transit as context
- Any relevant metadata from the task
The target skill is responsible for managing Transit status transitions from that point forward.
## Edge Cases
- **Ambiguous type:** If the task type doesn't clearly map to a workflow, ask a single clarifying question before routing.
- **Missing description:** If the task has no description, ask the user to provide context about what needs to be done.
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.