What problem does it solve? During long AL/Business Central feature builds, developers lose track of where the work stands: which task is next, which is blocked, and whether the plan still matches reality. This Skill reads the tasks/ folder, goal, codebase, and recent commits to name the concrete next move and act as the canonical replan venue. ## Core Features & Use Cases - Status board computation: Derives task state from frontmatter (status, depends_on, slice) via grep rather than a stored index, then routes each task to the right next skill (/al-refine, /al-implement, /al-code-review, /al-user-verification). - Eight replan triggers: Recognizes patterns like oversized tasks, hidden prerequisites, wrong ordering, and goal drift, then proposes structural mutations (split, insert, reorder, delete) applied only after explicit user acknowledgment. - Scope ledgers: Owns .out-of-scope/ for substantive rejections and .not-yet-specified/ for deferred questions, preventing re-litigation and silent scope absorption. - Use Case: Mid-feature, you ask "where are we?" and get a steering note naming that T-009 is blocked on a missing dependency edge, the slice owes a per-slice code review, and the next move is /al-code-review T-012. ## Quick Start Ask the assistant to run /al-steer and tell you where the current feature branch stands and what to do next.
