sprint-task

Manage Scrum sprint tasks with approval gates and acceptance criteria verification.

1|Updated Mar 27, 2026

Search Tags:#scrum #approval gates #task lifecycle #task ownership #sprint task management

Ready to run

npx skills add https://github.com/alon21034/claude-scrum-skills --skill sprint-task

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-task
Source: https://github.com/alon21034/claude-scrum-skills/tree/main/sprint-task
Command: npx skills add https://github.com/alon21034/claude-scrum-skills --skill sprint-task

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps manage sprint tasks in a Scrum project, ensuring clear ownership, explicit approval gates, and a streamlined task lifecycle.

Core Features & Use Cases

Task Selection: Display available tasks and allow users to pick one or use a task ID.
Task Details: Show full task details, including acceptance criteria.
Approval Process: Ask for user approval before task implementation.
Implementation Verification: Verify acceptance criteria after implementation.
Task Status Updates: Update task status to review or close the sprint.

Quick Start

Run the following command to start a sprint task: /sprint-task

Frequently Asked Questions about sprint-task

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

FAQPage Schema

How do I manage sprint tasks with explicit ownership and approval gates in a Scrum workflow?▼

Sprint task management with explicit ownership uses a sprint.json file to track task selection, enforce approval gates before implementation, and verify acceptance criteria upon completion. Shell scripts parse JSON details and update task statuses to review or close the sprint.

What do I need to set up before starting sprint task management with shell scripts?▼

Sprint task management requires a sprint.json file containing your task details and acceptance criteria. You select a task from this file or input a task ID, after which the system displays full details and prompts for user approval before proceeding.

How does the task approval process work for sprint tasks in software development?▼

The task approval process explicitly gates implementation by displaying full task details and acceptance criteria, then asking for user approval. Shell scripting handles the status updates, ensuring no sprint task proceeds without this manual confirmation step.

Can I verify acceptance criteria automatically after completing a sprint task?▼

Acceptance criteria verification happens after task implementation, but the system relies on explicit approval gates rather than automated testing. It parses the sprint.json file to display the criteria, prompting a manual review before updating the task status to review or close.

How do I update task status to review or close a sprint using shell scripting?▼

Updating task status to review or close a sprint involves running shell scripts that parse the sprint.json file to verify acceptance criteria were met. After confirming explicit approval gates, the script modifies the task lifecycle state within the JSON data structure.

What are the limitations of using sprint.json for task lifecycle management in Scrum?▼

Task lifecycle management via sprint.json is limited to software development workflows that can provide this specific JSON file format. It relies on shell scripting for status updates and manual approval gates, lacking native integration with external Scrum platforms or automated CI pipelines.