agile-10-implement

Name: agile-10-implement
Availability: InStock
Author: cedricfarinazzo

Automate Jira sprint tickets from To Do to In Review in dependency order.

Updated May 16, 2026

Search Tags:#automation #agile #jira #pr #orchestrator #sprint #monitor

Ready to run

npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-10-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agile-10-implement
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-execution/skills/agile-10-implement
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-10-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomously orchestrates the end-to-end sprint implementation workflow by selecting Jira board work, ordering tickets by dependency, and driving each ticket from To Do to In Review with a chain of per-ticket sub-skills.

Core Features & Use Cases

End-to-end sprint orchestration: coordinates validate → plan → code → pr → review → monitor for each eligible ticket in Jira, in dependency order.
Autonomy with safety gates: proceeds with minimal human intervention, only escalating for truly critical decisions, and resumes across restarts via Jira markers.
Per-ticket sub-skills composition: builds PRs and code changes by composing the implement-* family, ensuring traceability and replayability.

Quick Start

Instruct the agent to run agile-10-implement on the active sprint board to begin executing from the current To Do queue to In Review.

Frequently Asked Questions about agile-10-implement

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

FAQPage Schema

How do I automate sprint implementation from Jira tickets to pull requests?▼

Autonomous sprint implementation orchestrates the end-to-end workflow by selecting Jira board work, ordering tickets by dependency, and driving each ticket from To Do to In Review through chained sub-skills.

What is autonomous sprint orchestration and how does it handle Jira ticket dependencies?▼

Autonomous sprint orchestration is an automated workflow that selects Jira board work, orders tickets by dependency, and sequentially drives each ticket from To Do to In Review using chained implement sub-skills.

Does autonomous sprint orchestration work with both Scrum and Kanban boards in Jira?▼

Yes, autonomous sprint orchestration is applicable to active sprints in both Scrum and Kanban boards, handling per-ticket execution, risk gating, and autonomous decision-making while preserving resumption via Jira markers.

How do I start an automated sprint workflow on an active Jira board?▼

To start the automated sprint workflow, instruct the agent to run the orchestration skill on the active sprint board, which begins executing tickets sequentially from the current To Do queue to In Review.

Can automated sprint execution resume if the workflow is interrupted or restarted?▼

Yes, automated sprint execution resumes across restarts using Jira markers, which preserve progress and allow the workflow to continue per-ticket sequential execution without losing prior state.

When should I avoid using autonomous sprint orchestration for Jira ticket execution?▼

You should avoid autonomous sprint orchestration when tickets require continuous parallel execution, as it enforces single-ticket sequential processing and only escalates to humans for truly critical decisions during risk gating.