jbi

Plugin jbi from marketplace janbiehl in janbiehl/jbi-skills. Commands read from the repo's manifest — 2 days ago.

Skills (10)

• babysit

  Babysits a GitHub pull request toward mergeable, in rounds: rebases when GitHub says the branch must, fixes review comments and failing checks through subagents, replies on the threads it fixed and resolves them, posts a fresh /code-review each round, and stops when the PR is quiet or only a human c

• brainstorm

  Interviews the user about a feature, change, or design one question at a time until both sides hold the same picture, then writes up the decisions. Every question comes with a short summary, a running estimate of how many questions are left, and at least three options with pros and cons. Use wheneve

• handoff

  Writes a durable handoff document for whoever picks the work up next — a person, a fresh session, or another agent — capturing where things stand, what was decided and why, what was tried and rejected, and the next concrete step, grounded in the repository's actual state. With --resume it reads the

• map-feature

  Reads the codebase to explain how one named feature works end to end — locates it from a plain-language name, follows it from entry point through the logic to persistence and the UI, and writes a feature map with a mermaid diagram. Use when the user asks how a feature works, wants part of a codebase

• orchestrate

  Implements a GitHub epic or issue end to end — fetches its sub-issues, hands each one to a ticket lead that builds it in its own worktree, runs the tickets that do not block each other in parallel, has an independent verifier judge every commit, and integrates what passes onto a run branch behind a

• roundtable

  Convenes a panel of subagents, each arguing one perspective — UX, software architect, domain expert, customer, or whatever the topic needs — over several rounds in which every panelist reads the others' statements and answers them, then maps which aspect matters to which perspective and where they s

• test-drive

  Drives the running application through everything that landed in a time window, or — with --feature — through one named feature, judging each against its acceptance criteria the way a user would and persisting cases and verdicts under .scratch/agent-tests. Use when the user asks what landed last wee

• to-tickets

  Breaks a plan, spec, or the current conversation into a graph of thin vertical-slice tickets with explicit blocking edges, published as GitHub issues under an epic, written as local markdown files, or kept in the conversation. Use when the user wants to turn a plan into tickets, break a feature into

• verify

  Verifies that a change integrates by running the project's own review, format, build, unit, integration, and end-to-end gates, fixing what fails, and re-running only the gates a fix invalidated. Use whenever the user wants a change checked end to end, says 'verify this', 'run the full suite', 'does

• write-article

  Plans and writes a technical article or post with the user — a fixed interview first (topic, audience, medium, article type, length and scope, key points, sources, tone), then follow-up questions until no gap is left, then a briefing with a per-section length budget the user signs off, and only then

Similar plugins