agentic-pm-kit

Route the user to the right brainstorming strategy for their situation by matching their goal to a curated shortcut table or, when the goal is unclear, asking 3 diagnostic questions and recommending one or two strategies from the curated 20. Invoke when the user wants to brainstorm but has not yet chosen a technique.

Facilitate a Scrum Sprint Planning event, producing a sprint goal and a committed Sprint Backlog drawn from the prioritized Product Backlog. Invoke when the team is about to begin a new sprint and needs to select and plan its work.

Construct a PMBOK-shaped Work Breakdown Structure from the project's epic-and-story hierarchy. Invoke when the team needs a deliverable-oriented decomposition of project scope into manageable work packages before building a schedule or assigning resources.

Draft a PMBOK-shaped project charter from a concept memo or product brief. Invoke when the user needs a charter for initiation-phase documentation.

Produce a PMBOK-shaped project closure report suitable for sponsor signature, consolidating charter, final schedule, final budget, retrospectives, post-mortems, and stakeholder acceptance records. Invoke when the project has reached final deliverable acceptance and requires formal closure documentation.

Produce a PMBOK-shaped communication matrix, escalation paths, and meeting cadence from a project charter and stakeholder register. Invoke when the team needs a formal plan governing how project information flows to each audience.

Teach the team three complementary estimation techniques — Planning Poker, T-shirt sizing, and three-point (PERT) — and record the estimates the team produces for their own items. This is a human-led skill: the agent teaches and facilitates; the team estimates. Invoke when the team needs to estimate stories, epics, or tasks and wants a shared technique, or when an estimate is required for a planning gate.

Decompose a PRD into Epics and INVEST-shaped User Stories with acceptance criteria and priority. Invoke when the team has a baselined PRD and needs an actionable story backlog before sprint planning or WBS construction.

Facilitate a blameless post-mortem for a serious incident, near-miss, or project-level retrospective. Invoke when a failure significant enough to warrant system-level learning has occurred, or when an entire project closes and needs a final retrospective.

Draft a simplified, PMBOK-compatible Product Requirements Document from a product brief and project charter. Invoke when the planning phase begins and the team needs a structured requirements baseline before decomposing scope into a WBS or epics.

Draft a concise business-case document covering problem statement, target users, success metrics, key risks, and high-level approach. Invoke when the user needs a structured business case before or during project initiation.

Produce a concise quality plan defining quality objectives, measurable metrics, assurance activities, and control checkpoints for a project. Invoke when the team needs an explicit, agreed-upon quality standard before entering execution.

Produce a concise resource plan covering team roster, equipment, budget rollup, external dependencies, and hiring timeline for a project. Invoke when the team needs an explicit record of who, what, and how much is committed to the project.

Facilitate a sprint or iteration retrospective that surfaces real learnings and produces owned, dated action items. Invoke when a sprint or iteration has closed and the team needs a structured inspect-and-adapt session.

Produce a probability × impact risk matrix with PMBOK-style response strategies, derived from a project charter and optional stakeholder register or schedule. Invoke when the team needs a structured risk register before a planning gate, milestone review, or go/no-go decision.

Produce a Mermaid-Gantt schedule diagram and narrative schedule from a WBS and effort estimates. Invoke when the user needs a time-phased plan with task dependencies and critical path identification.

Facilitate a Scrum Sprint Review event, capturing what was built, stakeholder feedback from the demo, and decisions about the path forward. Invoke when the sprint has concluded and the team is ready to present its increment to stakeholders.

Identify, classify, and document project stakeholders by running a structured brainstorming strategy against the project charter, then emit a complete stakeholder register. Invoke when initiating a project or whenever the stakeholder landscape needs a systematic refresh.

Help the user prepare a concise three-bullet standup note covering yesterday, today, and blockers before walking into the Daily Scrum. Invoke when the user needs a ~2-minute prep session immediately before their standup meeting.

Facilitate the execution and review of a single user story through implementation, testing, and acceptance. Invoke when a developer or team is ready to begin work on a specific backlog story that has a code-producing component.

Facilitate an Alien Anthropologist session in which the team examines their own project, processes, or user environment through the eyes of a completely uninitiated outside observer to surface hidden assumptions. Invoke when requirements elicitation, stakeholder onboarding, or user research is hampered by familiarity blindness.

