By kenmulford
15 Project+ skills for technical PMs — generate charters, RACI matrices, risk registers, status reports, meeting minutes, decision logs, and more as production-ready .docx, .xlsx, and .pptx artifacts. Enforces never-invent discipline: no fabricated names, dates, metrics, or stakeholders.
Generate a Project+ style project budget as .xlsx — line items by category with committed amounts, actuals, variance, approved total, contingency, and optional monthly burn. Use whenever a user needs to capture or review project costs — triggers include "budget", "cost plan", "cost baseline", "approved budget", "contingency reserve", "burn plan", "variance". Enforces never-invent discipline: no fabricated costs, categories, owners, contingency percentages, or reconciling "plug" lines; fuzzy amounts stay fuzzy.
Generate a Project+ style change request as .docx — request metadata, description, impact analysis across scope/schedule/cost/quality/resources/risk, options considered, recommendation, and CCB approval block. Use whenever a user needs a change request, CR, change control form, scope change document, RFC, or baseline change. Triggers include "change request", "CR", "change control", "scope change", "baseline change", "RFC". Enforces never-invent discipline for impact numbers, CCB members, and disposition — and preserves the user's fuzzy estimates exactly.
Generate a Project+ style project closeout report as .docx — baseline-vs-actual for scope/schedule/cost, deliverables acceptance log, open items and known defects, contract/vendor closure, and formal sign-off block. Use whenever a user needs a closeout report, project closure document, final report, phase-end report, or handover document. Triggers include "closeout report", "project closure", "final report", "handover", "close the project", "wrap-up report". Enforces never-invent discipline for variance numbers, acceptance status, and sign-offs.
Generate a project decision log as .xlsx — one row per binding decision with ID, title, decision maker, date, context, options considered, decision, rationale, consequences, and review date. Use whenever a user needs a decision log, decision record, ADR, architectural decision record, choice history, or governance trail. Triggers include "decision log", "decision record", "ADR", "decision history", "document this decision", "what did we decide". Enforces never-invent discipline for decision makers, rationale, and options considered.
Generate a Project+ style project kickoff deck as a .pptx — title, vision, objectives, scope, team, milestones, risks, ways of working, and asks. Use whenever a user needs to run or prepare for a project kickoff meeting — triggers include "kickoff deck", "kickoff slides", "kickoff presentation", "kickoff meeting", "project kickoff", "launch deck", or any context where a PM is formally introducing a new project to stakeholders and team. Enforces Project+ kickoff structure and prevents fabrication of metrics, dates, names, or commitments the user never stated.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin that turns plain-language project descriptions into production-ready PM artifacts — no hallucinated names, dates, or metrics.
15 skills covering the full Project+ lifecycle, each generating a formatted .docx, .xlsx, or .pptx file from natural language input. Built with hard guardrails that prevent the LLM failure modes that make most AI-generated PM documents unusable.
| Skill | Artifact | Format |
|---|---|---|
| project-charter | Project charter + preliminary scope statement | .docx |
| kickoff-deck | Project kickoff presentation | .pptx |
| team-roster | Project team roster | .xlsx |
| raci-matrix | Responsibility assignment matrix | .xlsx |
| stakeholder-engagement-plan | Stakeholder register, power/interest grid, comms plan | .docx |
| risk-register | Risk register with RAG ratings | .xlsx |
| status-report | Weekly/biweekly status report | .docx |
| project-schedule | Project schedule with milestones | .xlsx |
| budget-plan | Project budget breakdown | .xlsx |
| wbs | Work breakdown structure | .xlsx |
| meeting-minutes | Structured meeting minutes | .docx |
| decision-log | Decision record / ADR log | .xlsx |
| change-request | Change request with CCB governance | .docx |
| lessons-learned | Lessons learned register | .docx |
| closeout-report | Project closeout report | .docx |
Each skill contains a SKILL.md with hard rules that prevent common LLM failure modes in PM artifacts, plus a Python script that renders the structured output. You describe a project situation in plain language; the skill parses your input into a JSON schema, applies fidelity checks, and generates the formatted document.
These skills enforce discipline that stock LLMs consistently violate:
[TBD] placeholders, not fabricated content# Add the marketplace (one time)
claude plugin marketplace add kenmulford/PMSkills
# Install the plugin
claude plugin install pm-skills@pmskills
# Update marketplace to pick up new versions
claude plugin marketplace update pmskills
/plugin marketplace add kenmulford/PMSkills
/plugin install pm-skills@pmskills
/plugin marketplace update pmskills
/reload-plugins
Download pm-skills.plugin from this repo and open it in Cowork.
python-docx (for .docx skills)openpyxl (for .xlsx skills)python-pptx (for .pptx skills)Install: pip install python-docx openpyxl python-pptx
Ken Mulford
github.com/kenmulford · linkedin.com/in/kmulford · ken@kenmulford.com
npx claudepluginhub kenmulford/pmskills --plugin pm-skillsUI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
This skill should be used when users need to generate ideas, explore creative solutions, or systematically brainstorm approaches to problems. Use when users request help with ideation, content planning, product features, marketing campaigns, strategic planning, creative writing, or any task requiring structured idea generation. The skill provides 30+ research-validated prompt patterns across 14 categories with exact templates, success metrics, and domain-specific applications.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.