minerva

Plugin minerva from marketplace agent-marketplace in honerlaw/agent-marketplace. Commands read from the repo's manifest — 3 days ago.

Skills (20)

• cleanup

  Removes `.minerva/worktrees/YYYY-MM-DD-slug/` directories whose branches have been merged into the default branch, prunes the corresponding local branches. Idempotent; never force-removes unmerged work, never commits, and opens no PR — the knowledge wiki needs no post-merge pass because its catalog,

• debug

  Investigate a bug end-to-end — gather evidence first, then diagnose root cause grounded in that evidence, and report with a mechanically-derived confidence score. Use this whenever the user reports breakage of any kind. Live-incident framing — "users are reporting", "X is broken in prod", "the cron

• explore

  Use when the user wants to explore a fuzzy idea, think through a problem, or weigh directions BEFORE committing to a work unit — when it's not yet clear whether there's anything to build, or what. The minerva analog of brainstorming — a divergent, commitment-free dialogue that writes no file, alloca

• grill-plan

  Use when a plan has just been drafted in conversation and needs stress-testing before approval — invoked by `minerva:propose` after approach selection and by `minerva:replan` after the new-plan brainstorm, also usable standalone on any drafted plan. Interviews the user relentlessly about the drafted

• init

  Scaffolds the `.minerva/` directory layout and agent-file Routing section — durable records, knowledge tracking, and project memory for agent work in a project. Idempotent — re-runs report per-piece status without rewriting anything in place, and it warns about legacy `.minerva/decisions/` layouts.

• lint

  Health-checks the `.minerva/knowledge/` wiki — runs the deterministic detector for mechanical defects (invalid ids, broken `## Related` links, missing `**Theme**` / `**Summary**` metadata, legacy `index.md` / `overview.md` still present, single-entry themes) and adds LLM-judged advisory findings (or

• migrate-fix

  Migrates a legacy knowledge corpus to the current shape — MUTATES `.minerva/knowledge/` and `.minerva/work/` behind confirmation gates. (1) Renames legacy `NNN`-prefixed entries and work units to date ids (`YYYY-MM-DD-type-slug`), dating each from its own git history and retargeting every wikilink,

• migrate

  Checks an existing `.minerva/knowledge/` folder against the current (3.0) wiki shape — read-only; runs the deterministic `migration_status` shape signal (files that don't conform to the naming convention and are therefore invisible to the wiki tooling — a false clean — legacy `index.md` / `overview.

• one-by-one

  Walks the user through the questions already outstanding in the current session, one at a time, showing the running position and total ("Question 3 of 10") and waiting for each answer before the next. Every question offers three to five concrete options, marks a recommended answer or says there is n

• promote

  Finalizes a minerva work unit's record — promotes durable knowledge to `.minerva/knowledge/`, rewrites `proposal.md` to match reality, and archives the scratchpad; every forward-looking TODO gets an explicit disposition — a small defect is fixed in this unit, and only an urgent defect too large to a

• propose-ship-auto

  Runs the full minerva lifecycle end-to-end with no scheduled human gates — the one autonomous orchestrator, for any size of change ("do the whole thing without asking", "just ship this", "ship this with a second opinion", "auto propose and ship"). Same lifecycle as `minerva:propose-ship` (propose -

• propose-ship

  Runs the full minerva lifecycle end-to-end in one command with the user in the loop — a human decision gate at each phase transition. Orchestrates propose - work - review - promote - ship - cleanup by delegating to each skill in sequence with no logic duplication, refuses to start if in-flight work

• propose

  Starts a new minerva work unit — brainstorm-style intake with one-question-at-a-time clarification, 2-3 candidate approaches, a `minerva:grill-plan` stress-test before approval, then creates the unit's branch + worktree and writes the approved design to `.minerva/work/YYYY-MM-DD-slug/proposal.md`, w

• replan

  Records a course-correction for the current minerva work unit — drafts Original plan / What changed / New plan, stress-tests it via `minerva:grill-plan`, then appends a dated divergence entry to `.minerva/work/YYYY-MM-DD-slug/replan.md`. Use when work has diverged from the proposal in a load-bearing

• review

  Reviews a changeset against both the minerva spec/knowledge lenses and code quality. With a work unit in context it runs a spec/knowledge audit alongside the code quality review, presenting both result sets before unified triage; if a GitHub PR exists and the optional `code-review:code-review` skill

• round-table

  Dispatches a 3-agent Proponent/Skeptic/Arbiter panel of fresh-context subagents over a decision or drafted artifact, counts accept votes against a caller-specified quorum (default 2/3), runs at most one revision round, and escalates to the user when consensus fails twice. Use when another skill dele

• ship

  Ships the current work — commits outstanding changes to a branch, opens a pull request, watches CI without blocking (a tracked watcher that resumes when checks settle, backed by a long scheduled fallback), fixes CI failures, and enables auto-merge. Use when the user asks to ship, push, open a PR for

• status

  Prints the current overall status of a project's minerva workstream as markdown tables — every unit's lifecycle stage, phase progress, branch/PR state and the next lifecycle step to run, plus knowledge-wiki health and the deferred backlog. Read-only; mutates nothing. Use when the user asks where thi

• using-minerva

  Use when starting work in a project that uses minerva (a `.minerva/` directory exists at the project root, or the user has invoked any `minerva:` skill in this session), or when the user describes starting / continuing / finishing a meaningful unit of work — features, refactors, investigations, spik

• work

  Implements a minerva work unit — reads the proposal and any replans, maintains a live scratchpad, auto-invokes the `minerva:replan` protocol when reality drifts in a load-bearing way, and checks proposal Open Questions on resume and Success criteria before signaling completion. Use when the user is

Similar plugins