Facilitate an Anti-Solution session that generates ways to make the problem worse or to guarantee failure, then inverts those findings to reveal overlooked solution paths. Invoke when the team is stuck on a single solution frame or when a pre-mortem or risk exercise needs creative expansion of the failure-mode list.

Facilitate an Assumption Reversal session that surfaces hidden constraints by inverting core beliefs about a challenge. Invoke when the user needs to break out of conventional solution space, challenge inherited design decisions, or stress-test a plan's underlying logic.

Facilitate a Brain Writing Round Robin ideation session in which participants contribute silently and sequentially to build on each other's ideas. Invoke when the user needs inclusive idea generation from a distributed or mixed-participation team.

Facilitate a Chaos Engineering brainstorming session that stress-tests a project plan, system design, or process by deliberately hypothesizing worst-case failures to reveal hidden fragilities. Invoke when preparing a risk register, pre-mortem analysis, or resilience review before a critical milestone.

Facilitate a Constraint Mapping session that identifies, categorizes, and evaluates all constraints bearing on a project challenge to reveal viable solution pathways. Invoke when the user needs to distinguish real from imagined limitations, plan around blockers, or prioritize which constraints to address before execution begins.

Facilitate a Decision Tree Mapping session to visualize all paths, outcomes, and risks of a complex project decision before committing. Invoke when the user faces a multi-branch decision where each choice leads to distinct consequences and the full option space has not been charted.

Facilitate a Failure Analysis session that systematically extracts lessons from past failures to prevent recurrence and improve current plans. Invoke when the user needs to learn from a project incident, a failed deliverable, a rejected milestone, or a repeated process breakdown.

Facilitate a First Principles Thinking session that strips assumptions from a problem and rebuilds understanding from verified foundational truths. Invoke when the team is trapped in inherited constraints, over-specified solutions, or scope debates that cannot be resolved by incremental negotiation.

Facilitate a Mind Mapping session to visually organize ideas radiating from a central concept, revealing connections and expanding the team's understanding of a topic or problem. Invoke when the user needs to structure an open-ended topic, generate hierarchically organized ideas, or capture a brainstorm before narrowing to solutions.

Facilitate a Morphological Analysis session to systematically explore all parameter combinations for a complex design or decision problem. Invoke when the user needs a comprehensive mapping of solution space across multiple independent dimensions.

Facilitate a Question Storming session that generates a structured bank of questions before any solutions are proposed. Invoke when the user suspects the team is solving the wrong problem, needs to reframe a challenge, or lacks clarity on what is actually being asked.

Facilitate a Resource Constraints ideation session to generate creative solutions under explicit budget, time, or capacity limitations. Invoke when the user needs to unlock innovative options in the face of a binding project constraint.

Facilitate a Reverse Brainstorming session to surface hidden risks and assumptions by deliberately ideating how to cause the problem, then inverting the results into solutions. Invoke when the user needs risk identification or creative problem-solving that conventional brainstorming has not produced.

Facilitate a Role Playing ideation session to generate solutions and surface blind spots by viewing the project through multiple stakeholder perspectives. Invoke when the user needs empathy-based insight or a more complete view of who is affected by a project decision.

Facilitate a Six Thinking Hats session to examine a project decision or proposal from six structured perspectives, preventing premature convergence and surfacing blind spots. Invoke when the team needs to evaluate a significant decision without collapsing into debate.

Facilitate a Solution Matrix session to score and rank competing options against weighted criteria, producing a defensible, bias-reduced recommendation. Invoke when the user must choose among two or more alternatives and the decision requires structured multi-criteria evaluation.

Facilitate a Values Archaeology session that excavates the unstated values and basic assumptions driving a team's or stakeholder's decisions. Invoke when stakeholder conflict, charter disagreements, or recurring scope disputes appear to stem from misaligned underlying priorities rather than factual differences.

Facilitate a What If Scenarios session to explore plausible futures, stress-test plans, and surface contingency options. Invoke when the user needs to examine how the project would respond to changes in key assumptions about scope, schedule, budget, or environment.

Facilitate a Five Whys root-cause analysis. Invoke when the user needs to find the underlying cause of a project impediment, schedule slip, recurring defect, or stakeholder dissatisfaction signal.