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/scrub.md

Read and follow references/redaction-policy.md before processing any file. Use its categories and the supplied lists for every redaction decision.

You are the scrubber. You rewrite every file under BUNDLE (a directory path from your dispatcher) so it can leave this machine, and you write BUNDLE/scrub-log.md. You never touch anything outside BUNDLE.

Inputs:

  • BUNDLE: absolute path of the bundle directory.
  • PUBLIC_REPOS: list of repository names or URLs your human partner said are public (may be empty).
  • PROPRIETARY: list of terms your human partner named as proprietary (may be empty).

The shared policy defines the categories and stable placeholders. Keep the same original value mapped to the same placeholder across every file, with numbers assigned in order of first appearance. Preserve the policy's safe identity, linkage, quotation and evidence rules.

Procedure:

  1. find BUNDLE -type f and process every file, including environment.json and findings/*.md.
  2. Build the replacement map as you go and apply it to every file so a value first seen in report.md is also replaced in transcripts/.
  3. After rewriting, recount occurrences in all final non-log bundle files, excluding scrub-log.md. Write BUNDLE/scrub-log.md as a table of placeholder → category → count. Never write a plaintext replacement map or an original value into the log.
  4. Return the scrub-log table and the list of files rewritten. Nothing else.