Fix a bug from BugPack by reading its context, locating code, applying fixes, and updating status. Use when: user asks to fix, repair, or resolve a bug. NOT for: just listing bugs (use bugpack-list-bugs) or just viewing bug details (use bugpack-view-bug).
View detailed bug context from BugPack including screenshots, environment info, and related files. Use when: user wants to see bug details, screenshots, or understand a specific bug before fixing. NOT for: listing all bugs (use bugpack-list-bugs) or directly fixing bugs (use bugpack-fix-bug).
BugPack - AI-powered bug tracking and fixing toolkit. List bugs, view bug details with screenshots, and fix bugs automatically. Includes three workflows: list-bugs, view-bug, fix-bug. Requires BugPack server running locally.
The antidote to vibe coding: a full software engineering team at your fingertips. Create or reverse-engineer PRDs, TRDs, personas, epics, and user stories with acceptance criteria, then plan, implement, test, and verify code against them - plus an autonomous Goal-Driven sprint loop that drives a prioritised batch to a…
Create an implementation plan — discovery in the real codebase first, then a plan document with verified code anchors, spec impact, and dependencies, filed under Active in the plans hub. Use when the user says "plan ", "write a plan for ...", or asks to turn a backlog task or accepted feature into work.
Brownfield-first workspace onboarding — scan the codebase and draft data/product.md plus starting architecture and spec docs from what the code shows, interview the developer only for what the code can't answer, mark the onboarding tasks done, and delete the example documents. Use when the user says "run the setup"…
Verify that implementation matches the graph — check a plan's tasks, spec requirements, and scenarios against the actual code before shipping, or sweep the whole workspace for doc↔code drift. Use when the user says "verify ", "is this ready to ship", "audit the docs", or "check for drift".
You are an expert at analyzing developer activity and workload from GitHub data. Your goal is workload balance and team health — not productivity surveillance. You help PMs identify overloaded developers, stale assignments, and unsustainable patterns before they become problems.
You are an expert at analyzing GitHub issue backlogs from a product manager's perspective. You don't just organize — you evaluate what matters most for project health and user experience, and you give actionable recommendations.
You are an expert at analyzing project delivery metrics from GitHub data. You produce actionable reports on milestone progress, delivery pipeline health, and stale work — giving PMs the data they need to make sprint decisions.
Processes bug reports from markdown files exported from any ticket system (Linear, GitHub Issues, Bugzilla, etc.), extracts reproduction steps, error logs, and environment details. Manages debugging workflow through Detective Methodology including reproduction, investigation, root cause analysis, fix verification, and…
A planning tool that turns rough ideas, long documents, attachments, or discussions into an executable software-workflow blueprint. A blueprint is a structured plan, not implemented code.
A procedure for checking and updating Workflow Agent plugins across their different installation methods. It determines whether the plugin is managed by a host such as Claude Code or installed manually, then uses the matching version source.