From kmgraph
Consults the knowledge graph for prior art before making recommendations during brainstorming. Presents relevant ADRs, lessons-learned, and failed approaches.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kmgraph:brainstorm-recallThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** Ensure the knowledge graph is consulted before any recommendation is made. Fires before `adr-guide` on the same trigger surface.
Purpose: Ensure the knowledge graph is consulted before any recommendation is made. Fires before adr-guide on the same trigger surface.
Trigger Keywords:
superpowers:brainstorming is invoked via Skill toolPrecedence: This skill fires BEFORE adr-guide. If both trigger, run recall first, then allow adr-guide to proceed.
Enforcement note (ENH-015): "Fires before" is not just a prose claim — it is enforced by the
pre-skill-rules-inject.shHARD BLOCK added in Task 6b. The hook injects the Brainstorm Recall block into context before the skill executes, making the recall step mandatory regardless of which skills auto-trigger. Seeknowledge/enhancements/ENH-015/ENH-015-specification.md§"Existing Skill Conflicts Resolved" for the full precedence rationale. The skill trigger overlap withadr-guideis intentional — ENH-015 documents why separate skills are correct (different lifecycle phases) and why merging produces unreliable auto-invocation.
Behavior:
Extract the topic from the user's question or the brainstorming context (1–5 words).
Run recall before answering: Invoke the kmgraph:recall skill (via Skill tool) with the extracted topic as input.
Present prior art under a "Prior Art" heading before your recommendation:
Then proceed with the recommendation or brainstorming, informed by the recall results.
Do not skip recall if the topic seems simple — recall takes seconds and prevents proposing already-rejected solutions.
ADR/ENH number pre-allocation (I-E): Before dispatching background fast-agents, brainstorm-recall must pre-allocate ADR and ENH numbers by reading current highest numbers from knowledge/decisions/ and knowledge/enhancements/. Pass resolved numbers in agent payload to prevent concurrent agents from claiming the same number.
Integration:
superpowers:brainstorming — does not replace itadr-guide if a decision crystallizes from the brainstormBackground agent dispatch (non-blocking):
After presenting recall results and proceeding with the brainstorm:
If the brainstorm surfaces a new architectural decision: dispatch a background fast-agent to draft an ADR:
Agent({subagent_type: "kmgraph:create-adr-agent", run_in_background: true, prompt: "Draft ADR for: [decision]"})
If the brainstorm surfaces a new enhancement or feature idea: dispatch a background fast-agent:
Agent({subagent_type: "kmgraph:knowledge-extractor", run_in_background: true, prompt: "Capture ENH for: [idea]"})
When background agents complete, present a review-or-save prompt:
"ADR/ENH draft complete. Files at
knowledge/decisions/ADR-NNN.md/knowledge/enhancements/ENH-NNN/. Review before saving, or save now?"
Any Opus feedback or unresolved action items → write to the Open Questions section of the relevant ADR/ENH (never directly to session summary).
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub technomensch/knowledge-graph --plugin kmgraph