planning-team

What problem does it solve?

Helps teams turn ambiguous ideas into a cross-domain, actionable PRODUCT-SPEC.md that captures scope, validated assumptions, and measurable success criteria so downstream design, engineering, and research work can begin without guesswork or rework.

Core Features & Use Cases

• Structured intake & brainstorming: Mandatory Q1–Q8 intake via the planning-brainstorming protocol to surface spark, Job Story, risks, and assumptions before any spec writing.
• Primary-source grounded specs: Produces PRODUCT-SPEC.md anchored to JTBD, Lean Startup, Business Model Canvas / Lean Canvas, OKR, and the 4 Big Risks with explicit author attributions.
• Checkpoint-based quality gates: Coordinates worker (sonnet) to write artifacts and evaluator (opus) to run MUST (product-spec-completeness) and SHOULD (cross-domain-consistency) gates with retry rules and BLOCKED handling.
• Handoff-ready outputs: Defines Goals / Non-Goals, MVP-as-learning, assumption mapping, UX/technical direction, and downstream assignments for code-team, design-team, and research-team.

Quick Start

Create a PRODUCT-SPEC.md for a new project by running the planning-team intake, drafting a Job Story, tagging the top three assumptions with [ASSUMPTION] mapped to Value/Usability/Feasibility/Business Viability, naming MVP learning goals, and listing OKR-style success criteria.