fix(ce-plan): run ambiguity gate before the non-software catch-all (#598)
Some checks failed
CI / pr-title (push) Has been cancelled
CI / test (push) Has been cancelled
Release PR / release-pr (push) Has been cancelled
Release PR / publish-cli (push) Has been cancelled

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Trevin Chow
2026-04-18 15:31:38 -07:00
committed by GitHub
parent d8e87c1790
commit 49249d7317

View File

@@ -82,10 +82,10 @@ If the plan already has a `deepened: YYYY-MM-DD` frontmatter field and there is
If the task involves building, modifying, or architecting software (references code, repos, APIs, databases, or asks to build/modify/deploy), continue to Phase 0.2. If the task involves building, modifying, or architecting software (references code, repos, APIs, databases, or asks to build/modify/deploy), continue to Phase 0.2.
Otherwise, read `references/universal-planning.md` and follow that workflow instead. Skip all subsequent phases. Named tools or source links don't change this routing — they're inputs, handled per Core Principle 8.
If the domain is genuinely ambiguous (e.g., "plan a migration" with no other context), ask the user before routing. If the domain is genuinely ambiguous (e.g., "plan a migration" with no other context), ask the user before routing.
Otherwise, read `references/universal-planning.md` and follow that workflow instead. Skip all subsequent phases. Named tools or source links don't change this routing — they're inputs, handled per Core Principle 8.
#### 0.2 Find Upstream Requirements Document #### 0.2 Find Upstream Requirements Document
Before asking planning questions, search `docs/brainstorms/` for files matching `*-requirements.md`. Before asking planning questions, search `docs/brainstorms/` for files matching `*-requirements.md`.