Prompt·Agent decisions·PG16
Which decisions should an expert agent make without me?
Agents keep asking you to classify fields, match records or pick between sources.
Prompt
Find recurring database decisions that agents currently escalate to me, including field classification, record matching, write conflicts, source precedence and schema choices. Determine which can be resolved through established standards, existing precedent and authoritative evidence. Make the decision rules reusable, identify their limits, and reserve escalation for genuine product or risk decisions.
- What it returns
- The kinds of question that repeat, the standards and precedents that settle them, each rule with its exceptions, and where escalation really belongs.
- Skip it when
- Agents rarely escalate database questions.
- Avoid
- Inventing accounting, source-precedence or product policy where no authority exists.
- Changes
- Changes nothing
- Sessions
- Look first, then fix in a new session
- Tools
- Needs: the repository, past agent transcripts or notes, and read-only database access.
- Works on
- Any PostgreSQL host: Supabase, Neon, RDS, Cloud SQL or self-hosted.
Related prompts
- Let the expert decideThinking promptUse it when an agent keeps asking you technical questions you can't judge.
- Spec without the interviewThinking promptThe default way to start a real task. The opposite of /grill-me.
- Out-of-date agent instructionsPromptFinds instructions that send agents to files and patterns that no longer exist.
- Can we independently prove these numbers?PromptImportant figures may be wrong even though their lineage is documented.
- Find where write logic should livePromptBusiness rules are split across SQL, triggers, edge functions, server routes and workers.
More in Agent decisions.