team-questionlisted

# Team Question — Decompose the Task Run the QUESTION phase only, then stop. The Question phase decomposes the user's intent into the artifacts that the rest of the QRSPI pipeline consumes: - `task.md` — the human's full intent. Read by `design-author` and downstream phases that need intent. **Never** read by `researcher` or `file-finder` — they only see `questions.md`. - `questions.md` — neutral research questions phrased without intent. The only file `researcher` and `file-finder` ever read. - `prd.md` — written **only when the request is vague, multi-story, cross-cutting, or replaces existing behavior** (criteria in `skills/product-requirements-doc/SKILL.md`, loaded conditionally through `skills/decomposing-intent/SKILL.md`). Referenced from `task.md`. read downstream by `design-author`. - `repos.md` — written **only when the topic spans more than one repository**. Lists each involved repo's slug, absolute path, and role. Its presence switches the rest of the pipeline into multi-repo mode (one worktree per repo, slice/step `[repo: <slug>]` annotations, one PR per repo). See `skills/qrspi-workflow/SKILL.md` for the schema and `skills/decomposing-intent/SKILL.md` for the detection rules. These files live in `docs/plans/<id>/` where `<id>` is either a ticket-derived slug (`ENG-1234-add-rate-limiting`) or a date-derived slug (`2026-05-01-add-rate-limiting`). ## Input `$ARGUMENTS` may be: - A ticket identifier (e.g. `ENG-1234`) — recorded as `ticke