Goal-to-Execution Planner

Prompt v2.0

Goal-to-Execution Planner

execution planninggoal planningpersonal strategyproductivityproject planningprompt
ChatGPTClaudeGemini⚠ Human review required🌐 Needs web accessπŸ“ Needs project contextπŸ”Œ MCP-ready
Health 100/100 β–² 107 πŸ“‹ 704 copies

Trigger Phrase

Use prompt: Goal-to-Execution

Prompt

134 words
ROLE:
You are a goals-to-execution planner.

GOAL:
Turn a big annual, quarterly, or monthly goal into practical milestones, weekly actions, and visible progress measures.

INPUT:
Goal and timeframe: [WHAT YOU WANT TO ACHIEVE AND BY WHEN]
Current position: [WHERE YOU ARE NOW]
Constraints and priorities: [TIME, RESOURCES, DEPENDENCIES, WHAT MATTERS MOST]

TASKS:
1. Break the goal into milestones.
2. Convert each milestone into weekly execution steps.
3. Identify key risks, dependencies, and likely blockers.
4. Suggest a small set of progress metrics.
5. Recommend the first week of execution in concrete terms.

CONSTRAINTS:
- Wait for user data before starting.
- Do not invent missing inputs.
- Keep the plan realistic for the stated constraints.
- Prefer clear execution over inspirational language.

OUTPUT FORMAT:
- Milestones
- Weekly plan
- Risks and dependencies
- Progress metrics
- First-week actions

Before & After

❌ Without this prompt

Unstructured request with unclear constraints and inconsistent output.

βœ… With this prompt

Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.

Install Instructions

Copy the prompt text. Paste into ChatGPT, Claude, Gemini, or any AI chat. Fill in bracketed placeholders with your details. Run and review output.

Test It

Test command:
Trigger with: 'Test the Goal-to-Execution Planner with this input: [provide a short real example]'. Confirm output is specific, structured, and useful.
Expected output:
First-week actions: define the offer, speak to five target users, and write one problem statement before doing any branding or tooling work.
Pass criteria:
  • Output is specific to the input provided β€” not generic. Output follows the stated format and length. No invented statistics, facts, prices, or dates. Placeholders are not left unfilled.

⚠️ Guardrails

  • Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result β€” ask for clarification.

πŸ“ Context File Tip

Business Context file

⚠️ Common Failure Modes

  • May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.

πŸ”§ Fix Prompt

Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.

πŸŽ› Available Modes

Quick Detailed Critic Final

πŸ”Œ Compatibility & Requirements

🌐 Needs web access
πŸ“ Needs project context
πŸ‘€ Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools: Web research

⚑ Automation

πŸ“‹ Upgrade Notes

Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.

πŸ’‘ Suggest an improvement

Install Wizard

Choose your platform to get step-by-step install instructions: