Stats
Actions
Available In
Tags
Help us improve
Share bugs, ideas, or general feedback.
Plugin
ai-pm-assistant
Transforms raw project inputs—meeting transcripts, stakeholder messages, Jira data, or feature requests—into actionable PM artefacts: charters, PRDs, roadmaps, sprint plans, decision logs, budget reports, and stakeholder updates. Orchestrates a multi-skill pipeline that synthesizes discovery findings, identifies risks, runs release readiness assessments, and produces audience-specific communications, all within an isolated project workspace.
$
npx claudepluginhub erica-j-01/ai-pmPopularity
Stars
Med: 0·Avg: 267
Installs
Med: 0·Avg: 1
What's Inside
Skills20
budget-tracker
/budget-tracker
Tracks project spend against the charter budget over time and flags burn-rate risk. Use whenever someone says "track the budget", "how much have we spent", "are we on budget", "burn rate", or shares cost/effort data that needs comparing to an approved budget. Produces a budget status with spent-to-date, forecast at completion, variance, and a RAG verdict. Not a charter - the charter sets the budget; this monitors it.
project-charter
/charter
Turns a project brief, intake summary, or rough idea into a complete, sponsor-ready project charter. Use whenever someone says "write the charter", "start a new project", "formalise this project", "we need a charter", "draft the project document", or pastes a brief and needs it turned into an official document. Also triggers after an intake summary is complete and the next step is formal authorisation. A charter is the document that officially starts a project - without it, the PM has no authority to act and the team has no agreed scope. Use this skill early, before any planning begins.
decision-log
/decision-log
Creates a structured decision log from project changes, scope revisions, or PM decisions. Use whenever a decision needs to be formally recorded - including when someone says "log this decision", "document this change", "we changed direction on X", or when the PM Orchestrator detects a decision in a prior skill output and asks whether to log it. Also triggers when a user shares a change request, revised scope, or any deviation from the original plan that needs an audit trail.
discovery-workshop
/discovery
Plans and documents discovery workshops and stakeholder interviews for new projects. Use whenever a PM needs to prepare for or capture output from a discovery session - including when someone says "plan a discovery workshop", "run discovery on this", "I need to interview stakeholders", "help me structure discovery", "summarise what came out of the discovery session", or shares raw notes from a workshop or interview and needs them turned into structured findings. Discovery is where projects are made or broken - the goal is to understand the real problem before anyone commits to a solution. Use this skill before requirements are written and before any build begins.
meeting-notes
/meeting-notes
Use this skill whenever the user wants to extract meeting notes, minutes, or a summary from a meeting transcript - especially from Microsoft Teams, Zoom, Google Meet, or any raw transcript text. Trigger when the user shares a transcript file or text and asks for a summary, key points, action items, decisions, or meeting minutes. Also trigger when the user says things like "summarize this meeting", "what was discussed", "extract the important parts", "write up the minutes", or pastes a block of conversation text that looks like a meeting transcript. This skill produces clean, plain-English meeting minutes and follow-up questions the user can ask to go deeper. Also trigger when the user wants to save or publish meeting minutes to Confluence.
Stats
Version2.0.0
LanguageTypeScript
Stars5
Forks3
MaintenanceExcellent
LicenseMIT
Last Commit
Added
Help us improve
Share bugs, ideas, or general feedback.
