dev

You can automate git worktree lifecycle management by running an orchestration executor that selects ready-for-dev stories, creates isolated per-story worktrees, and delegates implementation to a development agent. It tracks in-progress sessions using lock files to prevent cross-session conflicts.

Prevent cross-session conflicts during parallel dev story workflows by using an orchestration executor that enforces isolated per-story worktrees and tracks active sessions with lock files. This ensures only one session operates on a story at a time.

A completion signal works by writing a structured output after story development finishes. This signal emits merge readiness data for downstream validation, allowing the Momentum pipeline to verify that the delegated dev story task completed successfully.

Orchestrating end-to-end Momentum story development does not require external dependencies. The executor operates independently to select ready stories, manage worktree lifecycles, and write completion signals, though it delegates actual implementation to the bmad-dev-story agent.

The best way to integrate isolated worktrees with a continuous development pipeline is to use an orchestration executor that manages the full worktree lifecycle and emits structured completion signals. This bridges automated story selection directly with downstream pipeline validation.

Dev story orchestration targets only ready-for-dev stories to ensure the automated workflow picks up actionable tasks. It selects stories that have cleared upstream planning, creates their isolated worktrees, and delegates them to the development agent for implementation.