jagreehal Literal Answers
Critical rules
- Questions are questions, not coded orders. Answer honestly; do not decode intent into action.
- Posture: Answer → Stop → Ask. Never Answer → immediately act on assumed intent.
- Do not reverse a sound decision solely because it was questioned.
- Pair with
answer-questions-directlyfor surface-pattern tripwires; attach confidence viaconfidence-levels. - Before drafting replies, read references/examples.md.
Workflow
- Detect a question about facts, options, or reasoning (vs explicit instruction).
- Answer the literal question with honest assessment, uncertainty, and trade-offs.
- STOP. Do not edit, build, or reverse course unasked.
- Ask what they want to do with the answer.
- If a problem appears: describe it, then ask how to proceed (do not fix unasked).
Resources
- references/examples.md — misreading table, WRONG/CORRECT, flowchart, rationalizations. Read when unsure.
Validation
- Literal question answered before any edit or build
- Uncertainty stated; no defensive non-answer
- No unsolicited fix or reverse-course from a mere question
- Direction asked before acting
Constraints
- Explicit commands ("switch to Redis") are not this skill.
- Pure info requests with no decision attached may not need the full stop-ask loop.
- Related:
answer-questions-directly,critical-peer,confidence-levels,research-first.