workbench

Plugin workbench from marketplace workbench-kit in YOOGOMJA/workbench-kit. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• audit-codex-support

  Audit this workbench repository for Codex support issues. Use when a task changes or reviews AGENTS.md, README.md, skills/, .agents/skills, .claude/skills, .codex/, .worktrees/, .codebases/, .gitignore, slash-command wording, skill entrypoints, tool state files, stale docs links, or verification com

• caveman

  Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less toke

• codebase-onboard

  Use to onboard (register) an external git repo as a workbench-managed codebase. Triggers on requests like "manage/add this repo in workbench", "register <owner/repo> as a target", "put it in codebases.yaml and clone it", or — without an issue number — "I want to work on this project in workbench". O

• docs-ingest

  Use to weave task harvest (decisions/lessons/runbooks/researches) into the workbench docs/ wiki. Called by task-submit, or whenever knowledge that should survive the task needs to land in docs/.

• docs-lint

  Use to check and groom the docs/ wiki: contradictions, staleness, orphan pages, broken cross-references, accumulated supersedes. During maintenance tasks or opportunistically during ingest.

• docs-query

  Use to ask the docs/ wiki a question, run a new task's preflight lookup, or guard right before a decision or approach ("did we already decide / already fail at this?").

• skill-harvest-recommender

  Use to retrospect a just-finished (or finishing) session/task and surface procedures repeated by hand that could graduate into a skill, runbook, or utils script. Triggers on "anything from this work worth turning into a skill/automation?", "check what to graduate into tooling", "pull out automation

• task-done

  Use when the user asks to clean up or discard a task, or to clear the workspace after a PR is merged.

• task-start

  Use when the user asks to start a task, pick up an issue, or begin a new attempt, or hands over an issue number to start work.

• task-status

  Use to see local and remote task status at a glance and diagnose drift (unpushed, stale status, missed cleanup). When you want to know where everything stands before starting or submitting, or after a multi-device handoff.

• task-submit

  Use when the user asks to submit, wrap up, or extract from a task, or when work has reached a point to open a PR.

• task-tickets

  Use to scan open workbench tickets joined with task branches and lifecycle events into unstarted / claim-attempted / in-progress / awaiting-PR / cleaned-up states. Read-only.

• ticket-incubate

  Use to turn an idea that has no issue/ticket yet into an actionable GitHub issue. Grow a vague notion by divergence, narrow only the gaps via a deficit-based interview, and create the issue once the four required elements (background, goal, done criteria, out-of-scope) are filled. Triggers on "I hav

Similar plugins