From 49249d73170b64046a9a6ba38186d483f28047bd Mon Sep 17 00:00:00 2001 From: Trevin Chow Date: Sat, 18 Apr 2026 15:31:38 -0700 Subject: [PATCH] fix(ce-plan): run ambiguity gate before the non-software catch-all (#598) Co-authored-by: Claude Opus 4.7 (1M context) --- plugins/compound-engineering/skills/ce-plan/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/plugins/compound-engineering/skills/ce-plan/SKILL.md b/plugins/compound-engineering/skills/ce-plan/SKILL.md index 2ef260b..aa31970 100644 --- a/plugins/compound-engineering/skills/ce-plan/SKILL.md +++ b/plugins/compound-engineering/skills/ce-plan/SKILL.md @@ -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. -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. +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 Before asking planning questions, search `docs/brainstorms/` for files matching `*-requirements.md`.