aped-lead

What problem does it solve?

It resolves pending Story check-ins across parallel sprint worktrees by running deterministic approval checks, approving what is safe, and escalating what needs human input—so your sprint pipeline advances without inconsistent state.

Core Features & Use Cases

• Parallel-sprint coordination: Reads the sprint graph and processes queued check-ins from Story Leaders at transition points (story-ready, dev-done, review-done), then pushes the next command back to the correct worktree.
• Guardrailed, programmatic auto-approvals: For DONE-only items, runs scripted checks via check-auto-approve.sh and uses its exit codes as the source of truth.
• Human-in-the-loop escalation: Treats dev-blocked as always ESCALATE, and for concerns or missing context (DONE_WITH_CONCERNS / NEEDS_CONTEXT) asks the user to decide or provides the blocking reason verbatim.
• Load-bearing review-done merge handling: Merges approved story PRs into the sprint umbrella in the correct order (capture/merge+poll/record merged flag/mark done/teardown), then instructs the user to run aped-ship later for the umbrella release PR.
• Safety and audit consistency: Enforces root-only execution, validates state integrity, and ensures every mutation goes through checkin.sh or sync-state.sh to preserve the audit trail.

Quick Start

Run aped-lead from the main project root when Story Leaders have posted pending check-ins so it can approve safe items and escalate the rest for your confirmation.