envision

Opportunity framing transforms fuzzy ideas into precise product definitions by generating a Context Document. This document captures the opportunity, personas, capabilities, and MVP boundaries to enable faster team alignment.

A Context Document is a structured output capturing opportunity framing, personas, capabilities, and MVP boundaries. You need one to validate product direction and guide downstream workflows like mapping and design execution.

Defining MVP boundaries and success criteria requires framing the core opportunity and Jobs-to-Be-Done. This generates a Context Document containing target personas, capabilities, and key constraints for iteration.

Yes, split mode writes product framing outputs to product/index.yaml and product-context.yaml for downstream mapping. V1 mode writes only to product-context.yaml when a single file exists.

A Context Document feeds into mapping and design by providing structured outputs based on Context Schema templates. It guides downstream steps to decompose and execute the product plan with calibration plans.

Product framing works without prior dependencies by taking a fuzzy product idea as input. It identifies the core opportunity and produces a Context Document to validate direction before technical execution.