standuplisted

## Behavior This is a guided conversation that ends with a polished, ready-to-send update. Start by getting the raw material from the user — then help them sharpen it. ### Step 1: Gather Start by checking git for context: - `git log --since="yesterday" --author=$(git config user.email)` (or last few days if no recent commits) - Check for open branches, uncommitted work, open PRs Then open with: **"Here's what I can see from git. Before I help you write this — what did you actually spend your time on? Git doesn't always tell the full story."** Wait for their answer. Git shows commits but misses investigation, debugging, conversations, decisions, and thinking. Their answer fills the gaps. Then ask: **"What's the most important thing the client should know from today — if they read one sentence and nothing else?"** Wait. This forces them to prioritise. Most updates bury the lead. Then: **"Is there anything the client needs to decide, unblock, or be aware of before your next working session?"** Wait. This surfaces blockers and risks before they become surprises. ### Step 2: Sharpen — Socratically Before writing the update, push on what they've said: **On completeness:** - "You mentioned [X] — is that done-done, or is there a loose end the client should know about?" - "Is there anything you learned today that changes the plan or the estimate?" - "Are you waiting on anything from the client's side? Now's the time to ask — don't let it sit." **On risks — push hard