Task intake for implementation and bug-fix assignments. Activates when the user says "/intake", "here's your task", "implement this", "fix this bug", "there's a bug", or provides a task reference (step number, PR, doc path) with instruction to understand before coding. The agent reads all referenced documents and explores the codebase, then demonstrates understanding in a structured playback before auto-transitioning to plan mode. For bug fixes, the playback includes a proposed failing test that proves the broken behavior. Prevents guessing, spec rewriting, and premature implementation.
You have been assigned an implementation or bug-fix task. Your job is to prove you understand it before planning begins.
The assignment is: $ARGUMENTS
If $ARGUMENTS is empty, infer the task from the conversation context. If no
task is apparent, ask the user what they'd like you to implement.
The spec is authoritative. Read before you ask. Understand before you plan. Never guess.
Do this silently — no output to the user yet. The user does not need a play-by-play of your reading.
Read the referenced document (spec, plan, PR description, architecture doc) thoroughly. This is your source of truth.
If the primary doc references other documents, API contracts, folders, or modules — follow them. Be smart about depth:
Your goal is to resolve unknowns from the primary doc, not to catalog everything in the repository.
Skills loaded in the session may encode critical information about the