spec-writing

To extract behavioral scenarios from rough intent, you can use a structured 5-round Given/When/Then/Verify interview process. This method captures intent, edge cases, failure modes, and decision points to produce a finalized scenario spec.

The best way to capture edge cases and failure modes is through a 5-round structured interview designed to uncover ambiguities and decisions. It systematically probes your feature description to ensure all behavioral scenarios are documented.

You generate input for PLAN.md by completing a structured behavioral scenario interview. The output is a finalized scenarios document containing the scenario list, ambiguities, and decisions required for Architect planning.

You need to run a Given/When/Then interview before initiating Pulse builds or when you first describe a new feature or system. It ensures rough intent is converted into executable scenario specs before architectural planning begins.

Scenario spec writing is designed to produce output specifically for Architect planning input. Without this downstream planning phase, the finalized scenarios document and identified decisions would not be utilized for PLAN.md creation.