Consult
- 79 installs
- 1 repo stars
- Updated August 3, 2026
- davidlee/doctrine
Prompts the agent to stop and consult the user when hitting an unanticipated obstacle, competing tradeoffs, or emergent complexity mid-task.
About
Forces a pause to present context, options, and tradeoffs to the user before adapting scope, adding a dependency, or taking a shortcut. A developer uses it the moment a task hits an impactful decision that shouldn't be made unilaterally.
- Lists obstacle types that require stopping immediately
- Routes deferrable work to backlog new instead of a decision
Consult by the numbers
- 79 all-time installs (skills.sh)
- Ranked #1,455 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davidlee/doctrine --skill consultAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 79 |
|---|---|
| repo stars | ★ 1 |
| Last updated | August 3, 2026 |
| Repository | davidlee/doctrine ↗ |
What it does
Prompts the agent to stop and consult the user when hitting an unanticipated obstacle, competing tradeoffs, or emergent complexity mid-task.
Files
Consult
The user has strong feelings about architecture, plan adherence, and especially about agents making impactful decisions or concessions without consultation.
DO NOT make them alone.
If you encounter an unanticipated obstacle, YOU MUST consider stopping to discuss it. If the obstacle:
- requires adaptations that could alter planned functionality
- presents multiple solutions with different tradeoffs
- requires substantial research, debugging, or diverts you from the task
- suggests introducing new imports or coupling vectors
- risks policy violations or doctrinal ambiguity (i.e. heresy — see
/canon) - tempts a shortcut or omission
YOU MUST STOP IMMEDIATELY.
Present the situation with context. Summarise:
- the relevant task code, plan,
design.md, or governing canon - what you are trying to do
- the nature of the obstacle
- relevant discoveries
- options and/or hypotheses
- any obvious tradeoffs
Then ask for guidance before proceeding.
If the obstacle is really a piece of latent work to defer rather than a decision needing the user now — a follow-up, a newly-spotted risk, a chore — then capture it with backlog new so it is not lost to the conversation, and say so. Is it work, knowledge, or a decision? See the boundary in using-doctrine.md.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k