Provide the user with a refresher of existing chat turns. Useful when the user wants to understand where we stand in the conversation.
Scanned 9/22/2026
Install to Claude Code
npx -y skills add dotlas/skills --skill where-were-we --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Where Were We?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dotlas-where-were-we)More formats (shields.io, HTML) on the badges page.
---
name: where-were-we
description: Provide the user with a refresher of existing chat turns. Useful when the user wants to understand where we stand in the conversation.
---
Provide the user with an ELI5, first-principles recap of the recent conversation turns.
Assume they are returning after a while to resume work on this task.
Help them clearly understand:
* Where things currently stand.
* Which decisions have been locked.
* Which decisions remain open, along with the available options for each.
* What remains in the planning stage (if planning is still ongoing).
Go back as many turns as necessary to provide a complete picture of the conversation
context. Do not waste time going too far back unnecessarily—use locked decisions and
implementation milestones to short-circuit the context and highlight what needs the
user’s attention right now.
Assume the user may not remember past decisions made, but will recall checkpoints for
implementation work that has already been completed and shipped.
Do not make the assumption that even a message that exists in the prior conversational
turn was read by the user either.
For completeness, include any deferrals present in the current or previous plans in the
brief too.
Prioritize scannability to minimize cognitive load, ensuring the brief is easy to skim
without omitting important details in its content.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!