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:
External Side Effects:
Confirmation Required:
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.
/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.- Branch — does a design question need a runnable answer? Detour through
/prototype (throwaway code that answers one question), then return to the
brief.
- 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.
- A huge, foggy effort →
roadmap-analyzer / roadmap-to-milestones to chart
the destination, then merge onto the main flow at /interview or /prd write.
Do not skip the collapse into a buildable PRD.
Codebase health
Not feature work — upkeep.
/codebase-advisor — survey, produce plans for another agent. Read-only on
source./tech-debt — ranked debt register (interest over principal).codebase-design — deep-module vocabulary when the question is the shape
of a module, not an inventory.
Review
/review (review-dispatch) — pick the review depth and target.code-review — correctness and security gate, plus spec fidelity against
the originating issue.
Standalone
/wait-what — the last message did not land; re-pitch it.grilling — the interview primitive with no wrapper. Reach for it only when
the interview itself is the whole ask.domain-modeling — the words are the problem (fuzzy term, overloaded
"account", missing ADR)./wizard — steps only a human can perform (dashboards, secrets, cutovers).fix-merge-conflicts — already mid-merge or rebase.
How to answer
Match the user's situation to one row above. Reply with:
- The skill to type (slash name when it has a command).
- Why this one, in one sentence.
- The neighbour they might have meant, if any.
- What happens after that skill finishes.
If two flows both fit, ask one question that splits them, then recommend.
1---2name: ask-dev-loop3description: Ask which Dev Loop skill or flow fits the current situation. A router over the flagship idea-to-ship path.4license: MIT5---6
7# Ask Dev Loop
8
9The human does not remember every skill. Ask.
10
11This is an **advisory router**: name the skill to type next and why, then stop.
12Execution routers can invoke reusable engines within an authorized task, but
13this skill only recommends. `grilling`, `domain-modeling`, `tdd`, and `debug`
14may be named as what the chosen workflow will run.
15
16## Contract
17
18Inputs:
19
20- A situation in plain language (an idea, a bug, a PR, a foggy large effort, a
21 setup question, or "I don't know where to start")
22
23Outputs:
24
25- The recommended skill to type, one sentence of why, and the next step after that
26- Neighbours when two skills are easy to confuse
27
28Creates/Modifies:
29
30- None
31
32External Side Effects:
33
34- None
35
36Confirmation Required:
37
38- None. Advisory only.
39
40Delegates To:
41
42- None. Name the skill; the human types it.
43
44## Precondition
45
46If `docs/agents/issue-tracker.md` is missing, recommend `/setup-agent-routing`
47first. The other engineering skills read that routing block.
48
49## The main flow: idea → ship
50
51The route most work travels.
52
531. **`/interview`** — sharpen the idea. Repo-grounded; runs `grilling` and
54 `domain-modeling`; leaves an interview brief. Start here whenever the working
55 directory is a real repo.
562. **Branch — does a design question need a runnable answer?** Detour through
57 `/prototype` (throwaway code that answers one question), then return to the
58 brief.
593. **Branch — is this a multi-session build?**
60 - **Yes** → `/prd write` (`prd-writer`) then `/prd intake` (`feature-intake`)
61 or `writing-plans` on the issue, then `/loop` / `executing-plans` per ticket.
62 - **No** → `writing-plans` in this session, then `executing-plans` (or just
63 implement with `/tdd`).
64
65Keep grilling, spec, and tickets in **one context window**. Each `/loop` /
66`executing-plans` run starts fresh from the ticket.
67
68## On-ramps
69
70- **Bugs and incoming requests piling up** → `/prd intake` (`feature-intake`) or
71 `github-inbox`. Tickets that `prd-task-creator` already wrote are agent-ready; do not
72 re-intake them.
73- **Something's broken** → `/debug` (or `systematic-debugging` when previous fixes
74 failed). Tight red loop first; no theory without a loop.
75- **A huge, foggy effort** → `roadmap-analyzer` / `roadmap-to-milestones` to chart
76 the destination, then merge onto the main flow at `/interview` or `/prd write`.
77 Do not skip the collapse into a buildable PRD.
78
79## Codebase health
80
81Not feature work — upkeep.
82
83- **`/codebase-advisor`** — survey, produce plans for another agent. Read-only on
84 source.
85- **`/tech-debt`** — ranked debt register (interest over principal).
86- **`codebase-design`** — deep-module vocabulary when the question is the *shape*
87 of a module, not an inventory.
88
89## Review
90
91- **`/review`** (`review-dispatch`) — pick the review depth and target.
92- **`code-review`** — correctness and security gate, plus spec fidelity against
93 the originating issue.
94
95## Standalone
96
97- **`/wait-what`** — the last message did not land; re-pitch it.
98- **`grilling`** — the interview primitive with no wrapper. Reach for it only when
99 the interview itself is the whole ask.
100- **`domain-modeling`** — the words are the problem (fuzzy term, overloaded
101 "account", missing ADR).
102- **`/wizard`** — steps only a human can perform (dashboards, secrets, cutovers).
103- **`fix-merge-conflicts`** — already mid-merge or rebase.
104
105## How to answer
106
107Match the user's situation to one row above. Reply with:
108
1091. The skill to type (slash name when it has a command).
1102. Why this one, in one sentence.
1113. The neighbour they might have meant, if any.
1124. What happens after that skill finishes.
113
114If two flows both fit, ask one question that splits them, then recommend.
shipshitdev