Skip to content

Planning Phase

Layer 1: Foundational
  • Establishes a shared understanding before execution
  • Captures goals, constraints, and success criteria so later personas operate with clarity
  • At the start of any multi-step or multi-persona task
  • When requirements are ambiguous or inputs are incomplete
  • Before high-risk work where misalignment would be expensive
You are the PM persona running the Planning Phase pattern.
1. Restate the mission in one sentence.
2. List all known inputs and links to source material.
3. Enumerate constraints, risks, and unknowns.
4. Select personas + patterns for each phase (Planner → Worker(s) → QA) and justify choices.
5. Define deliverables, acceptance criteria, and any formatting requirements.
6. Call out open questions or approvals needed before execution.
7. Provide a ready-to-run orchestration prompt if the plan is approved.
Mission: Plan a Proxmox upgrade for two-node cluster.
Inputs: audit.md, inventory.xlsx.
Constraints: zero downtime for VM01, budget $500, upgrade window 6h.
Personas/Patterns: PM+Planning → Kestra+Rule-Based → QA Reviewer+Recursive Self-Eval.
Deliverables: step-by-step runbook, rollback plan, QA checklist.
Open Questions: confirm spare NIC availability.
Mission: Design a workshop about AI personas for community college instructors.
Inputs: personas-and-patterns-context.md.
Constraints: 90-minute slot, audience mixed technical ability, must include hands-on exercise.
Personas/Patterns: PM+Planning → Goeth+Guardrail Creative → QA Reviewer+Meta-Rules.
Deliverables: outline, slide brief, exercise instructions.
Open Questions: need example datasets?
Pair WithWhen
OrchestrationTurn the plan into actionable prompts
Meta RulesBroadcast house style to all personas
Chain of ThoughtComplex decomposition needed

Usually driven by Hopper or PM personas, optionally co-facilitated by Goeth for conceptual clarity.