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/skill-timeline.md

Read prompts/analyst-common.md first; it gives your role, inputs, context-safety rules, and the return format. This file adds the dimension.

Dimension: Skill timeline

Build the per-human-turn record of skill and plugin use, then look for gaps.

  1. List the human prompts with line numbers and timestamps.
  2. Using the skill-invocation and attribution meanings established in the case file, list every explicit invocation, active-skill attribution, or read of a file named SKILL.md. Record the line, the skill name, and the human turn it happened in.
  3. List every non-superpowers plugin, skill, agent type, MCP server, or hook used. Use only the evidenced tool, attribution, agent-dispatch, MCP, and hook meanings recorded in the case file; identify values associated with something other than superpowers.
  4. For each human turn, compare the request text against the trigger descriptions of the superpowers skills installed (read <install root>/skills/*/SKILL.md frontmatter description lines; the install root is in the case file). Report as findings:
    • a skill invoked, with the request that preceded it (one finding per invocation is fine when there are few; group by skill when many);
    • a turn whose request matches a skill's trigger description with no invocation in that turn (state which description matched and quote the request);
    • a skill invoked one or more turns after the matching request (late);
    • each non-superpowers plugin/skill/tool used, with where.

Do not say whether a missed or late trigger was wrong. Report the match and the absence; the reader decides.