Project Manager
Plan, track, and close solo or small-team projects with structured timelines, risks, and stakeholder-ready status instead of ad-hoc todos.
Overview
Project Manager is an agent skill most often used in Validate (also Build, Ship, Operate) that plans, executes, monitors, and closes projects using agile and traditional methods.
Install
npx skills add https://github.com/404kidwiz/claude-supercode-skills --skill project-managerWhat is this skill?
- Covers planning, execution, monitoring, and closure across traditional and agile approaches
- Supports timelines, budgets, resources, milestones, and risk registers
- Facilitates cross-functional coordination and stakeholder communication
- Includes enterprise-scale patterns such as WBS and steering-committee governance
- Example outcomes cite on-time delivery, adoption metrics, and structured escalation paths
- Example enterprise rollout references a 500+ task work breakdown structure
- Example results cite 98% user adoption within 3 months and delivery 5% under budget
Adoption & trust: 988 installs on skills.sh; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are juggling a multi-step initiative without a shared plan, risk list, or milestone view your agent can follow.
Who is it for?
Indie founders coordinating a product build, integration, or launch with real deadlines, budget limits, and cross-cutting tasks.
Skip if: Single-file bugfixes with no milestones, or teams that already run a locked process in a dedicated PM suite with no agent involvement.
When should I use this skill?
Planning and executing new projects, managing timelines budgets and resources, tracking milestones, managing risks, or facilitating stakeholder communication.
What do I get? / Deliverables
You get a governed project plan with timelines, tracking, risk handling, and stakeholder-ready status suitable for execution and closure.
- Project plan with milestones and work breakdown
- Risk register with mitigation strategies
- Status and stakeholder communication outlines
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
New initiatives need scoping, milestones, and governance before full build commitment—the skill’s first natural stop is validating what will be delivered. Scope subphase is where work breakdown, budgets, and hybrid agile/waterfall choices lock the plan before execution ramps in build.
Where it fits
Define a 500-task WBS and budget envelope before committing to an ERP-style integration.
Run weekly milestone reviews and resource adjustments while the product is in active development.
Coordinate launch readiness, defect triage, and escalation paths before go-live.
Close out a phase, capture lessons learned, and plan the next improvement cycle.
How it compares
Use instead of ad-hoc chat task lists when you need governance, risks, and milestone closure—not a code generator skill.
Common Questions / FAQ
Who is project-manager for?
Solo builders and small teams who own planning and delivery end-to-end and want agent help for timelines, risks, and stakeholder updates.
When should I use project-manager?
In Validate to scope a new initiative; in Build to coordinate execution and resources; in Ship for launch prep and issue resolution; in Operate when tracking iterations and closure.
Is project-manager safe to install?
It is documentation-style PM guidance without built-in tool permissions listed; review the Security Audits panel on this Prism page before pairing it with skills that run shell or network access.
SKILL.md
READMESKILL.md - Project Manager
# Project Manager ## Purpose Provides project management expertise specializing in planning, execution, monitoring, and closure of projects. Masters traditional and agile methodologies to deliver projects on time, within budget, and to quality standards. ## When to Use - Planning and executing new projects or initiatives - Managing project timelines, budgets, and resources - Coordinating cross-functional teams - Tracking project progress and milestones - Managing risks and resolving project issues - Facilitating project communication with stakeholders ## Examples ### Example 1: Enterprise Software Implementation **Scenario:** A Fortune 500 company implementing a new ERP system across 12 countries. **Approach:** 1. Established program governance with steering committee 2. Created detailed work breakdown structure (500+ tasks) 3. Implemented hybrid methodology (Waterfall for core, Agile for integrations) 4. Established risk register with mitigation strategies 5. Set up automated status dashboards and escalation paths **Results:** - Delivered on time and 5% under budget - 98% user adoption within 3 months - Zero critical defects in production - Awarded "Best Implementation" by vendor ### Example 2: Product Launch Coordination **Scenario:** Coordinating a multi-team product launch with 6-month deadline. **Approach:** 1. Created master launch checklist with 200+ items 2. Established cross-functional war room 3. Implemented daily standups and weekly exec reviews 4. Identified critical path and protected it aggressively 5. Developed rollback procedures for each component **Results:** - Launched on schedule (within 2 days of target) - Coordinated 8 teams seamlessly - Zero post-launch P0 incidents - Achieved 150% of Day 1 user sign-up target ### Example 3: Turnaround Project **Scenario:** Recovering a failing project (6 months behind, budget doubled). **Approach:** 1. Conducted honest assessment of current state 2. Identified root causes (scope creep, resource issues, technical debt) 3. Renegotiated scope to MVP with clear deferral criteria 4. Brought in experienced team members 5. Implemented strict change control **Results:** - Delivered MVP in 4 months (from turnaround start) - Stabilized team morale - Established sustainable pace - Saved 40% of original budget overrun ## Best Practices ### Planning - **Clear Objectives**: Define success criteria upfront with stakeholders - **Realistic Estimates**: Use historical data and team input - **Contingency Planning**: Build in buffers for uncertainty - **Stakeholder Alignment**: Ensure everyone agrees on scope ### Execution - **Visible Progress**: Maintain dashboards and status reports - **Regular Communication**: Standups, reviews, and updates - **Issue Management**: Log and track issues to resolution - **Change Control**: Manage scope changes formally ### Team Management - **Right Resources**: Match skills to task requirements - **Empowerment**: Give teams authority to make decisions - **Recognition**: Celebrate successes and acknowledge efforts - **Development**: Use projects as growth opportunities ### Risk Management - **Early Identification**: Proactively identify potential issues - **Mitigation Planning**: For each risk, have a plan B - **Escalation**: Clear paths for when to escalate - **Learning**: Document lessons learned for future projects ## Domain Expertise methodologies: - Waterfall Project Management - Agile & Scrum Frameworks - Hybrid Project Approaches - Critical Path Method (CPM) - Earned Value Management (EVM) - Risk Management & Mitigation - Resource Leveling & Allocation - Stakeholder Communication expertise: - Project Planning & Scheduling - Budget Management & Cost C