What problem does it solve? Delivering a multi-story feature as a set of pull requests is error-prone: stories get dispatched before their prerequisites merge, agents duplicate or collide on the same files, and merges happen without verified evidence. This Skill enforces a dependency frontier so each story ships only when every prerequisite is actually merged. ## Core Features & Use Cases - Dependency Ledger: Derives story boundaries, acceptance criteria, and dependency edges from specs and task lists, marking each story ready or blocked with cited evidence. - Isolated Dispatch: Assigns one task, worktree, branch, and PR per ready story with a full brief covering source SHA, acceptance scope, invariants, and required verification. - Evidence-Based Monitoring: Tracks CI checks, review feedback, and diffs, classifying stories as working, blocked, or verified-ready only after inspecting actual evidence. - Use Case: You have an approved spec with five interdependent stories. Use this Skill to build the dependency ledger, fan out the two independent stories to isolated agents, and hold the rest until their prerequisites merge. ## Quick Start Use the story-pr-orchestrator skill to break this approved spec into dependency-gated story PRs and coordinate their delivery.