skills.rest
Scripsteam
ScripsteamOFFICIAL
Explore all skills by this author →
GitHub

be-sprint-runner

Orchestrate Jira stories, code changes, tests, security reviews, and PRs for .NET backend sprints.

Updated Aug 27, 2026
Search Tags:#automation#backend#dotnet#jira#ci-cd#sprint
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill be-sprint-runner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: be-sprint-runner
Source: https://github.com/Scripsteam/scrips-stack/tree/main/be-sprint-runner
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill be-sprint-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end execution of a backend sprint by orchestrating Jira stories, applying changes to the live codebase, running unit and integration tests, performing security reviews, and opening PRs with reviewer notifications.

Core Features & Use Cases

  • Autonomous sprint orchestration for .NET backends (Identity / API / FHIR / EF Core)
  • Reads Jira stories, codes against the live BE codebase, runs tests, and triggers PRs with templates
  • Mirrors admin-sprint-runner to cover backend workflows with zero human input

Quick Start

Run the be-sprint-runner in Claude Code to start an autonomous BE sprint execution.

Frequently Asked Questions about be-sprint-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate backend sprint execution from Jira stories to PR creation?▼

Backend sprint execution can be fully automated by reading Jira stories, coding against the live .NET codebase, running tests, and opening PRs. This Skill orchestrates the entire workflow autonomously across code, tests, and approvals.

Can I run autonomous sprint orchestration for a .NET backend with EF Core and FHIR stories?▼

Yes, autonomous sprint orchestration supports .NET backend stories involving Identity, API, FHIR, and EF Core. It automatically codes, tests, reviews, and opens PRs for these specific backend story types.

What is the best way to coordinate backend sprint tasks across Jira and CI-CD without human input?▼

Zero-human-input orchestration coordinates backend sprint tasks by integrating Jira transitions with live codebase changes, security reviews, and PR publication. It handles the entire CI-CD workflow autonomously.

Does backend sprint automation handle unit and integration tests automatically?▼

Yes, backend sprint automation runs both unit and integration tests automatically. It reads the Jira story, modifies the codebase, executes the test suites, and performs security reviews before creating the PR.

When should I use autonomous backend sprint automation for my Jira workflow?▼

Use autonomous backend sprint automation when your sprint requires hands-off coordination across code, tests, and approvals. It is designed for Scrips backend sprints involving .NET, Identity, API, FHIR, and EF Core stories.

Why does automated sprint execution include a security review step before opening a PR?▼

Automated sprint execution includes a security review step to ensure code quality before PR publication. This hands-off step validates the Jira story implementation alongside the live codebase changes, tests, and reviewer notifications.

Related Skills

Explore More Software Engineering Skills→
adobecomadobecom
1

start-ticket

Gather Jira context and analyze codebase structures for ticket work.

Official
Advanced
OreStudioOreStudio
25

autonomous-developer

Manage sprint backlog stories and deliver incremental code changes with tests and pull requests.

Official
Basic
congiuluccongiuluc

database-migration

Create, apply, and roll back EF Core database migrations for .NET applications.

Community
Advanced
Lobbi-DocsLobbi-Docs
18

jira

Automate Jira issue, sprint, board, and workflow tracking via API.

Official
Intermediate