bmad-github-dev-story

To automate GitHub issue implementation for BMAD stories, this Skill coordinates with the GitHub API and BMAD workflow definitions to resolve existing issues, linked PRs, and branches before executing the structured implementation flow.

GitHub serves as the primary source of truth for BMAD story implementation, providing authoritative data for acceptance criteria, definition of done, active status, branches, comments, and PR linkage, while BMAD local artifacts supply product context and traceability.

BMAD workflow integration resolves and resumes existing GitHub story issues by checking linked PRs and branches prior to implementation, ensuring accurate continuation and preventing conflicts with current active work.

Yes, interacting with the GitHub API and BMAD workflow definitions is required to automate dev story implementation, as these dependencies provide the necessary operational source of truth and execution flow context.

The best way to ensure consistent dev story implementation is to use an automated workflow that treats GitHub as the source of truth for status and criteria, integrating local BMAD artifacts for product context and traceability.

Yes, you can resume an incomplete GitHub story implementation because the Skill resolves existing work including active branches and linked PRs, combining GitHub status with BMAD local artifacts for accurate context.