sibyl-story-pick

Select and dispatch ready stories from SIBYL's committed story graph.

Updated Aug 27, 2026

Search Tags:#project management #dependency check #story selection #SIBYL #dispatch automation

Ready to run

npx skills add https://github.com/memorysaver/SIBYL --skill sibyl-story-pick

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sibyl-story-pick
Source: https://github.com/memorysaver/SIBYL/tree/main/apps/harness/skills/sibyl-story-pick
Command: npx skills add https://github.com/memorysaver/SIBYL --skill sibyl-story-pick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of selecting which story to run next in SIBYL's project cockpit, reducing ambiguity and ensuring a structured story-building flow.

Core Features & Use Cases

Story Selection: Agrees on which ready story to run next, based on the committed story graph.
Dependency Check: Ensures all dependencies are completed before a story is picked.
Dispatch Automation: Automates the creation of a git worktree and spawning an independent worker process for the selected story.
Use Case: When conducting the story-build phase in the project cockpit, use this Skill to select the next story to run by reading the product-context.yaml and calling the submit_story_pick tool.

Quick Start

Read the product-context.yaml and identify ready stories. Use the submit_story_pick tool to select a story or dispatch the ready wave.

Frequently Asked Questions about sibyl-story-pick

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

FAQPage Schema

How do I automate story selection and dispatch in project management workflows?▼

Story selection automation reads the committed story graph to agree on a ready story, then uses a harness to create a git worktree and spawn a worker process. This dispatch automation ensures a structured story-building flow by reducing ambiguity in choosing the next task.

What is the best way to check story dependencies before running a project wave?▼

Dependency check is built into the story selection process by reading the product-context.yaml file. It ensures all dependencies are completed before a story or wave is picked, preventing execution errors and ensuring only ready stories are dispatched to the worker process.

How do I select the next ready story from a committed story graph?▼

To select the next ready story, read the product-context.yaml file to identify stories with completed dependencies, then call the submit_story_pick tool. This selects an individual story or dispatches the entire ready wave based on the committed story graph.

Can I dispatch an entire wave of stories instead of picking them individually?▼

Yes, you can dispatch a ready wave by calling the submit_story_pick tool after reading the product-context.yaml. The dispatch automation creates a git worktree and spawns an independent worker process for the selected wave, streamlining the story-build phase.

Does dispatch automation create a separate git worktree for each story?▼

Yes, the dispatch automation uses a harness to create a git worktree and spawn an independent worker process for the selected story. This isolates the story-building environment, ensuring structured and conflict-free execution within the project cockpit.

Why does story selection require agreement on a story before running?▼

Story selection requires agreement to ensure the chosen story or wave aligns with the committed story graph and has all dependencies completed. This reduces ambiguity and maintains a structured flow before the harness creates a worktree and spawns the worker process.