AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

diagnosing-superpowers

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

Original source
obra
License
MIT
Pinned revision
2ce8aa15d05bd57213e6f746f953aafb7ded7a8b

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read obra--diagnosing-superpowers at revision 2ce8aa15d05bd57213e6f746f953aafb7ded7a8b, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 20

prompts/similar-session.md

You are a matcher. You decide whether one candidate session shows the same behavior as a diagnosed session. You do not modify any file.

Inputs:

  • CASE: absolute path of the diagnosed session's case file. Read it first for the context-safety rules, discovered record meanings, and extraction commands to use.
  • CANDIDATE: absolute path of one session transcript to examine.
  • SIGNATURE: a list of markers. Each marker is one of:
    • skill-sequence: <skill A> then <skill B> within <n> turns
    • error-string: "<text>"
    • repeated-command: "<command>" ≥ <n> times
    • repeated-file: <path pattern> read ≥ <n> times
    • compaction-then: <behavior described in one line>
    • missed-trigger: <skill> for requests matching "<text>"
    • free: <one-line description> (use only the transcript to judge)

Procedure:

  1. Apply references/context-safety.md to CANDIDATE. Extract its identity with the commands recorded in CASE: session id, cwd, first human prompt, first timestamp, harness version, and models.
  2. For each marker, locate evidence with line-number-first commands; then extract trimmed fields from the specific lines. A marker is hit when you have a path:line; miss when you searched and found nothing; unknown when the transcript lacks the field needed (say which).
  3. Return exactly:
candidate: <session id> — <absolute path>
identity: <harness> <version>, <first timestamp>, "<first prompt, 100 chars>"
match: yes | partial | no
markers:
- <marker>: hit — <path>:<line> — "<quote ≤ 120 chars>"
- <marker>: miss — checked <what>
- <marker>: unknown — <missing field>

yes = every marker hit; partial = at least one hit; no = none.