bmad-loop-resolve

To resolve a CRITICAL escalation in a bmad-loop run, use an interactive resolution workflow that involves human input to clarify ambiguous specifications and enables story progression. You initiate this by running the resolve command with the specific story key.

The best way to update frozen specification files during a code review escalation is to use an interactive resolution workflow that automates spec file updates based on human disambiguation, allowing you to re-drive the story with corrected inputs.

Human-machine collaboration for specification resolution works by providing an interactive environment where human oversight guides informed decisions to disambiguate contradictions, ensuring the specification is correctly updated before resuming the process.

Yes, resolving bmad-loop escalations requires knowledge of the bmad-loop environment and its associated spec file structure, because the process involves updating frozen specification files to correct ambiguous inputs and resume story progression.

You need interactive session management for implementation reviews when a bmad-loop run encounters a CRITICAL escalation, such as a specification contradiction, requiring human input to disambiguate and update the spec to continue.