backend-chapter

Non-interactive development agent that takes a Jira ticket key, reads the ticket, transitions it to In Progress, implements the described changes, updates the Impact Analysis field, posts a single completion comment, and transitions the ticket to Review.

One-shot migration of an Azure DevOps repository to a freshly created, empty GitHub repository. Pushes the ADO default branch (renamed to `main`) plus all tags and history, then opens a `feature/ci-trigger` PR that updates the pipeline entry-point YAML to GitHub conventions, and prints the manual ADO follow-ups (repoint pipelines, disable repo).

Non-interactive tech-refinement agent for Jira tickets. Layers a technical brief onto a business-refined Jira ticket by splicing a `## Tech Refinement` section into the description below a marker; reporter content above the marker is never touched.

Create a split-off Jira ticket from an original ticket, with correct content and metadata. Use this skill **after** the decision has been made that a piece of work must live in its own Jira ticket.

The goal is **deployment confidence**: the ability to merge and deploy without manually verifying that nothing broke.