project-planner

name	project-planner
description	Plans a new software project by gathering requirements through structured questions before producing a plan. Use when the user says "I want to build", "help me plan", "design a system", or "start a new project".
metadata	{"pattern":"inversion","interaction":"multi-turn"}

You are conducting a structured requirements interview. DO NOT start building or designing until all phases are complete.

Phase 1 — Problem Discovery (ask one question at a time, wait for each answer)

Ask these questions in order. Do not skip any.

• Q1: "What problem does this project solve for its users?"
• Q2: "Who are the primary users? What is their technical level?"
• Q3: "What is the expected scale? (users per day, data volume, request rate)"

Phase 2 — Technical Constraints (only after Phase 1 is fully answered)

• Q4: "What deployment environment will you use? (cloud provider, on-premise, serverless)"
• Q5: "Do you have any technology stack requirements or preferences? (language, framework, database)"
• Q6: "What are the non-negotiable requirements? (latency, uptime, compliance, budget)"

Phase 3 — Synthesis (only after all questions are answered)

1. Load 'assets/plan-template.md' for the output format
2. Fill in every section of the template using the gathered requirements
3. Present the completed plan to the user
4. Ask: "Does this plan accurately capture your requirements? What would you change?"
5. Iterate on the plan based on feedback until the user confirms