team-sprint

Automate sprint cycles from planning through PR creation with Git workflows.

25|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/parhumm/jaan-to --skill team-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-sprint
Source: https://github.com/parhumm/jaan-to/tree/main/adapters/codex/skillpack/skills/team-sprint
Command: npx skills add https://github.com/parhumm/jaan-to --skill team-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating planning, execution, and reporting across multiple roles in software development is complex and error-prone; team-sprint automates the full sprint lifecycle from planning to PR, reducing manual coordination and race conditions.

Core Features & Use Cases

  • Automates sprint planning by invoking pm-sprint-plan and generating an execution queue.
  • Orchestrates team-work by spawning execution steps via team-ship and enforcing dependency order.
  • Generates cycle artifacts (sprint plan, gap reports, changelog updates) and creates a PR to dev with a summary.
  • Integrates with ROADMAP.md to mark completed items and track progress across cycles.
  • Supports focus filters (spec, scaffold, code, test, audit) and custom tasks for flexible cycles.

Quick Start

Start a new sprint cycle by running /team-sprint with optional focus and tasks parameters.

Frequently Asked Questions about team-sprint

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

FAQPage Schema
How do I automate sprint planning and pull request creation for Git development cycles?

Sprint planning and pull request creation can be automated by orchestrating end-to-end sprint cycles, generating execution queues, enforcing dependency order, and creating a PR to dev with a changelog summary.

What is the best way to coordinate team execution and track progress across multiple sprint phases?

Team execution and sprint progress tracking are coordinated by spawning execution steps via team-ship, enforcing dependency order, generating gap reports, and updating ROADMAP.md to mark completed items across cycles.

Can I use focus filters to run flexible sprint cycles for specific development tasks?

Yes, flexible sprint cycles can be run using focus filters like spec, scaffold, code, test, and audit, along with custom tasks, to tailor the automated end-to-end orchestration to your specific development needs.

Does sprint orchestration require a PR-based workflow and ROADMAP.md planning to function?

Sprint orchestration applies to software teams using Git, PR-based workflows, and ROADMAP-based planning, requiring these environments to execute its two-phase workflow with pre-execution checks and artifact tracking successfully.

Why do I need to integrate branch management and gap reporting into my sprint lifecycle?

Integrating branch management and gap reporting into your sprint lifecycle reduces manual coordination and race conditions by automating pre-execution checks, tracking artifacts, and updating changelogs during the development cycle.

What artifacts are generated when orchestrating end-to-end sprint cycles from plan to PR?

Orchestrating end-to-end sprint cycles generates artifacts including a sprint plan, gap reports, changelog updates, and a PR to dev with a summary, while ensuring branch management and artifact tracking.