genisis0x 97584ef70b fix(autoplan): surface scope-detection counts and stop silent phase skips ... Phase 0 decides whether to run the Design (Phase 2) and DX (Phase 3.5) reviews by grepping the plan for scope terms with a 2-match threshold. Below the threshold the phase was dropped silently: the run reported only a yes/no, with no match count, no near-miss warning, and no way to override. A plan that is genuinely UI- or developer-facing but phrases its terms with hyphens (form-control), uses synonyms outside the list, or buries them in code fences grep skips would lose two whole review phases without the user ever knowing why. A scope sitting at exactly two matches is one edit away from silently disappearing on the next run. Report the match count per scope, flag a below-threshold scope as a near-miss instead of a clean no, call out the borderline exactly-two case, and offer an override so the user can force a phase regardless of the count. The Phase 0 output line now carries the counts and the override note. Closes #1957		2026-06-15 18:11:25 +05:30
..
SKILL.md	fix(autoplan): surface scope-detection counts and stop silent phase skips	2026-06-15 18:11:25 +05:30
SKILL.md.tmpl	fix(autoplan): surface scope-detection counts and stop silent phase skips	2026-06-15 18:11:25 +05:30