implementing-as-sprint

Implement sprint briefs into code, tests, documentation, and pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tuvens/phased-development --skill implementing-as-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing-as-sprint
Source: https://github.com/tuvens/phased-development/tree/main/skills/implementing-as-sprint
Command: npx skills add https://github.com/tuvens/phased-development --skill implementing-as-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates the full execution of a sprint so an agent can turn a phase brief into working code, tests, documentation, and a review-ready pull request without losing track of orchestration rules.

Core Features & Use Cases

  • Sprint-driven implementation: Reads the sprint prompt, identifies acceptance criteria, and implements the requested scope incrementally.
  • Testing and regression discipline: Requires failing tests first, produces mandated TEST-RESULTS and REGRESSION-GUIDE artifacts, and preserves prior-phase invariants.
  • Cross-session orchestration: Manages status updates, signal handling, branch-shape differences, staging validation, and PR creation in long-running phased projects.
  • Use case: A Claude Code sprint agent receives a branch-specific prompt, builds the feature, validates it in staging, documents the outcome, and opens a properly scoped PR.

Quick Start

Use the implementing-as-sprint skill to read the sprint brief, implement the requested scope, validate the changes, and prepare the required testing artifacts.

Frequently Asked Questions about implementing-as-sprint

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

FAQPage Schema
How do I automate sprint execution to generate code, tests, and pull requests?

Sprint execution automation translates a sprint brief into working code, tests, and a review-ready pull request by applying incremental implementation, testing protocol compliance, and regression guide generation.

What is the best way to manage cross-session status tracking for phased software projects?

Cross-session status tracking for phased software projects manages signal-file handling, branch-shape detection, and staging validation to preserve prior-phase invariants across long-running agent sessions.

How do I prepare a sprint branch for staging validation and PR creation?

Preparing a sprint branch requires reading the sprint prompt, implementing requested scope incrementally, validating changes in staging, and documenting outcomes with mandated TEST-RESULTS artifacts before opening a properly scoped PR.

Does sprint-driven implementation require failing tests before writing feature code?

Sprint-driven implementation requires failing tests first, then produces mandated TEST-RESULTS and REGRESSION-GUIDE artifacts while preserving prior-phase invariants to maintain regression discipline.

Can I use branch orchestration for multi-session phased projects with Claude Code?

Branch orchestration applies to multi-session phased software projects needing turn-by-turn execution, status updates, staging validation, and pull request preparation using Claude Code sprint agents.

Why does sprint execution need branch-shape detection and signal-file handling?

Branch-shape detection and signal-file handling prevent orchestration rule loss during long-running phased projects by tracking status updates and preserving prior-phase invariants across cross-session execution.