sibyl-story-pick

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.

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.

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.

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.

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.

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.