admin-sprint-runner

Automate admin sprint execution from Jira stories to pull requests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill admin-sprint-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: admin-sprint-runner
Source: https://github.com/Scripsteam/scrips-stack/tree/main/admin-sprint-runner
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill admin-sprint-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates end-to-end admin sprint orchestration, coordinating Jira stories, code generation against defined sources of truth, QA, security review, PR creation, and reviewer notifications.

Core Features & Use Cases

  • End-to-end sprint automation: orchestrates per-story execution, gating, and handoffs across frontend, backend, and QA.
  • Governed reviews & PR flow: ensures PR creation with proper reviews and security checks before merge.
  • Sources of Truth alignment: references Jira tickets, design/spec docs, and code repos to drive sprint execution.

Quick Start

Initiate an autonomous admin sprint by loading the sprint plan, mapping Jira stories, and starting the execution pipeline.

Frequently Asked Questions about admin-sprint-runner

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

FAQPage Schema
How do I automate end-to-end sprint execution from Jira stories to pull requests?

Sprint execution automation orchestrates per-story Jira ticket resolution, code generation, QA, security reviews, and deployment-ready pull request creation. It coordinates gating and handoffs across frontend, backend, and QA roles by referencing Jira tickets and spec docs as sources of truth.

What is autonomous sprint orchestration and how does it handle code generation?

Autonomous sprint orchestration coordinates the full development pipeline by mapping Jira stories to a three-layer source of truth. It drives code generation, enforces gated reviews, and creates pull requests while tracking outcomes and notifying reviewers.

How do I ensure QA and security reviews are gated before a pull request is created?

Gated reviews enforce mandatory QA and security checks before pull request creation. The sprint execution pipeline applies these gates per story, ensuring code generated against defined sources of truth passes security review before reviewers are notified.

Can I use Jira tickets and design specs as a source of truth for sprint automation?

Yes, sprint automation explicitly references Jira tickets, design documents, and code repositories as a three-layer source of truth. This structured workflow ensures generated code aligns with defined requirements before entering the QA and PR creation phases.

Does autonomous sprint execution handle frontend, backend, and QA coordination?

Autonomous sprint execution orchestrates per-story task completion across frontend, backend, and QA. It manages role-based handoffs, applies gating between phases, and aggregates outcomes to produce deployment-ready pull requests with explicit reviewer notifications.

What are the limitations of automating sprint execution with Jira and PR gating?

Sprint execution automation requires predefined Jira stories, design specs, and a three-layer source of truth to function correctly. It cannot generate code or create pull requests without these structured inputs and the explicit artifacts defined for its gated workflow.