Route a coding agent's questions by the kind of decision, and log every answer
by PaperChaseWebb
A team building a business system with coding agents has the agent stop and ask, with options, when a task runs past its spec. Questions about product direction, rule exceptions or loosening a check go to a person; routine design calls are answered from written rules and earlier rulings. In one week, 762 questions, 59 answered by the owner.
- Price
- Free
- Difficulty
- Intermediate
- Setup
- 30 min
- Format
- .md file
route-a-coding-agent-s-questions-by-the-kind-of-decision-and-log-every-answer.md · 3 KB · direct download, no signup
What you end up with
The figures are the team's own.
What you get
- A plain-language summary of the workflow
- A fill-in prompt template
- What to watch out for
- A link to the original source
Who it is for
Builders who already use AI agents and want a proven workflow they can copy into their own project.
Works with
Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free with the agent plan you already use.
Time to result: One working session
How it works
Tell the agent to stop and ask with two or three options when the task
Tell the agent to stop and ask with two or three options when the task goes past the spec.
Expected: Done before you move to the next step.
Sort questions into: product direction, rule exception, loosening a ch
Sort questions into: product direction, rule exception, loosening a check, routine design.
Expected: Done before you move to the next step.
Send the first three to a person; answer routine ones from your rules
Send the first three to a person; answer routine ones from your rules and past rulings.
Expected: Done before you move to the next step.
Record every answer with who gave it and point later questions to it
Record every answer with who gave it and point later questions to it.
Expected: Done before you move to the next step.
Treat 'unsure which kind' as a person question
Treat 'unsure which kind' as a person question.
Expected: Done before you move to the next step.
Sample prompt from the pack
Apply this workflow to [your project]: 1. Tell the agent to stop and ask with two or three options when the task goes past the spec. 2. Sort questions into: product direction, rule exception, loosening a check, routine design. 3. Send the first three to a person; answer routine ones from your rules and past rulings. 4. Record every answer with who gave it and point later questions to it. 5. Treat 'unsure which kind' as a person question. Stop and ask me before anything irreversible: deploys, payments, sends or deletes.
Adapted by PaperChaseWebb. Not the original author's prompt.
Free preview of the file
# Route a coding agent's questions by the kind of decision, and log every answer PaperChase agent use case (free feed entry), version 1.0. Source: [u/DynoKore](https://www.reddit.com/r/AI_Agents/comments/1xiiris/we_route_our_coding_agents_questions_by_type_of/), 2026-10-28. ## What they did Every answer is recorded with who gave it, so later questions can cite earlier decisions instead of being asked again. In the week to 26 October 2026 the agents raised 762 design questions; of the 737 answered, the owner answered 59. The rule they stress: 'not sure which route' counts as a reason to ask a person, otherwise the agent ends up judging the risk itself. ## Worth knowing The figures are the team's own. The idea scales down: even a solo builder can keep a decision log the agent reads before asking. A related thread asks which early question saved the most rework; one example was whether a support bot needs account data or just docs.
Worth knowing
- The figures are the team's own. The idea scales down: even a solo builder can keep a decision log the agent reads before asking. A related thread asks which early question saved the most rework; one example was whether a support bot needs account data or just docs.
- Figures are as reported by the original author and were not re-measured by us.
Questions
Where does this come from?
A public post credited to u/DynoKore. Source: https://www.reddit.com/r/AI_Agents/comments/1xiiris/we_route_our_coding_agents_questions_by_type_of/
Is it free?
Yes. Feed entries are free to read and download.
Details
Version 1.0 · Updated Oct 29, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms
Related
AGENTS.md, CLAUDE.md and Cursor rules starter files
Six fill-in instruction files for coding agents (base, Next.js plus Supabase, FastAPI, browser game, CLAUDE.md pointer, scoped Cursor rules), an Approvals section that makes the agent stop and wait for your yes, a table of what Grok Bot, Claude Code, Codex, Hermes and Cursor each read, a read-only checker for your rule files and 9 prompts to write, trim and test your own.
Ask-first rules for AI agents: hard nos, approval cards and a test set
Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.