mode-selector

# Mode-Selector Skill ## Status Heuristic v1 active (issue #291, shipped 2026-04-25). Wired into session-start Phase 7.5 (issue #292, shipped 2026-04-25). Backlog signal source live (issue #293, shipped 2026-04-25): `signals.backlog` is populated by `scripts/lib/backlog-scan.mjs::scanBacklog`. Accuracy feedback loop live (issue #294, shipped 2026-04-25): `scripts/lib/mode-selector-accuracy.mjs::recordAccuracy` writes a `mode-selector-accuracy` learning after the user confirms/overrides the Phase 7.5 banner. Phase B contract is **closed**. Phase C (#277) `/autopilot` Loop Command is the next epic and owns its own PRD. ## Purpose Mode-Selector centralizes the session-mode decision across all consumers: session-start Phase 1.5 banner, `/autopilot` (Phase C), and any future caller that needs a structured recommendation rather than ad-hoc heuristics inline at the call site. Before this skill existed, mode-picking logic was either implicit (user-typed free text) or embedded directly in session-start with no reuse path. Phase A (`state-md.mjs::parseRecommendations`, issue #272) established the `recommended-mode` frontmatter field written by session-end Phase 3.7a. Phase B is the skill that reads that field (plus future signals) and returns a structured recommendation. The key output is a four-field tuple: `{mode, rationale, confidence, alternatives}`. `mode` is the recommended session type. `rationale` is a ≤120-char human-readable explanation. `confidence` is a float (0.0–1.0)...