Interview a person about how they want an agent to write to them, then generate their Response Standard profile. Twenty questions across five sets, covering answer shape, depth, structure, evidence, tone, and forbidden constructs. Use when someone wants their own response standard, wants to change an existing one, or asks how to make an agent write the way they think. Trigger on: /build-response-standard, "build my response standard", "how should you talk to me", "make your own standard for me".
1 skill
Interactively facilitate writing a short Architecture Decision Record (ADR). Use when the user wants to make and document an upfront technical or architecture decision — capturing the problem, constraints, 2-3 realistic options with tradeoffs, the chosen decision and why, risks/consequences consciously accepted, and a concrete revisit trigger. Trigger on: /create-adr, "create ADR", "write an ADR", "architecture decision record", "document this decision", "let's decide how to build X".
1 skill
Second brain for code changes, so the user owns a change instead of just having it merged — they can explain the problem, defend the solution, name the alternatives, and answer a skeptical senior engineer without the agent present. Two modes. Change mode: after-action review of work just done (read the real diff, explain in three layers, Mermaid diagrams, write the debrief doc, then flip roles and interview the user). Comment mode: work through PR review feedback until the claim is understood, its risk is triaged, and a decision is made together. Output always goes to the separate debrief repo, never into the project. Trigger on: /debrief, "debrief this", "after-action review", "walk me through what we just did", "quiz me on this change", "help me own this PR", "I need to defend this in review", "what is this reviewer actually saying", "triage these comments", "work through this PR feedback".
1 skill
Use when the user invokes /dg for an entertaining adversarial code review with Dinesh vs Gilfoyle banter from Silicon Valley
1 skill
Use when the user says "get to the point", "tighten this up", "make this scannable", "cut this down", or wants a Slack message, email, doc, PR body, or ticket rewritten to the "Get to the point" communication standard.
1 command
any input (code, docs, papers, images) → knowledge graph → clustered communities → HTML + JSON + audit report
1 skill