sprint-start

Audits sprint readiness by validating Definition of Ready tasks and story-map coverage in docs/ROADMAP.md.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/supermalang/ai-augmented-coding --skill sprint-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-start
Source: https://github.com/supermalang/ai-augmented-coding/tree/main/.claude/skills/sprint-start
Command: npx skills add https://github.com/supermalang/ai-augmented-coding --skill sprint-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents a sprint from starting until every planned task is truly ready, reducing churn, blocked work, and avoidable mid-sprint rework.

Core Features & Use Cases

  • Definition of Ready audit: Checks each planned task for required fields, criteria, dependencies, schema impact, risk, and wireframe coverage when needed.
  • Story-map gate: Verifies the user journey map is present and that any new journeys or gaps are either planned or explicitly deferred before sprint kickoff.
  • Sprint-state control: Renames the sprint heading in the roadmap only when the sprint is ready to begin and reports exact blockers when it is not.
  • Use case: A team can run this Skill at the start of planning to confirm the sprint is safe to launch and to surface missing story, design, or readiness details early.

Quick Start

Ask the sprint-start skill to review the next sprint in docs/ROADMAP.md and tell you whether it can begin or which readiness gaps must be fixed first.

Frequently Asked Questions about sprint-start

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

FAQPage Schema
How do I audit sprint readiness before starting a new sprint?

Sprint readiness audits check planned tasks against your Definition of Ready to verify required fields, dependencies, schema impact, and wireframes. This prevents blocked work and mid-sprint rework by surfacing missing details early.

What is a Definition of Ready in agile sprint planning?

A Definition of Ready specifies criteria that planned tasks must meet before a sprint begins, including required fields, dependencies, risk, and wireframe coverage. It acts as a hard gate to ensure work is truly actionable.

How do I enforce a release gate for new user journeys in a sprint?

Release gating for new user journeys verifies that the story-map is present and any gaps are planned or explicitly deferred before sprint kickoff. This ensures complete user journey coverage before work starts.

Can I prevent a sprint from starting if tasks are missing dependencies?

Yes, sprint kickoff controls can hard-gate the sprint from starting by validating task fields and dependencies. If planned tasks are missing required readiness details, the sprint heading is not marked in progress.

What do I need to validate a sprint roadmap before kickoff?

Validating a sprint roadmap requires read access to docs/ROADMAP.md and project context. The audit checks task fields, dependencies, and story-map coverage to confirm the sprint is safe to launch.

Why does my sprint have blocked work after kickoff?

Sprints experience blocked work when planned tasks lack readiness details like missing dependencies or schema impact analysis. Auditing tasks against the Definition of Ready before kickoff prevents this avoidable churn.