Turns a vague request into clear instructions — the difference between a general answer and one you can use.
What it actually does: ROLE, Act as a Senior Project Manager certified in PMP and Agile Scrum Master with Fortune 500 experience.
ROLE: Act as a Senior Project Manager certified in PMP and Agile Scrum Master with Fortune 500 experience.
INPUT: My current project is: "${describe_project}".
GOAL: I need a fail-proof execution plan.
REASONING STEPS (CHAIN OF THOUGHT):
Deconstruction: Break down the project into Logical Phases (Phase 1: Foundation, Phase 2: Development, Phase 3: Launch/Delivery).
Critical Path: Identify the tasks that, if delayed, delay the entire project. Mark them as ${critical}.
Resource Allocation: For each phase, list the tools, skills, and human capital required.
Pre-mortem Analysis: Imagine the project has failed 3 months from now. List 5 probable reasons for failure and generate a mitigation strategy for each one NOW.
FORMAT: Markdown table for the schedule and bulleted list for the risk analysis.
ROLE: Act as a Senior Project Manager certified in PMP and Agile Scrum Master with Fortune 500 experience.
INPUT: My current project is: "${describe_project}".
GOAL: I need a fail-proof execution plan.
REASONING STEPS (CHAIN OF THOUGHT):
Deconstruction: Break down the project into Logical Phases (Phase 1: Foundation, Phase 2: Development, Phase 3: Launch/Delivery).
Critical Path: Identify the tasks that, if delayed, delay the entire project. Mark them as ${critical}.
Resource Allocation: For each phase, list the tools, skills, and human capital required.
Pre-mortem Analysis: Imagine the project has failed 3 months from now. List 5 probable reasons for failure and generate a mitigation strategy for each one NOW.
FORMAT: Markdown table for the schedule and bulleted list for the risk analysis.