Prioritization & Backlog Agent Skills

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Convenes a council of specialized agents to debate important decisions, synthesizing independent perspectives into a structured recommendation and optional spec document.

Runs an Opportunity Solution Tree workflow with a lightweight graph database and CLI, routing through outcome, opportunity, solution, and assumption phases.

Moves issues and external PRs through a state machine of triage roles, categorizing, verifying, grilling, and writing agent-ready briefs.

Guides the agent to act as a product manager, collecting context, proposing three requirement plans (bug fix, new feature, iteration), scoring them by ROI, and recommending one with an MVP slice and timeline.

Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula.

Choose a prioritization framework based on product stage, team context, and stakeholder needs.

Run a user story mapping workshop with adaptive questions and a structured map output, generating backbone activities, user tasks, and release slices for a workflow.

Identify, evaluate, and prioritize design opportunities using impact-effort frameworks and strategic criteria.

Convenes four independent advisor voices to surface structured disagreement for ambiguous decisions, tradeoffs, and go/no-go calls before choosing a path.

Validates product direction before building, runs product diagnostics, founder reviews, user journey audits, and feature prioritization, producing actionable briefs and recommendations.

Decode an incoming message into a structured breakdown that separates the literal ask from the job-to-be-done, before replying to a loaded Slack ping, email, mandate, or escalation.

Creates product backlog items in Why-What-Acceptance format, producing independent, valuable, testable items with strategic context.

Guides strategic product decisions, pricing, backlog prioritization, and trend intelligence, routing tasks to specialized sub-skills.

Write and refine user stories using INVEST criteria, the 'As a X, I want Y, so that Z' format, Gherkin acceptance criteria, definition of ready, anti-patterns, and a review checklist.

Breaks applications or features into thin vertical user-story slices with clear acceptance criteria and user-observable value, suitable for backlog planning and feature decomposition.

Breaks a plan, spec, PRD, or conversation into independently-grabbable GitHub issues using tracer-bullet vertical slices, then publishes them as native sub-issues under a parent tracking issue via the gh CLI.

Provides a suite of five product team skills covering OKR alignment, feature prioritization, sprint planning, user research, and design systems, with scripts and templates for each role.

Turns vague features, bug clusters, roadmap items, or launch work into an execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.