E37: pre-flight plan review — surface plan conflicts as one batched question before Task 1

This commit is contained in:
Jesse Vincent
2026-06-11 14:54:55 -07:00
parent a2a4190809
commit c87f336cc0

View File

@@ -82,6 +82,20 @@ digraph process {
}
```
## Pre-Flight Plan Review
Before dispatching Task 1, scan the plan once for conflicts:
- tasks that contradict each other or the plan's Global Constraints
- anything the plan explicitly mandates that the review rubric treats as a
defect (a test that asserts nothing, verbatim duplication of a logic block)
Present everything you find to your human partner as one batched question —
each finding beside the plan text that mandates it, asking which governs —
before execution begins, not one interrupt per discovery mid-plan. If the
scan is clean, proceed without comment. The review loop remains the net for
conflicts that only emerge from implementation.
## Model Selection
Use the least powerful model that can handle each role to conserve cost and increase speed.