dev-sprint

Coordinate sprint workflows with plan.md, tracker.md, and changelog updates.

68|10|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/google/capsem --skill dev-sprint-google
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-sprint
Source: https://github.com/google/capsem/tree/main/skills/dev-sprint
Command: npx skills add https://github.com/google/capsem --skill dev-sprint-google

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Development teams often struggle with missing planning, unclear milestones, and scattered documentation across sprints. This Skill provides a disciplined, repeatable workflow to plan, track, and deliver features with proper changelog discipline and testing gates.

Core Features & Use Cases

  • Plan-first sprint design: Create a plan.md before coding to outline goals, dependencies, and milestones.
  • Progress tracking: Maintain tracker.md as a living checklist of tasks, blockers, and changes.
  • Release discipline: Enforce changelog updates and commit milestones to ensure traceability.
  • End-to-end sprint lifecycle: Guides from planning to verification and release, reducing rework.

Quick Start

Create a sprint directory and start by drafting plan.md and tracker.md, then implement changes and record progress in changelog.

Frequently Asked Questions about dev-sprint

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

FAQPage Schema
How do I manage agile sprint planning and track progress effectively?

Sprint planning and tracking work by drafting a plan.md to outline goals and milestones, then maintaining a tracker.md as a living checklist of tasks and blockers to ensure plan-first execution.

What is the best way to maintain changelog discipline during software development?

Changelog discipline is maintained by enforcing artifact-based milestones, structured commit guidance, and documentation updates tied directly to sprint phases, ensuring reliable and traceable feature releases.

How does a plan-first sprint workflow improve feature releases?

A plan-first sprint workflow improves releases by requiring a plan.md before coding, enforcing end-of-sprint testing gates, and tying changelog updates to milestones, which reduces rework and ensures traceability.

Can I use structured milestones for tracking blockers and changes in an agile sprint?

Yes, structured milestones support tracking blockers and changes by using a tracker.md artifact as a living checklist, updating it continuously alongside commit milestones and sprint phase documentation.

Do I need specific dependencies to enforce end-to-end sprint lifecycle tracking?

No specific dependencies are required to enforce end-to-end sprint lifecycle tracking; the workflow relies on generating and maintaining standard markdown artifacts like plan.md, tracker.md, and a changelog.