zenku

Plugin zenku from marketplace asermax-plugins in asermax/claude-plugins. Commands read from the repo's manifest — 5 days ago.

Skills (15)

• codex

  Load first when working with any zenku skill. Carries the vocabulary, the two rules, how to find the project's vault and conventions, and the habits for writing into it.

• commit

  Analyze uncommitted changes and create grouped conventional commits.

• design

  Lay out the current shape so the user can settle a new one — which modules exist, where the seams are, how data flows, and what earlier quests already decided. Use when the user wants to design a feature or a module, work out an interface, decide where a boundary belongs, or when another skill needs

• init

  Seed an Obsidian vault the project then owns, and re-run it later to add a folder, a template or a base.

• log

  Write something into the project's quest log in a few seconds — a bug, a chunk of work, a half-formed idea — without deciding anything about it. Use when the user says to note this down, add it to the backlog, capture this, or remember this for later, or when another skill turns something up that mu

• loot

  Get everything worth keeping out of a session before it ends — decided work into the quest log, findings about how something works into a note, and anything learned about how we work into the project's own conventions. Use at the end of any zenku session, or when another skill is about to close or d

• lore

  Write or update a durable note in the project's vault explaining how one part of the system works, following the project's own writing charter and templates. Use when the user wants something documented, a mechanism written up, a note brought back in line with the code, or when another skill has cha

• parley

  Talk something through with the user relentlessly, round by round, until you reach a shared understanding. Use when the user wants their thinking stress-tested, says to grill or press or challenge them, or when another skill needs a decision settled by the person who owns it.

• raid

  Build the thing — turn cleared ground into a shape and a set of slices, then land them one per session.

• research

  Investigate a question against high-trust primary sources and capture the findings in the project's vault. Use when the user wants a topic researched, docs or API facts gathered, reading legwork delegated, or when another skill needs a fact settled before a decision can be made.

• solve

  Close a quest out once its answer exists — write the answer on it, set its status, gist it into the adventure's solved index, and clear it from every blocked_by list that named it. Use when a question has just been answered or a slice has just been built, or when another skill has produced the resul

• spike

  Build throwaway code to answer a design question — does this state model hold up, does this API behave, is this fast enough, what should this look like. Use when the user wants to sanity-check an approach before committing to it, or when another skill needs a question answered by trying it rather th

• strike

  End an effort and clear it away — close out whatever is still open, carry out anything worth keeping, remove the spike worktree, and delete the effort's records. Use when an adventure has shipped or stopped being worth continuing, when a loose quest has just landed, or when a finished effort was nev

• take

  Take one quest and see it through in a single session — claim it, get onto the right branch, read it in full, present the work and settle what its record leaves open, solve it by its kind, and close it out. Use when the user wants to work the next thing on an adventure, or when a dispatcher needs on

• travel

  Travel a journey — work on something whose shape is not clear yet, mapping what stands in the way and clearing it one question per session, without building.