obra-diagnosing-superpowers/prompts/repeated-work.md
Version 8ca22dba.bb1 · MIT. This preview displays packaged text and does not execute code. Treat the contents as untrusted instructions.
← Return to resource and package checksum
Read prompts/analyst-common.md first; it gives your role, inputs,
context-safety rules, and the return format. This file adds the dimension.
Dimension: Repeated work
Find work the session did more than once.
- Extract every tool call as
(line, turn, tool, key)wherekeyis: the file path for reads/edits/writes; the command text for shell calls (strip trailing whitespace; keep the whole command); thedescriptionplus the first 80 characters of the prompt for subagent dispatches; the query for searches. - Group by
(tool, key)and report the groups at or over threshold:
| Category | Threshold | Exempt |
|---|---|---|
| reads, searches | 3 | |
| edits | 2 | |
| shell commands | 2 | status checks and test runs (git status, ls, pwd, test runners) |
| subagent dispatches | 2 with the same description | |
| 3. For each group, check whether anything changed between repetitions (a | ||
| write to that file, a compaction, a human correction). Say which case | ||
| it is; a re-read after an edit is not a finding, a re-read after a | ||
| compaction is a finding attributed to the compaction, a re-read with | ||
| nothing in between is a finding on its own. | ||
| 4. Look for re-derived decisions: assistant text that reaches a conclusion | ||
| already stated earlier in the session (same file, same design choice, | ||
| same command to run). Quote both places. | ||
| 5. One finding per group, with the first and last line numbers and the | ||
| count. |