Planning plugins

Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking or wants to find high-impact features.

1 skill

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

1 skill

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear or features are complex.

1 skill

Plan, document, and orchestrate software work the BMAD way — product briefs, PRDs, architecture, epics, and ready-for-dev stories — then fan the work out as conflict-free parallel workstreams that your dev tools execute. Implements the BMAD Method (v6.x) by the BMAD Code Organization. This plugin does the planning and orchestration; it never writes the code.

20 skills · 3 agents · hooks

Planning framework for Claude Code that catches gaps before execution: a 10-step pipeline, 21 anti-patterns with detection rules, mandatory FAILED conditions, and silent execution-vehicle selection.

2 skills · 1 agent

Validated interactive system maps and diagrams as standalone HTML from a typed JSON spec, for one of five diagram types (architecture, workflow, sequence, dataflow, lifecycle). Use when the user asks to visualize architecture, a workflow, a call sequence, a data pipeline, or a state machine, or to map this repository. Not for ad hoc drawings or slide art, and not for Mermaid output; use the artifact tool for plain Markdown.

1 skill

Decides the engineering approach for an intent in an interactive session: investigates, proposes two or three genuinely different approaches with trade-offs, recommends, lets the user decide, and writes the decision doc. Not a task-by-task plan; use cut-it. Not a multi-perspective debate; use design-council. Not product intent; use product-intent. Not a typed implementation handoff; use tech-spec.

1 skill

Turns a finished PRD or architecture doc into a ticket backlog of small stories with verifiable acceptance criteria, confirmed, then created as GitHub issues or in another configured tracker. Not for local sprint slicing into a SPRINT.md; use cut-it.

1 skill

Author a product brief by interview (the PRD tradition, under a plainer name), then emit user stories, scope, metrics, and a derived nested task list.

1 skill

Design workflow in the RFC tradition: problem -> alternatives -> tradeoffs -> design -> risks -> recommendation -> impl plan. Two sizes with hard ceilings.

1 skill

Claude Code skills for creating, reviewing, splitting and submitting work items — RFEs to the RHAIRFE Jira project and Initiatives to RHAISTRAT — through one generic pipeline (/rfe-create, /rfe-review, /rfe-split, /rfe-submit, /rfe-auto-fix, /rfe-speedrun; --type initiative for Initiatives). The legacy dotted names (/rfe.create and friends) remain as compatibility aliases.

13 skills · hooks

Claude Code skills for creating, reviewing, and submitting strategies to the RHAISTRAT Jira project. Provides an automated pipeline from initial creation through refinement, adversarial review with independent reviewers, and human sign-off workflow with pull/push/signoff gates.

12 skills · hooks

Execute RHOAI SPIKE investigations with human-in-the-loop approval gates. 9-step lifecycle: intake, plan, Jira sync, AI research enrichment with hallucination detection, pytest test suites on OpenShift, rubric-based scoring with security gates, and RFE input generation. Supports both runtime and protocol library assessment.

2 skills · 4 MCP servers

Fully local visual plans and recaps — the agent writes markdown, a bundled zero-dependency server renders it in your browser with Mermaid diagrams, rich diffs, styled DB migrations, API call cards, and a read-only OpenAPI view, with live reload and a comment feedback loop. No remote services.

2 skills

Plan-building flow that ends in one clean plan, never a story of revisions — a commit-stamped map of the codebase's structure, flows, patterns, and tests, parallel exploration, a zero-context review of the draft against the original ask, questions batched for the user and filtered by what was already decided, tickets with what/why/acceptance criteria/dependencies/size, spikes resolved on the spot, every decision logged with its reason, and a plain-text handoff to implementation.

1 skill

A quick plan for a small coding change — one short plan file with one ticket, the repository's patterns and the tests to extend found by two scoped explorers instead of a full codebase map, unknowns checked on the spot, only the user's decisions asked, one fresh check of the plan, and a warning whenever the change outgrows a quick plan, recommending the full planning-flow skill when it is installed.

1 skill

Decides the engineering approach for an intent in an interactive session: investigates, proposes two or three genuinely different approaches with trade-offs, recommends, lets the user decide, and writes the decision doc. Not a task-by-task plan; use sprint-plan. Not a multi-perspective debate; use design-council. Not product intent; use product-intent. Not a typed implementation handoff; use tech-spec.

1 skill

Turns a finished PRD or architecture doc into a ticket backlog of small stories with verifiable acceptance criteria, confirmed, then created as GitHub issues or in another configured tracker. Not for local sprint slicing into a SPRINT.md; use sprint-plan.

1 skill

Turns an idea into a product requirements document through a phase-gated interview, ending in PRD.md plus per-milestone prompt files ready to drive a coding agent. Not for the problem-first product thesis; use product-intent.

1 skill

Budget planning: annual/quarterly budgets, forecasting from actuals, employee cost budgeting with burden rates, and project budgeting.

1 skill · 4 commands · 1 MCP server

Planejamento visual com diagramas Excalidraw via servidor MCP oficial — arquitetura, fluxos, dependências, decisões e roadmaps editáveis.

1 skill · 1 MCP server

Statically assess a codebase against the ISO/IEC 25010:2023 product quality model (9 characteristics, ~40 sub-characteristics) using ISO/IEC 25023 measures. Produces a scored Markdown report + JSON scorecard with file:line evidence, severity-rated findings, and Mermaid radar/bar diagrams.

1 skill

WBS from scope + deliverables. Enforces 100% rule, mutually exclusive siblings, deliverable-oriented nodes, 8/80-hour sizing, depth-by-need (3–5 levels). Decomposition axes (deliverable / phase / responsibility / hybrid) consistent within branches. WBS dictionary per node (description, deliverable, acceptance, size, deps, risks). Milestones distinct from work. Intra-WBS dependencies + coverage matrix. Anti-patterns flagged.

1 skill

Scope statement — purpose, SMART objectives with success criteria, deliverables with acceptance, explicit in-scope, explicit out-of-scope (highest-leverage section preventing creep arguments), assumptions with confirm-by dates, constraints (budget / time / people / regulatory / technical), boundaries (organizational / geographic / temporal / technical / segments), stakeholders + approval authority, scope-change protocol, coverage check with WBS, open questions. Distinct from business case / WBS / stakeholder map.

1 skill

Deepest-mode planning — consensus + gates + synthesis. Self-contained.

19 skills · 7 commands

Write proposals for code changes that people can review before any code is written: checked against the codebase, with mermaid diagrams, diffs and tables, then refined in discussion.

3 skills · 4 agents

Review a UX flow, agentic handoff point, or delegation-boundary decision for agency risks and articulation barriers before implementation — advocating for the user's intent map, not the screen in front of you

1 skill · 1 agent

Plans a software project end to end before any code is written, then captures the result as durable context files (AGENTS.md + context/) that keep agents accurate across sessions: a decision log that keeps its reasoning, phased specs with mechanically checkable exit criteria, an explicit scope boundary, UI tokens/rules/registry, and verification rules that stop invented versions and APIs.

1 skill

Turn customer evidence into auditable personas, journeys, progression hypotheses, and product-strategy opportunity maps

1 skill

Turn feature requests, PRDs, and backlog issues into an EARS-format spec file or one new GitHub issue

1 skill