← ClaudeAtlas

correct-courselisted

Manage mid-sprint changes and pull deferred items forward into the active workstream. Use when the user says "correct course", "change of plans", "we need to adjust", or "something came up".
rterakedis/leanwheel-skills · ★ 2 · AI & Automation · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Correct Course Skill **Goal:** When discovery/requirements/bugs break plan, update `docs/`, `docs/epics/`, and backlog coherently. Every impact: fix now, schedule as story, or defer with date/condition. **Deferred problem:** `[Defer]` items in stories go nowhere. This skill pulls them forward and forces decisions. ## Activation Ask: "What triggered this?" 1. Requirement changed 2. Bug in done work 3. Architecture wrong mid-implementation 4. External dependency changed 5. Scope creep 6. Other Store trigger. Read `docs/epics.md` for status. --- ## Phase 1 — Triage the Trigger If `docs/project/decisions.md` exists, record the trigger there first (**PARK** from `skills/decision-log/SKILL.md`), then run the `/ideate` loop scoped to it — resolve only the questions this trigger raises, recording each impact decision with `source: /correct-course`. The recorded decisions are the triage output. (No decision log yet → assess inline as below; consider creating the log if the change is direction-setting.) Assess impact across: PRD (what/who), architecture (tech/patterns), epics (ACs/tasks/ordering), active story, done stories. Note what changes and why for each affected artifact. --- ## Phase 2 — Classify Each Impact `fix-in-place`: not implemented yet (ready-for-dev). Update docs/story directly. `new-story`: done/review work OR large fix. Don't reopen done stories; schedule new story instead (keeps history clean). `defer-explicitly`: real but out of scope. Must include: