wa:dev-sprint

Execute tracker-defined engineering sprints in dependency order with state recovery.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:dev-sprint
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/dev-sprint
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates completing a tracker-defined sprint worth of engineering tasks while enforcing dependency order, persisting sprint state for recovery, and producing a completion report.

Core Features & Use Cases

  • Dependency-ordered sprint execution: Builds a task dependency graph from tracker “is blocked by” links and executes tasks in a topologically sorted order.
  • Stateful execution with recovery: Stores sprint state in the tracker Epic description and can resume after context loss by reading tracker Epic/task comments.
  • Quality-gated development workflow: Dispatches the appropriate developer agent per task prefix and runs simplification, quality gates, review, and (when applicable) integration QA before marking completion.

What problem does it solve?

  • Use case: After running /design-feature to generate a structured sprint in the tracker, use /dev-sprint to execute all sprint tasks in the correct order, commit changes in the right branches, and update the Epic with sprint completion + AC satisfaction.

Quick Start

Use wa:dev-sprint after /design-feature by running the command: /dev-sprint WA-100

Frequently Asked Questions about wa:dev-sprint

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

FAQPage Schema
How do I execute engineering sprints in the correct dependency order?

To execute engineering sprints in dependency order, this Skill builds a task dependency graph from tracker 'is blocked by' links and topologically sorts tasks. It then dispatches developer work sequentially to ensure blocked tasks wait for their dependencies.

What Git branching and PR discipline is enforced during sprint orchestration?

Sprint orchestration enforces Git branching and GitHub PR workflow discipline by requiring changes committed to correct branches. It validates tool health, runs quality gates, and executes reviews before marking any tracker task complete.

How do I generate sprint completion reports with acceptance criteria metrics?

To generate sprint completion reports with acceptance criteria metrics, this Skill validates 'Success Criteria' for each task during execution. It updates the tracker Epic with final completion status and AC satisfaction metrics at the end.

Does dev-sprint work with sprints generated by design-feature?

Yes, dev-sprint works with sprints generated by design-feature. You run '/dev-sprint WA-100' to execute the structured sprint tasks, maintain Git discipline, and update the Epic with completion metrics.

When should I not use automated sprint orchestration for task execution?

You should not use automated sprint orchestration if your tasks lack 'Success Criteria' or 'is blocked by' relationships in the tracker. It requires tracker-backed state persistence to validate stages and store execution progress.