greenfield

Greenfield project planning generates a comprehensive PLAN.md by coordinating research, architecture, product management, and security perspectives. It processes BRIEF.md, asks clarifying questions, and synthesizes domain context, phased execution, and threat modeling into an aligned GSD-style execution plan.

Persona synthesis for product roadmap planning runs a Research phase first, then spawns Architect, Product Manager, and Security subagents in parallel. This multi-perspective approach covers design, delivery, and risk from day one to reduce early-stage uncertainty.

Aligning architecture, product, and security decisions requires synthesizing parallel expert outputs into a single execution plan. The process combines domain research, architecture design, product delivery phases, and threat modeling into PLAN.md, explicitly surfacing unresolved Tensions between disciplines.

Greenfield project planning requires BRIEF.md from the project root as input. If the file is absent, the system uses fail-soft behavior to prompt you to provide a brief interactively before generating research, persona outputs, and the final execution plan.

The architecture, product, and security outputs are fully reusable. The process writes architect.md, pm.md, security.md, research.md, and PLAN.md directly into the .wednesday/plans/ directory, providing structured output files for immediate consumption by other tooling.

Threat modeling for greenfield projects depends entirely on the domain context provided in BRIEF.md. If the initial brief lacks detail on integration points or compliance context, the fail-soft behavior triggers clarifying questions, which may slow down the generation of the final security.md and PLAN.md outputs.