aped-course

What problem does it solve?

It prevents chaotic, inconsistent scope changes by turning a mid-pipeline pivot into a controlled “course correction” that validates state, updates upstream artifacts, and forces explicit user confirmation before destructive effects.

Core Features & Use Cases

• Managed pivot with guardrails: Validates enabled state and pipeline integrity, detects stale locks, and coordinates a safe transition so parallel-sprint worktrees do not silently drift.
• Impact-aware scope execution: Assesses whether changes are minor (feature add/remove) or major (architecture/pivot), then updates PRD, epics, stories, and state accordingly.
• Auditability and continuity: Records ticket sync context (when applicable), appends corrections using the state schema, invalidates epic context caches when needed, and clears the upstream lock safely.

Quick Start

Use aped-course when you want to change scope (for example, “correct course: switch priorities and update the PRD, epics, and affected stories for a new OAuth requirement”).