haku

Plugin haku from marketplace vibekit in shrwnsan/vibekit-claude-plugins. Commands read from the repo's manifest — today.

Skills (52)

• demo-prep

  Use when the user is preparing for a demo — exec review, customer pitch, board update, investor meeting, sales call, or all-hands. Trigger phrases include "I'm demoing X tomorrow", "help me prep for the review", "what could go wrong in this demo?". Especially valuable for AI-feature demos, where pro

• exec-readout-prep

  Use when the user needs a decision from executives and is preparing the meeting or memo that gets it — QBRs, roadmap reviews, headcount asks, investment pitches. Trigger phrases include "prep my exec readout", "I'm presenting to leadership", "I need sign-off from the VP", "help me get this decision

• product-pulse

  Use to produce a single-page dated pulse report on product health — usage metrics, AI-feature signals (hallucination, refusal, eval drift), counter-metrics, follow-ups. Trigger phrases include "run a pulse on [area]", "give me a product health snapshot", "weekly product pulse", "what does the data s

• pulse-synthesize

  Use to derive trends, anomalies, inflection points, and regime shifts across accumulated product-pulse reports. Trigger phrases include "what's been the pattern across pulses this quarter", "synthesize my product pulses for [area] over the last 8 weeks", "before my exec readout, what does the data s

• read-the-room

  Use for retrospective subtext reads on meetings, reviews, Slack threads, or 1:1s. Trigger phrases include "what was actually going on in that meeting", "I think X is bothered but I can't tell why", "did anyone push back on my idea or were they just being polite", "read this Slack thread for me", "is

