consultant-vault

Plugin consultant-vault from marketplace consultant-vault-skills in deanpointblank/consultant-vault-skills. Commands read from the repo's manifest — 18 days ago.

Skills (24)

• daily-worklog

  Close out one working day — Jira worklog rows for the whole day, posted after one confirmation, the day logged in Harvest in the same run, and the month's ledger updated. Use whenever the user says "log my day" (with or without hours), "log my hours for a day", "close out today", "log 8.5 hours for

• daybook

  Capture engineering findings, gotchas, workarounds, and follow-ups into the daily note as the user works. Use whenever the user says "log this", "log it", "note that down", or "add to my daybook", shares a discovery worth remembering, or hits a blocker — even mid-task while working on something else

• decisions

  Record architecture and project decisions in lightweight ADR style. Use whenever the user says "we decided", "log this decision", or "let's go with", when a meeting or working session produces a decision, when a proposed approach is being weighed, or when the user asks "why did we do it that way". A

• gap-stories

  Work out and draft the stories that unblock a Jira ticket that ticket-intake found cannot be built as written, and create approved ones in Jira. Use whenever the user says "fill the gaps for KEY", "what stories do we need to unblock KEY", "bridge the gap", "what tickets are missing for KEY", "draft

• glossary

  Maintain a glossary of client and domain jargon. Use whenever an unfamiliar acronym or internal term appears in any context, the user asks "what does X mean" or says "add X to the glossary", or a meeting or daybook capture contains a term the vault doesn't know yet. Client platforms and logistics do

• granola-sync

  Pull meetings from Granola into the Obsidian vault as structured markdown notes. Use whenever the user says "sync my meetings", "pull granola", or "get today's standup into the vault", references a recent meeting that isn't in the vault yet, or when another task needs meeting content that hasn't bee

• handoff

  Write the end-of-session state of a ticket so the next session, human or agent, can resume cold. Use whenever the user says "write the handoff", "hand this off", "where are we on", "so I can pick it up tomorrow", or ends a working session on a ticket with pull requests, branches, rulings, or gated i

• meeting-trends

  Analyze how meetings evolve over time — recurring topics, persistent blockers, action-item carryover, and how discussion of a subject changes across standups, refinements, demos, and working sessions. Use whenever the user asks about trends or patterns, "how often has X come up", "what keeps blockin

• obsidian-vault

  Foundational conventions for the consultant knowledge vault in Obsidian. ALWAYS consult this skill before reading from or writing to the vault in any way — creating notes, appending to a daily note, capturing a quick thought, searching past notes, setting properties, or building Base views — even wh

• open-questions

  Track questions that need answers from client stakeholders. Use whenever the user says "open question", "need to verify", "need to ask", "not sure if/whether", or wonders about something only a colleague can answer; and whenever they ask "what's still open", "what should I ask X", or are preparing f

• people

  Maintain notes on client stakeholders and what they own. Use whenever a new person is mentioned, the user learns someone's role, team, or ownership, asks "who owns X" or "who do I ask about X", or is preparing for a meeting and wants context on the attendees. Other skills create bare person stubs; u

• reconcile

  Track contradictions between what someone says and what the vault already records. Use whenever a meeting write-up, daybook capture, or document review would add a "conflicts with", "contradicts", or "needs reconciling" callout; when a stated plan or sprint goal contradicts an accepted decision; whe

• record-testing

  Record a Playwright walkthrough that verifies a ticket's acceptance criteria or checks V1-versus-V2 parity, and leave the evidence in the vault: a login-free video, one GIF per criterion, and a test-run note with the step log and a draft comment. Use whenever the user says "record this", "record the

• reference-clipper

  Save external reference material — vendor docs, API references, specs, wiki pages, articles — into the vault as clean markdown. Use whenever the user shares a URL with "clip this", "save this", or "add this to my vault", or references external documentation they'll clearly need again during the enga

• repo-dossier

  Create and maintain a standardized note for each client repository. Use whenever the user clones or first mentions a repo, says "dossier" or "document this repo", asks what a repo does, learns something new about a repo's build, owners, or dependencies, or wants an overview of onboarding progress ac

• runbook-capture

  Write a client-specific workflow into the vault as a runbook the next run can follow. Use whenever the user says "save this as a runbook", "capture that workflow", "make a runbook for", or "write up how we did that", and right after a multi-step sequence that changed an environment, a service, or fi

• runbook-run

  Carry out a runbook from the vault step by step, with a confirmation before each step that changes something outside the machine. Use whenever the user says "run the X runbook", "do the X workflow for KEY", or asks for an outcome a runbook's title or topics cover, such as "set up a PFD env for PFD-6

• shareable

  Produce an external-safe copy of an internal vault note for a client stakeholder, another team, or anyone without the vault. Use whenever the user says "make a version I can send", "shareable", "for Heiko", "Bobby will see it", "strip the internal stuff", or asks to export, forward, or publish a not

• ticket-intake

  Check a Jira ticket against the code and the vault before starting work on it. Use whenever the user says "pick up KEY", "start on KEY", "look at KEY", "what's blocking KEY", "can this be built as written", "intake", or pastes a Jira issue URL. A key mentioned in passing is daybook's job. A ticket t

• time-logging

  Draft the week's or month's billable hours as per-day, per-ticket worklog rows reconciled against the invoice source. Use whenever the user says "time logging", "log my hours", "worklogs", "reconcile against Harvest", "what did I bill", or mentions an invoice audit against Jira. Hours that cannot be

• vault-gardener

  Vault hygiene — find and fix inconsistencies before they rot the knowledge base. Use whenever the user asks to clean up, review, audit, or garden the vault, on a recurring weekly maintenance pass, or when another skill notices widespread frontmatter drift. Small inconsistencies compound; a monthly-g

• vault-init

  One-time setup that scaffolds an Obsidian vault for the consultant-vault-skills collection. Use whenever someone is setting up these skills for the first time, says "set up my vault", "initialize the vault skills", or "onboard me", reports that the config note is missing, or when any vault skill fai

• weekly-status

  Draft a client-ready weekly status update from the week's daily notes, meetings, decisions, and questions. Use whenever the user asks for a status update or client report, "what did I do this week", or an end-of-week or end-of-sprint summary — and when they ask what's slipping or what to flag to the

• work-chart

  Keep a plain-language record of goal-directed work as it happens, one note per ticket or topic per day: what was done, why, and what was decided. That covers code changes in any repo, research, coordination, design, and dead ends. Use whenever work toward a goal finished or was dropped in this sessi

Hooks (2)

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/work-chart-log.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/work-chart-stop.sh

Similar plugins