draft-epic-expectation

Drafting testable expectations from an intent epic YAML file involves reading an existing intent triple and generating structured success scenarios and recovery entries directly into the expectations block atomically. This preserves all other fields verbatim while creating reviewer-verifiable outcomes.

Recovery planning for agentic workflows generates exactly one recovery entry per failure cause from an intent failure scenario, including routing for autonomous versus human handoff. It structures recovery within epic YAML files to ensure failures are reviewer-verifiable at the specify checkpoint.

Generating success scenarios from intent goals creates concrete then outcomes with a defined persona and a measurable verification signal. This process populates the expectations block by mapping the intent goal into reviewer-verifiable success criteria.

Overriding expectation generation rules and decision manifest paths is supported by providing optional parameters alongside the required epic path. The process reads these custom rules to draft expectations and emits a decision manifest recording mapping and handoff decisions.

Draft-epic-expectation works with existing intent epics produced by generate-intent-epics by validating the presence of an expectations stub before merging. It applies to the product layer for epic YAML files, ensuring expectations are ready for human approval.

Atomic read-merge-write updates for expectations blocks limit changes to filling only the expectations block in the existing epic YAML. This deterministic design requires a validated expectations stub and preserves all other fields verbatim, preventing partial or unstructured modifications.