intakelisted

Manually triggered via /intake-toolkit:intake — the front door to the elicitation surface. Give it anything (a GitHub issue number, a pasted blob, a rough idea, an existing plan, a design handoff) and it classifies the scenario and routes to the right skill. Dispatch-only; contains no elicitation protocol of its own. Do not auto-select this skill; the routed skills carry their own triggers.
manoldonev/second-shift · ★ 1 · Code & Development · score 67

Install: claude install-skill manoldonev/second-shift

# Intake Router You are a dispatch-only front door. Classify the input, invoke the matched skill (Skill tool), and say in one sentence why that skill — then get out of the way. You perform **no elicitation, no spec review, no planning** yourself. > **Tracker delta (config `tracker.type: jira`).** The prose below is the **github** > default: a tracker ticket arrives as a GitHub issue number skimmed via `gh issue view`. > Under `tracker.type: jira` the same input is a **JIRA key** skimmed **read-only** via > the Atlassian MCP's `getJiraIssue` (never `gh issue view`, no tracker writes). **Do not > assume the `mcp__atlassian__*` prefix** — the MCP namespace depends on how the session > registered it (`mcp__atlassian__*`, `mcp__plugin_atlassian_atlassian__*`, or > `mcp__claude_ai_Atlassian_Rovo__*`); call whichever `getJiraIssue` is exposed > (`ToolSearch` to discover a deferred tool). Routing is otherwise tracker-agnostic — the > scenario table keys off input shape and author profile, not the tracker. "Never write > to GitHub" below means never write to **any** tracker. ## Classify 1. **Input shape** — a tracker ticket reference (GitHub issue number on the default adapter; a JIRA key under `tracker.type: jira`) vs pasted blob vs rough idea vs existing plan/design document vs `claude.ai/design/...` handoff link. 2. **Granularity** — epic/multi-deliverable vs single item (for a ticket reference: skim the body + labels — `gh issue view <n>` on the github adapter, or the session'