greenfield-product

Greenfield product workflows are coordinated by a boundary router that directs raw ideas to the correct child skill, enforcing prerequisites and returning a single actionable artifact like a design doc or PRD.

You need a product workflow router when you have a raw product idea and must route it to the correct phase-specific skill, preventing inline execution and ensuring clean handoffs across the product-definition pipeline.

You route a product idea by providing it to the router and specifying the target child skill, such as startup-pressure-test for viability teardowns or requirements-writer for PRDs, ensuring phase prerequisites are met.

The greenfield product router validates frontmatter and references before routing to ensure a consistent discovery experience, maintaining boundary integrity and capturing rules for durable product-definition handoffs.

You cannot run child workflows like product-blueprint and system-architect inline; the boundary router prevents inline execution, surfaces the final artifact from the chosen child, and enforces prerequisite handoffs.