Autonomous Decision Making
Medium
- Category
- Excessive Agency
- Content
**Path A vs Path B gate.** Routing depends on TWO signals: (1) did any *blocking* question fire before Phase 2.5? AND (2) what tier did Phase 0 classify? Blocking questions = scope disambiguation, dialogue probes, approach selection menus. Internal classification and pressure-tests do not count. - **Path A** — Lightweight tier AND no blocking questions fired → announce-mode. Emit "What we're building" prose only (no other sections, no confirmation question), then proceed to Phase 3 doc-write in the same turn. Lightweight Path A docs are short; post-hoc revision is cheap. - **Path B** — Standard/Deep tier OR any blocking question fired → full synthesis with confirmation gate. Two scenarios fire Path B: the user invested answer-time in dialogue, or pre-loaded substantive scope content. Either way, the substance earns a real checkpoint. The tier guard catches pre-loaded Deep brainstorms that would otherwise shortcut via the no-questions branch. **Keep tests per section.** Each conditional section has its own keep test; failing items dissolve into the internal draft only.
- Confidence
- 95% confidence
- Finding
- The skill explicitly allows a Path A flow that skips user confirmation and proceeds to write a design artifact in the same turn. Even though it limits this to 'lightweight' cases, this is still autonomous decision-making that can mis-scope work, create unwanted repository artifacts, and normalize acting without explicit user approval. In an agent workflow skill, silent progression is more dangerous because it can turn ambiguous requests into durable project documents without a checkpoint.