story-orchestrator

Orchestrates parallel worker subagents to execute unblocked GitHub user stories in isolated git worktrees.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/jacobmiller22/chrishop --skill story-orchestrator-jacobmiller22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-orchestrator
Source: https://github.com/jacobmiller22/chrishop/tree/main/.agents/skills/story-orchestrator
Command: npx skills add https://github.com/jacobmiller22/chrishop --skill story-orchestrator-jacobmiller22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Coordinating multiple user stories across a monorepo manually is slow and error-prone: stories get picked that are still blocked, parallel changes collide in the same files, and completed work is accepted without verifying PRs, CI, or cleanup. This Skill automates the full fleet lifecycle from candidate selection through adversarial audit. ## Core Features & Use Cases - Shovel-Ready Candidate Discovery: Runs a Python script against the GitHub CLI to find open issues with no blockers, no assignees, and no in-progress/blocked labels, ranked by priority tier and delivery phase. - Parallel Worker Dispatch: Spawns worker subagents in isolated wt worktrees based on origin/staging, with model and thinking-level selection matched to story complexity, and conflict analysis to guarantee disjoint workspaces. - Chief Judge Adversarial Audit: Verifies each completed story across 7 criteria including PR-to-issue linking, passing CI checks, ephemeral preview deployments, worktree teardown, and monorepo typecheck integrity. - Use Case: A maintainer says "orchestrate the next batch of stories" and the Skill selects the top 3-5 unblocked GitHub issues, dispatches parallel workers to implement them, audits each PR, and delivers a consolidated fleet report with PR URLs and unblocked next steps. ## Quick Start Ask the agent to orchestrate the next batch of shovel-ready stories so it discovers unblocked GitHub issues, dispatches parallel workers in isolated worktrees, and audits their pull requests.

Frequently Asked Questions about story-orchestrator

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

FAQPage Schema
How do I run multiple GitHub issues in parallel with AI agents?

Run the story-orchestrator to discover unblocked issues, then it dispatches one worker subagent per story in an isolated git worktree. Each worker implements the issue, opens a PR targeting staging, and reports back for audit.

How does the orchestrator decide which GitHub issues are ready to work on?

The find_candidates.py script filters open issues via the GitHub CLI, excluding any with blocked, in-progress, completed, needs-refinement, or creator-review labels, any with assignees, and any whose declared dependencies are still open. Remaining issues are ranked by priority label first, then delivery phase.

Can parallel workers cause merge conflicts in the same files?

The orchestrator performs conflict analysis before dispatch, verifying that selected stories touch disjoint packages or directories. If two top candidates overlap, the lower-ranked one is deferred in favor of the next non-conflicting story.

What does the completion audit check before accepting a story?

The Chief Judge audit verifies 7 criteria: issue and PR lifecycle state, audit-trail comments, PR base branch and Fixes linking, passing CI checks, live ephemeral preview deployment, worktree teardown, and monorepo typecheck plus unit test integrity.

Does this work with branches other than staging?

No. The protocol mandates that all worktrees are created from origin/staging and all PRs target staging via gh pr create --base staging. Branching from production or main is explicitly prohibited by the repository's branching policy.