Agent skill · shipshitdev
ask-dev-loop
Ask which Dev Loop skill or flow fits the current situation. A router over the flagship idea-to-ship path.
What it needs
About 2k tokens when loaded.
What this skill does
Ask Dev Loop The human does not remember every skill. Ask. This is an advisory router: name the skill to type next and why, then stop. Execution routers can invoke reusable engines within an authorized task, but this skill only recommends. grilling, domain-modeling, tdd, and debug may be named as what the chosen workflow 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 issue, then /loop / executing-plans per ticket. No → writing-plans in this session, then executing-plans (or just implement with /tdd). Keep grilling, spec, and tickets in one context window. Each /loop / executing-plans run starts fresh from the ticket. On-ramps Bugs and incoming requests piling up → /prd intake (feature-intake) or github-inbox. Tickets that prd-task-creator already wrote are agent-ready; do not re-intake them. Something's broken → /debug (or systematic-debugging when previous fixes failed). Tight red loop first; no theory without a loop. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills shipshitdev/ask-dev-loop