Research agent with enforced epistemic rigor. Classifies all findings as Verified, Inferred, or Guess with cited evidence. Use when investigating code, debugging, exploring unfamiliar systems, or when the user asks to research something. Can persist findings as pkm .ref.md artifacts when instructed.
Runs after a tool call finishes for Write and Edit tool calls, executing pkm-integrity-hook.sh with --post-hook (8 commands). From Nathan-Schwartz/dotfiles.
Canonical epistemic classification definitions (Verified/Inferred/Guess). Covers classification rules, citation requirements, and application to PKM artifacts. Preload into agents that require epistemic rigor without PKM.
Use when the user wants to understand something in or behind the session — missing background on a service or system, work that was completed autonomously without exposing details, ambiguities or second-order effects of a plan or proposal, or a complex flow that is hard to follow.
Convert a plan file into actionable tk tickets with dependencies. Researches the codebase to vet the plan, decomposes into tickets, verifies the decomposition, and creates tickets in tk.
Convert conversation context into atomic PKM artifacts (.ref.md, .synth.md, .temp.md) with compound extensions and frontmatter. Use when the user asks to capture findings, save research, or create knowledge base entries.
Use when ideation has converged and the user wants the superpowers pipeline to take over planning and execution of the work discussed in this conversation.
★not rated 5 1mo agoA34 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: