PM Master Project Management Assistant

Problem Addressed

At project kickoff and iteration planning, PMs often need to digest conceptual requirements, architecture constraints, team capacity, and estimation assumptions before drafting WBS, milestones, and risks. When inputs are scattered or inconsistent, drafts can miss upstream dependencies or state uncertain timelines as fixed commitments.

PM Master targets software delivery project management. It acts as an assistant to the real PM, producing reviewable planning drafts rather than replacing the PM’s final decisions.

How It Works

The skill advances through remote MCP tools in staged calls. Each call passes context.stage, such as init for path confirmation, understand for input loading, knowledge for reference retrieval, constraints for goal alignment, plan for document generation, and finalize for format review.

Core capabilities include:
- Iteration 0 planning: draft a kickoff plan from conceptual requirements and high-level technical constraints.
- MVP planning: organize scope, technical risk tasks, and resource constraints into a workable plan table.
- Project planning: integrate requirements, architecture, iteration outcomes, and cost information into a unified plan.
- Detailed iteration planning: generate resource and constraint notes for a specific iteration based on upstream documents.
- Workload assessment: compare task items against reference baselines and mark uncertainty explicitly.

Boundaries

It supports project management assistance only: planning, WBS decomposition suggestions, progress templates, risk identification, and scope checks. It does not write code, design system architecture, perform BA requirement clarification, or make absolute schedule commitments. Treat all outputs as drafts and have the real PM review them before execution.