• engineering-health

  Use when an EM wants to assess engineering systems and processes—not team morale (that's team-diagnosis): measurement, developer experience, onboarding friction, and platform investment. Trigger phrases include "is my team actually productive", "I want to understand developer experience on my team",

• glue-audit

  Use when the user wants to systematically identify, categorize, and quantify "glue work" on themselves or their team. Trigger phrases include "what glue work am I doing", "audit my glue work", "what non-promotable work is our team doing", "catalog our glue tasks", "how much time do we spend on glue"

• impact-audit

  Use when a PM or team stress-tests whether work connects to business outcomes—"are we even pointed at the right thing?"—before strategy-doc or prioritization-frameworks. Trigger phrases include "are we doing the right work?", "I'm worried my team isn't driving real impact", "help me check if my team

• leadership-os

  Use when the user is navigating people/leadership situations as a PM — managing up to executives, managing down to a team, cross-functional conflict, 1:1s, performance reviews, post-mortems, incident response, roadmap negotiation, or stakeholder communication. Trigger when the question is about *how

• manage-glue-workers

  Use when managing engineers who gravitate toward glue work (onboarding, documentation, unblocking) and need burnout protection, visibility, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how do I protect my glue person", "glu

• metrics-design

  Use when the user is designing the metric tree for a feature (especially an AI feature)—north star, leading and lagging indicators, quality metrics, counter-metrics. Trigger phrases include "what should we measure for…", "how do we know if this is working?", "I need to define success for…". Distinct

• patterns-watch

  Use to surface unsolicited patterns across stakeholder reflections, wins log, and self-reflect entries. Trigger phrases include "what patterns am I missing", "anything notable across my files", "scan my reflections for things I should know", "weekly cross-cutting check". Distinct from `stakeholder-s

• premortem

  Use for pre-mortem analysis of decisions, projects, or initiatives—solo or facilitated with a team before a launch or strategic commitment. Trigger when the user says "what could go wrong", "risk assessment", "pre-mortem this", "let's run a pre-mortem", or when evaluating risks for a plan. Three-cat

• prioritization-frameworks

  Use when the user is prioritizing a backlog, building a roadmap, cutting scope, or arguing about what to build next. Trigger phrases include "what should we build first?", "help me cut this list", "I need to defend my roadmap", "should we do X or Y?". Surfaces the right framework—RICE, ICE, WSJF, Mo

• tech-strategy-writer

  Use when a senior IC (staff/principal, architect, tech lead) writes a technical strategy or direction doc. Trigger phrases include "write a tech strategy for [domain]", "I need a technical direction doc", "our platform needs a north star doc", "help me write the tech vision for [area]". Distinct fro

• career-retro

  Use for a quarterly/annual career retrospective across the haku memory; cited growth deltas vs. last retro, written to self/retros/. Trigger phrases include "run my career retro", "where am I in my career", "annual self-assessment", "how have I grown this year", "it's review season, take stock of ev

• coaching-mode

  Use when coaching a report, peer, or mentee through a problem rather than solving it for them. Trigger phrases include "coach me through how to talk to [report]", "I want to help [name] figure out X without telling them what to do", "let me practice a coaching conversation", "GROW conversation about

• commitments

  Use to track promises in ~/haku-work-reflections/commitments.md and keep them from going stale. Trigger phrases include "what have I committed to", "add a commitment", "I promised X by Friday", "am I overcommitted", "help me say no to this", "I need to renegotiate a deadline". Renegotiate early; pre

• feedback-frameworks

  Use when the user is preparing to give feedback to a teammate, direct report, peer, or stakeholder — performance reviews, 1:1 prep, post-incident conversations, peer reviews, 360s, written async feedback, or any moment they're drafting "how do I tell them that…". Apply the COIN structure to compose

• hiring-craft

  Use when designing interview loops, writing interview questions or rubrics, calibrating panel feedback, running hiring debriefs, or making a hire/no-hire call. Trigger phrases include "design an interview loop for [role]", "write interview questions for [signal]", "help me run the debrief", "should

• influence-without-authority

  Use when moving outcomes without authority. Trigger phrases include "how do I get [team] to do X without going to their manager", "I need to convince [person] to support this", "I have to push back on [exec] without burning the relationship", "build the coalition", "I'm a TPM/staff eng/IC and I need

• one-on-one-prep

  Use when preparing for a 1:1 — manager with a report, IC with their manager, or peer sync. Trigger phrases include "I have a 1:1 with X tomorrow", "help me prep for my 1:1", "what should I bring up in my next 1:1?". Builds a relationship-matched agenda; if the other person is a registered stakeholde

• performance-management

  Use when dealing with underperformance, considering a PIP, navigating a brilliant-jerk pattern, documenting concerns, or preparing a hard performance conversation. Trigger phrases include "I have a report who's underperforming", "should I PIP X", "I need to document this", "how do I have the hard co

• promo-case-glue

  Use when a glue-heavy engineer needs a promo packet framing it as technical leadership. Trigger phrases include "promotion case for glue work", "I do a lot of glue work how do I get promoted", "frame my non-code work for promotion", "my manager says I need more technical accomplishments", "I'm a glu

• report-career-architect

  Use when designing or revisiting a 12–18 month growth plan for a direct report. Trigger phrases include "build a growth plan for [report]", "what should [name]'s next year look like", "I want to architect [report]'s path to senior", "I'm prepping for promo cycle and [report] needs a plan", "let's th

• report-promo-case

  Use when building a promotion case for a direct report — internal promo packet, panel write-up, or calibration-committee one-pager. Trigger phrases include "build the promo case for [report]", "I'm submitting [name] for staff this cycle", "draft [report]'s promo packet", "help me make the case for [

• self-reflect

  Use when the user wants to reflect on themselves as a leader — behavior under pressure, communication, time and energy, fulfillment, advocating for themselves. Trigger phrases include "let me reflect on myself", "self-check", "I want to think about how I've been leading lately", "self-reflection". L

• visibility-sponsorship

  Use when work outpaces its visibility; build sponsor awareness before promo/calibration. Trigger phrases include "nobody knows what I do", "how do I get more visibility", "I need a sponsor", "my work speaks for itself but nobody's listening", "I was passed over because people don't know me", "how do

• wins-curate

  Use to turn the wins log into an audience-specific artifact — promo packet, behavioral interview stories (STAR), perf-review self-eval, salary case, or year-in-review. Trigger phrases include "build my promo packet", "I have a behavioral interview Tuesday", "draft my self-eval for the perf review",

• wins-due

  Use for a low-pressure nudge on whether anything from the recent week is worth logging. Weekly Desktop scheduled task friendly (never cloud routines); probes by category. Trigger phrases include "what should I log this week", "is anything missing from my wins doc", "did I do anything notable this we

• stakeholder-due

  Use when the user wants to know which stakeholder reflections are overdue — "what's due", "who haven't I thought about lately", "what's on my plate this week for stakeholder reflection", "stakeholder check-in", Monday-morning planning. Scans `~/haku-work-reflections/`, computes overdue question × st

• stakeholder-manage

  Use when changing a registered stakeholder — list, edit role/background, re-categorize, rename, archive, or delete. Triggers include "list my stakeholders", "show all my reports", "Jill is my manager now", "move Jill to managing-up", "Draymond left the company", "archive [name]", "Jill changed her n

• stakeholder-reflect

  Use when reflecting on a registered stakeholder — manager, peer, report, or team — capturing insight to a durable file. Triggers include "let me reflect on John", "I want to think through my 1:1 with Jill", "log my thoughts on the Client Delivery ABC team", "reflect on [name]". Picks 1–3 questions b

• stakeholder-register

  Use when the user wants to register a new stakeholder for ongoing reflection — manager, peer, direct report, or team. Triggers include "add a new stakeholder", "register Jill in managing-across", "I just got a new manager", "I'm now leading the X team", "let me set up reflection for [name]". Creates

• stakeholder-synthesize

  Use when deriving insight across stakeholder reflections — patterns, trends, contradictions, blind spots. Triggers: "how is my managing-up overall", "summarize what I've learned about Jill this quarter", "before my performance review, what do I know about my reports", "what patterns do I see across

• psychological-safety

  Use when a team lacks psychological safety — members don't speak up, withhold concerns, or fear making mistakes. Triggers include "build psychological safety", "team is afraid to speak up", "create safe environment", "people are withholding their opinions", "no one challenges decisions", "fear-based

• team-charter

  Use when forming a new team, resetting after a reorg, or when a team's goals/roles/norms are unclear and causing friction. Triggers include "create a team charter", "align our team on goals roles norms", "reset the team operating model", "new team kickoff", "team alignment workshop". Facilitates exp

• team-check-in

  Use when a team must revisit their Goals/Roles/Norms foundation to surface drift and realign. Triggers include "team check-in", "are we still aligned", "team retro on our operating model", "review our team charter", "3X3 check-in". Structured conversation (30–90 min): still committed to our goals/ro

• team-close-gap

  Use when a team has identified a gap between stated goals/roles/norms and actual behavior and needs small-step action plans to close it. Triggers include "close the saying-doing gap", "how do we actually change our behavior", "action plan for team norm change", "small steps to improve team work", "b

• team-diagnosis

  Use when the user wants a structured read on their team's *health*, beyond individual morale. Triggers: "how is my team doing", "I want a team health check", "diagnose my team", "before my skip-level update, what should I flag", "is something off with the team that I'm missing". Reads stakeholder-re

• team-lifecycle

  Use when a team is transitioning — forming, storming, norming, performing, adjourning — or resetting after a reorg, new member, or a stuck team. Triggers: "our team is changing", "new team member joining", "team reorg transition", "how do we reset our team", "team dissolving", "adjourning a team". T

• team-style-inventory

  Use when a team wants to understand their collective working style preferences — communication, decisions, conflict, meetings, information sharing. Triggers: "team work style assessment", "how does our team prefer to work together", "team style inventory", "understand our team dynamics", "communicat

• team-workspace

  Set up or work with a git-backed team workspace for co-owned artifacts — charters, strategy docs, decision records — separate from private reflections. Triggers: "share our team charter with the team", "set up a shared haku workspace", "put our strategy doc in the team repo", "how do teams use haku

• workload-equity

  Use when the user wants to analyze whether non-promotable (glue) work is fairly distributed across their team, with attention to demographic patterns. Triggers: "is our glue work fair", "who does the non-promotable work on our team", "audit workload distribution", "are women doing more glue work", "

• capture

  Use to log something from the current conversation into the user's haku memory — a decision just made, a win that surfaced, a stakeholder observation, a self-insight. Triggers: "log this", "capture this", "save that decision", "remember this", or a substantive conversation just concluded. Distinct f

• decision-log

  Use when the user makes or revisits a meaningful product, technical, or organizational decision and wants it captured ADR-style. Triggers: "we decided to…", "let's go with X over Y", "write up the call we made on…", or reconstructing a past decision. Especially AI-product decisions — model choice, e

• doctor

  Use to health-check the user's haku memory directory — validate file layout, catch problems before they cost data. Triggers: "run haku doctor", "check my reflection files", "is my data okay", "back up my reflections", "I'm moving to a new machine". Validates ~/haku-work-reflections/ (or $HAKU_WORK_R

• start

  Use when the user is new to haku and doesn't know where to begin, or wants a tour of what's available. Triggers: "where do I start", "how do I use this", "what can you do", "what should I run first", "I just installed this", "what is haku". Entry point for new users; branches into first-time setup o

• strategy-doc

  Use to create or update a product/area strategy document — target problem, approach, personas, 3-5 SMART metrics, 2-4 strategic tracks, explicit not-working-on section. Triggers: "draft a strategy doc for [area]", "I need a strategy.md for the platform team", "interview me about my strategy". Lives

• user-profile

  Use to create or update the user's anchor profile — one private file (~/haku-work-reflections/profile.md) capturing who they are and the context other skills need. Read automatically by other skills when present, so the user doesn't re-explain themselves every session. Triggers: "set up my profile",

• weekly

  Use for the user's weekly review ritual — one ~15-minute guided session wrapping the haku maintenance loop. Triggers: "run my weekly review", "Friday review", "weekly check-in", "/haku:weekly", "catch up on the week". Composes wins-due, stakeholder-due, stakeholder-reflect, patterns-watch into four

• wins-log

  Use when the user wants to capture a "win at work" — something shipped, judgment exercised, someone mentored, a fire put out. Triggers: "I just shipped X", "log this win", "add to my brag doc", "I had a good week". Captures structured entries (situation, action, impact, evidence) to ~/haku-work-refl

Subagents (5)

• the-red-teamer

  Use proactively before launch and during maintenance of an AI feature to find failure modes the user hasn't thought of. Trigger when reviewing prompts, agent tool wiring, or LLM-facing endpoints for prompt injection, data exfiltration, jailbreaks, or out-of-distribution failures.

• the-reducer

  Use proactively when a vague or ambiguous problem hasn't been framed and the proposed fix is "add AI" — the whether-to-use-AI call. Triggers: "we should add AI to…", "users are complaining about…", any pitch where the problem is fuzzier than the solution. Hands off once the whether is settled — prob

• the-retro-facilitator

  Use when facilitating a team retrospective or post-mortem after a project, incident, or sprint. Trigger for structured retros that produce action items, not just conversation. Distinct from the-incident-responder (real-time incident management) and the-postmortem-facilitator (infrastructure postmort

• the-rfc-reviewer

  Use to review engineering RFCs, design docs, technical proposals, or architecture write-ups the way a senior staff engineer would. Trigger when the user shares a doc and asks for review, an EM wants a second opinion before approving a proposal, or the user wants structured critique before publishing

• the-spec-writer

  Use when the user has a validated problem and needs to turn it into a written product spec or PRD. Trigger phrases include "draft a PRD for…", "write a spec on…", "I need a one-pager on…", or naturally after `the-reducer` has produced a Problem Definition. Also use when reviewing an existing spec fo

Hooks (1)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/bin/ship-review-hook.mjs"

Similar plugins