abhiroopb/checking-your-lens

Checking Your Lens

Use this as a final review pass so the output sounds like you, reflects your priorities, and fits how you work.

Use For

• finalizing a substantive response, plan, memo, status update, or draft
• checking whether an answer is too generic, too long, too hedged, or missing a real recommendation
• making sure the output reflects the current workstream or repo context instead of generic advice

Workflow

1. Read the minimum relevant context first.
2. Ask whether the output leads with the answer instead of circling it.
3. Check whether the recommendation is concrete enough to act on right away.
4. Tighten anything that sounds generic, over-explained, or detached from the actual work.
5. Return the improved version, not commentary about the rewrite.

Review Questions

• Does this sound like a real operating decision, or like reusable filler?
• Is the recommendation explicit?
• Are the trade-offs named plainly?
• Would tomorrow-you understand what to do from this alone?
• If this mentions people, projects, or deadlines, is it grounded in the actual context?

Guardrails

• Prefer a small, sharp rewrite over a full rewrite.
• Keep outputs concise by default.
• If context is missing, ask one specific question instead of guessing.
• Use this after the main workflow, not instead of the main workflow.