decomposing-intentlisted

# Decomposing Intent The questioner's templates and procedure. Capture the user's intent in `task.md`, and write neutral research questions in `questions.md`. Record repo scope in `repos.md` when the topic spans more than one repository. ## The `topic` field `topic` must be **identical across `task.md` and `questions.md`**. It is the kebab portion of `<id>` — i.e. `<id>` minus the `<TICKET>-` or `<YYYY-MM-DD>-` prefix the orchestrator added. Never use the ticket id, the date, or a re-worded form of the description as the topic. Never write a different topic in `questions.md` than the one in `task.md`. Downstream phases (research, design, structure, plan) inherit the same topic value. The full invariant and worked examples live in `skills/artifact-frontmatter/SKILL.md`. ## task.md Capture the user's intent in their own framing. Required frontmatter: ```yaml --- topic: <kebab-case-topic> date: <YYYY-MM-DD> phase: task ticketId: null # set if a tracking ticket is tracking this work --- ``` `ticketId` lives **only** on `task.md` — no other artifact carries it (rationale in `skills/artifact-frontmatter/SKILL.md`). Then the body: ```markdown # Task: <topic> ## Description <the user's description verbatim, plus any obvious clarifications> ## Stated goal <one sentence: what the user wants to achieve> ## Inferred goal <one sentence: what they probably actually need — may be the same> ## Acceptance signals - <how the user will know this is done, even if they