story-pr-orchestrator

Coordinates dependency-gated story delivery into isolated tasks, worktrees, branches, and pull requests.

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill story-pr-orchestrator-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-pr-orchestrator
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/story-pr-orchestrator
Command: npx skills add https://github.com/mintuz/.dotfiles --skill story-pr-orchestrator-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about story-pr-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a multi-story feature into separate pull requests?

Derive a dependency ledger from the spec that records each story's prerequisites, target base, and owned scope. Dispatch only stories whose prerequisites are already merged, giving each one an isolated task, worktree, branch, and PR.

How to coordinate multiple coding agents on one feature without conflicts?

Assign each story non-overlapping ownership of files and keep dependency tracking and integration order with a parent coordinator. Require each agent to acknowledge its base and owned paths before editing, and treat changes outside owned paths as scope exceptions.

When should a dependent story be dispatched for implementation?

A dependent story is ready only when every prerequisite is actually merged into the base it builds on. Approval, green checks, or an open PR on the prerequisite do not satisfy the gate.

Can this orchestrator handle a single story with no dependencies?

No, a single story with no dependencies is explicitly out of scope. The skill hands it to ordinary single-story delivery with one task, worktree, branch, and PR, without maintaining a dependency ledger.

What happens when a CI check fails during story delivery?

The exact failing job must be inspected before changing code or CI configuration. An instruction to ignore a failing or flaky check does not replace inspected evidence; without inspection the story is classified as blocked with the uninspected job named.

Does the orchestrator merge pull requests automatically?

No, merges require explicit user authorization. After an authorized merge, the base and PR state are refreshed and the dependency frontier is recalculated before newly ready stories are dispatched.