sprint

Name: sprint
Availability: InStock
Author: drusifer

Coordinate a sprint lifecycle with gates, reviews, and handoffs.

1|Updated Jan 10, 2026

Search Tags:#workflow #planning #handoff #sprint #project-management #team-collaboration

Ready to run

npx skills add https://github.com/drusifer/via --skill sprint-drusifer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/drusifer/via/tree/main/agents/skills/sprint
Command: npx skills add https://github.com/drusifer/via --skill sprint-drusifer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the entire sprint process from planning to launch, ensuring structured reviews, phase gating, and consistent handoffs.

Core Features & Use Cases

End-to-end sprint lifecycle: planning, architecture review, phase breakdown, implementation, UAT, grooming, and launch.
Clear gates and handoffs: explicit approvals and recommended handoff commands to move between stages.
Documentation and artifacts: templates and chat-based handoffs stored for traceability.
Team alignment: enforces 1-3 task phases per sprint to prevent scope creep.

Quick Start

Begin with *plan sprint to start the cycle and follow gates through each phase.

Frequently Asked Questions about sprint

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

FAQPage Schema

How do I manage a complete sprint lifecycle from planning to launch?▼

To manage a complete sprint lifecycle from planning to launch, you orchestrate structured phases including architecture review, implementation, UAT, and grooming. The sprint process enforces 1-3 task phases per cycle to prevent scope creep and ensure predictable delivery through gated approvals.

What is the best way to structure handoffs between sprint phases?▼

The best way to structure handoffs between sprint phases is using explicit approval gates and recommended handoff commands. This stateful handoff management ensures cross-functional team alignment and stores documentation templates for traceability across the entire sprint workflow.

Can I use this sprint workflow for cross-functional software teams with specialized roles?▼

Yes, this sprint workflow is designed for cross-functional software teams that rely on structured roles. It coordinates gates, reviews, and handoffs across disciplines, applying disciplined phase breakdowns to ensure predictable delivery and consistent team collaboration.

How do I start a sprint cycle and move through the phase gates?▼

To start a sprint cycle and move through phase gates, begin with the plan sprint command to initiate the cycle. You then follow explicit gates through each phase, using recommended handoff commands to transition between architecture review, implementation, UAT, and launch.

Why does my sprint workflow suffer from scope creep and inconsistent reviews?▼

Sprint workflows suffer from scope creep and inconsistent reviews when they lack disciplined phase breakdowns and explicit gates. Enforcing 1-3 task phases per sprint, applying structured roles, and documenting handoffs prevents scope creep and ensures traceable, predictable delivery.

Does sprint planning work without dependencies or external components?▼

Yes, sprint planning works without dependencies or external components. The sprint lifecycle operates independently using documented workflows, explicit commands, and stateful handoff management to coordinate phases and team collaboration without requiring additional integrations.