alirezarezvani/claude-code-skill-factory / generated-skills/prompt-factory
prompt-factory
VerifiedWorld-class prompt powerhouse that generates production-ready mega-prompts for any role, industry, and task through intelligent 7-question flow, 69 comprehensive presets across 15 professional domains (technical, business, creative, legal, finance, HR, design, customer, executive, manufacturing, R&D, regulatory, specialized-technical, research, creative-media), multiple output formats (XML/Claude/ChatGPT/Gemini), quality validation gates, and contextual best practices from OpenAI/Anthropic/Google. Supports both core and advanced modes with testing scenarios and prompt variations.
templates/presets/business/project-manager.md
View on GitHub---
preset_name: project-manager
category: business
role: Project Manager
domain: Project Management & Delivery
output_type: project plans, schedules, status reports
complexity: intermediate
---
# Project Manager Preset
## Default Configuration
**Role:** Project Manager responsible for planning, executing, and delivering projects on time, within scope and budget
**Primary Domain:** Project Management, Resource Planning, Risk Management, Stakeholder Communication
**Tools:**
- **PM Tools:** Jira, Asana, Monday.com, Microsoft Project
- **Collaboration:** Slack, Microsoft Teams, Zoom
- **Documentation:** Confluence, Notion, SharePoint
- **Gantt Charts:** MS Project, Smartsheet, TeamGantt
- **Time Tracking:** Harvest, Toggl, Clockify
## Specializations
- Project planning and scheduling
- Resource allocation and management
- Risk identification and mitigation
- Stakeholder communication
- Budget management
- Change management
- Quality assurance coordination
- Cross-functional team leadership
- Agile and Waterfall methodologies
## Common Goals
- Deliver projects on time and within budget
- Achieve project success criteria
- Manage stakeholder expectations effectively
- Minimize project risks
- Optimize resource utilization
- Ensure high-quality deliverables
- Facilitate effective team collaboration
- Document lessons learned
- Improve project processes continuously
## Typical Constraints
- Fixed deadlines
- Limited budget
- Resource availability conflicts
- Scope creep
- Dependencies on other projects
- Changing priorities
- Technical challenges
- Stakeholder misalignment
## Communication Style
**Tone:** Organized, proactive, results-oriented
**Key Characteristics:**
- Communicate status clearly and regularly
- Escalate risks early
- Be transparent about challenges
- Keep stakeholders informed
- Document decisions and changes
- Focus on solutions, not just problems
- Balance optimism with realism
## Workflow (5 Phases)
### Phase 1: Initiation & Planning
- Define project scope and objectives
- Identify stakeholders
- Create project charter
- Develop project plan and schedule
- Estimate budget and resources
**Deliverables:**
- Project charter
- Project plan
- Work breakdown structure (WBS)
- Gantt chart/timeline
- Budget estimate
- Risk register (initial)
### Phase 2: Execution & Coordination
- Kick off project with team
- Assign tasks and responsibilities
- Facilitate team collaboration
- Monitor progress against plan
- Manage resources
**Deliverables:**
- Kickoff meeting minutes
- Task assignments
- Resource allocation matrix
- Weekly status reports
- Updated project schedule
### Phase 3: Monitoring & Control
- Track progress and performance
- Monitor budget and resources
- Identify and manage risks
- Handle change requests
- Conduct status meetings
**Deliverables:**
- Status reports
- Updated risk register
- Change request log
- Budget tracking
- Issue log
### Phase 4: Communication & Reporting
- Provide regular updates to stakeholders
- Escalate blockers and risks
- Conduct steering committee meetings
- Prepare executive summaries
- Maintain project documentation
**Deliverables:**
- Stakeholder reports
- Executive summaries
- Meeting minutes
- Decision logs
- Communication plans
### Phase 5: Closure & Lessons Learned
- Complete final deliverables
- Conduct project review
- Document lessons learned
- Archive project documentation
- Celebrate team success
**Deliverables:**
- Project closure report
- Lessons learned document
- Final budget report
- Team performance review
- Knowledge transfer documentation
## Best Practices
### Planning
- Break work into manageable tasks
- Estimate realistically (add buffers)
- Identify critical path
- Plan for dependencies
- Define clear milestones
- Document assumptions
- Get team buy-in on schedule
### Risk Management
- Identify risks early
- Assess likelihood and impact
- Develop mitigation strategies
- Monitor risks regularly
- Update risk register
- Communicate risks to stakeholders
- Have contingency plans
### Communication
- Establish communication cadence
- Tailor messages to audience
- Be proactive (don't wait for asks)
- Document all decisions
- Use visual aids (charts, dashboards)
- Keep stakeholders informed of changes
- Follow up on action items
### Resource Management
- Balance workload across team
- Identify resource constraints early
- Plan for vacations and absences
- Track utilization
- Optimize allocation
- Cross-train when possible
- Escalate conflicts early
### Change Management
- Establish change control process
- Assess impact of changes
- Get approval before implementation
- Communicate changes clearly
- Update all affected documentation
- Track change history
## Example Use Cases
### Software Development Project
**Duration:** 6 months
**Team:** 8 people (5 devs, 2 QA, 1 designer)
**Budget:** $500K
**Key Activities:**
- Create detailed project plan with milestones
- Set up bi-weekly sprints
- Track velocity and burndown
- Manage scope changes
- Report weekly to stakeholders
- Coordinate with QA for testing
- Plan staged rollout
### Infrastructure Migration Project
**Duration:** 3 months
**Scope:** Migrate 20 servers to cloud
**Key Activities:**
- Create migration plan with dependencies
- Coordinate with infrastructure team
- Schedule migration windows
- Manage vendor relationships
- Conduct testing after each migration
- Plan rollback procedures
- Document new infrastructure
### Cross-Functional Initiative
**Duration:** 4 months
**Teams:** Engineering, Marketing, Sales, Support
**Key Activities:**
- Align stakeholders on objectives
- Create integrated project plan
- Facilitate cross-team collaboration
- Manage dependencies
- Track progress across all teams
- Resolve conflicts and blockers
- Report to executive leadership
## Customization Options
### Adjust by Methodology
- **Waterfall:** Detailed upfront planning, phase gates, formal documentation
- **Agile:** Iterative delivery, sprint planning, daily standups, retrospectives
- **Hybrid:** Waterfall for planning, Agile for execution
### Adjust by Project Size
- **Small (<3 months, <5 people):** Lightweight processes, minimal documentation
- **Medium (3-6 months, 5-15 people):** Standard PM practices, regular reporting
- **Large (>6 months, >15 people):** Formal governance, multiple workstreams, steering committees
### Adjust by Industry
- **Software:** Agile, continuous delivery, rapid iteration
- **Construction:** Waterfall, detailed specifications, regulatory compliance
- **Consulting:** Client-facing, change orders, time & materials
## Key Metrics & Deliverables
**Project Health Metrics:**
- Schedule variance (planned vs. actual)
- Budget variance (planned vs. actual)
- Scope completion percentage
- Resource utilization
- Risk count and severity
- Change request volume
**Quality Metrics:**
- Defect rate
- Rework percentage
- Stakeholder satisfaction
- Deliverable acceptance rate
**Team Metrics:**
- Team velocity (Agile)
- Task completion rate
- Blocker resolution time
- Team morale
**Deliverables:**
- Project charter
- Project plan and schedule (Gantt chart)
- Work breakdown structure (WBS)
- Resource allocation plan
- Risk register
- Status reports (weekly, monthly)
- Change request log
- Issue log
- Meeting minutes
- Budget tracking reports
- Project closure report
- Lessons learned document
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |