kenmulford
- 15 skills
- 0 followers
- 17 hours ago last updated
- ▌ Wbs · kenmulford bundleGenerate a Project+ style Work Breakdown Structure (WBS) as a .xlsx, decomposing project deliverables into a hierarchy of work packages with codes, owners, effort estimates, and durations. Use whenever a user needs to break a project into plannable chunks — triggers include "WBS", "work breakdown structure", "work packages", "project decomposition", "break down the project", "deliverables hierarchy", "scope decomposition", or any context where a PM is turning a charter into plannable work. Enforces Project+ WBS conventions (100% rule, 8–80 hour work packages, hierarchical numbering) and prevents fabrication of work packages, owners, or estimates the user never stated.
- ▌
- ▌ Raci Matrix · kenmulford bundleGenerate a Project+ style RACI (Responsibility Assignment Matrix) as a .xlsx, mapping project activities to team members with R/A/C/I assignments. Use whenever a user needs to clarify *who does what* — triggers include "RACI", "responsibility matrix", "RAM", "who owns what", "role clarity", "accountability matrix". Enforces Project+ RACI rules (exactly one A per row, ≥1 R) and prevents fabrication of people or activities.
- ▌ Team Roster · kenmulford bundleGenerate a Project+ style team roster as a .xlsx listing every known project team member with role, responsibilities, availability, manager, contact, and core/extended status. Use whenever a user needs to capture "who is on the project" in a structured artifact — triggers include "team roster", "project team", "staffing plan", "team structure", "who's on the project", "team list", "resource roster", or any context where a PM is standing up a team. Enforces Project+ conventions and prevents fabrication of people, titles, or details the user never stated.
- ▌ Decision Log · kenmulford bundleGenerate 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.
- ▌ Kickoff Deck · kenmulford bundleGenerate 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.
- ▌
- ▌ Status Report · kenmulford bundleGenerate a Project+ style weekly project status report as .docx — executive summary, RAG with trend vs prior week, accomplishments, upcoming, risks vs issues (distinguished), asks, metrics, and dependencies. Use whenever a user needs to produce a status report, weekly update, steering committee update, stakeholder update, or "where are we" document. Triggers include "status report", "weekly status", "exec update", "sponsor update", "RAG status", "this week's update". Enforces never-invent discipline and structural consistency across reporting weeks so stakeholders can scan the same sections in the same order every time.
- ▌ Change Request · kenmulford bundleGenerate 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.
- ▌ Closeout Report · kenmulford bundleGenerate 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.
- ▌ Lessons Learned · kenmulford bundleGenerate a Project+ style lessons-learned register as .docx — one entry per lesson with category, what happened, root cause, impact, recommendation, and owner. Use whenever a user needs a lessons-learned document, retrospective write-up, post-mortem, project closeout learnings, or phase-gate retrospective. Triggers include "lessons learned", "retro", "retrospective", "post-mortem", "closeout learnings", "what went well", "what went wrong". Enforces never-invent discipline for root causes, never fabricates positive lessons to balance negatives, and preserves the user's exact phrasing.
- ▌ Meeting Minutes · kenmulford bundleGenerate project meeting minutes as .docx — attendee list (present/absent), agenda items discussed, decisions made, action items with owners and due dates, parking lot, and next meeting. Use whenever a user needs meeting minutes, meeting notes, action items writeup, steering committee minutes, standup recap, or retro notes. Triggers include "meeting minutes", "meeting notes", "action items", "steering committee minutes", "standup notes", "MoM". Enforces never-invent discipline for attendees, decisions, action items, and quoted statements.
- ▌ Project Charter · kenmulford bundleGenerate a sponsor-ready project charter and preliminary scope statement as a .docx. Use whenever a user is starting a new project and needs to formally frame it — triggers include "project charter", "charter doc", "scope statement", "preliminary scope", "initiating a project", "PID", "authorize the project", or any context where a PM needs to capture vision, scope, deliverables, success criteria, and sponsor approval in one document. Enforces Project+ conventions and prevents fabrication of numbers, dates, or constraints the user never stated.
- ▌
- ▌ Stakeholder Engagement Plan · kenmulford bundleGenerate a Project+ style Stakeholder Engagement Plan as a .docx, with a stakeholder register, power/interest grid, current-vs-desired engagement levels, and a communication plan per stakeholder. Use whenever a user needs to plan how to manage, communicate with, or influence project stakeholders — triggers include "stakeholder engagement plan", "stakeholder register", "stakeholder analysis", "power/interest grid", "communication plan", "stakeholder management", "SEP". Enforces Project+ engagement-level vocabulary and prevents fabrication of stakeholders, positions, or concerns.