rai-bugfix-start

This skill automates bugfix branch initialization by creating a dedicated bug branch from the development config, reproducing the issue, and committing a scope.md artifact that documents what, when, where, and done-when criteria for formal triage.

A bug reproduction scope artifact is a committed scope.md file defining what the bug is, when it occurs, where it manifests, and the done-when resolution criteria. You need one when tracked bugs require formal validation and documentation before investigation continues.

You initialize a formal bugfix workflow by reading development branch config, creating a deterministic bug/RAISE-{N} branch, reproducing the issue, and committing the work/bugs/RAISE-{N}/scope.md artifact to enable triage and handoff before further investigation.

Yes, this approach works with existing git development branch configurations by reading the development branch config deterministically to ensure the newly created bug branch is up to date before reproduction and scope generation begin.

The best way to automate bug triage handoff is to generate a scope.md artifact during branch initialization that documents the bug's what, when, where, and done-when conditions, producing formal artifacts ready for downstream triage and team handoff.

Your bugfix branch needs a reproduction step because formal bugfix pipelines require validation that the issue exists before investigation continues, ensuring the scope artifact accurately documents the problem for triage and downstream resolution work.