ask-dev-looplisted

# Ask Dev Loop The human does not remember every skill. Ask. This is a **router**: it names the skill to type next and why. It hints. It does not fire other user-invoked skills. Model-invoked primitives (`grilling`, `domain-modeling`, `tdd`, `debug`) may be named as what the chosen skill will run. ## Contract Inputs: - A situation in plain language (an idea, a bug, a PR, a foggy large effort, a setup question, or "I don't know where to start") Outputs: - The recommended skill to type, one sentence of why, and the next step after that - Neighbours when two skills are easy to confuse Creates/Modifies: - None External Side Effects: - None Confirmation Required: - None. Advisory only. Delegates To: - None. Name the skill; the human types it. ## Precondition If `docs/agents/issue-tracker.md` is missing, recommend `/setup-agent-routing` first. The other engineering skills read that routing block. ## The main flow: idea → ship The route most work travels. 1. **`/interview`** — sharpen the idea. Repo-grounded; runs `grilling` and `domain-modeling`; leaves an interview brief. Start here whenever the working directory is a real repo. 2. **Branch — does a design question need a runnable answer?** Detour through `/prototype` (throwaway code that answers one question), then return to the brief. 3. **Branch — is this a multi-session build?** - **Yes** → `/prd write` (`prd-writer`) then `/prd intake` (`feature-intake`) or `writing-plans` on the issu