exploring

To extract ambiguous product decisions before planning, run a Socratic exploration process that surfaces gray areas one question at a time. This locks your product decisions into a structured context document before any research or coding begins.

A context document for feature planning is an authoritative record of locked implementation and product decisions with stable IDs and cited code paths. You need it when a new feature request has fuzzy requirements that require systematic gray area identification.

Prevent hidden assumptions during software refactoring by enforcing a hard gating process that blocks planning and coding until a reviewer validates all extracted decisions. This ensures an auditable handoff state before implementation starts.

Yes, you can use a phased Socratic questioning process to surface gray areas in fuzzy requirements. It enforces one-question-at-a-time gating to extract explicit answers and writes them to a concrete context markdown file.

The best way to lock decisions for downstream planning agents is to generate a context markdown file with stable decision IDs and update a shared state file. This gated handoff provides an auditable record that validating agents can act on.