skills.rest
YarikChekin
YarikChekinCOMMUNITY
Explore all skills by this author →
GitHub

new-sprint

Assemble the next sprint from PRD, backlog, and tech debt data.

Updated Mar 17, 2026
Search Tags:#planning#story#backlog#prd#sprint#tech-debt
One-click install
npx skills add https://github.com/YarikChekin/ralph-cc --skill new-sprint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-sprint
Source: https://github.com/YarikChekin/ralph-cc/tree/main/skills/new-sprint
Command: npx skills add https://github.com/YarikChekin/ralph-cc --skill new-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate next sprint by reading PRD, backlog, and tech debt, to detect what is already built, then assemble the next chunk of work into ready-to-implement user stories with minimal user input.

Core Features & Use Cases

  • Detects built work across PRD, backlog, tech debt, ideas, and archived sprints to determine what remains.
  • Identifies the next sprint target, archives the current sprint when appropriate, and preserves coding patterns for consistency.
  • Generates detailed stories with precise acceptance criteria, dependencies, and branch naming aligned to the project conventions.

Quick Start

Run /new-sprint to generate the next sprint from your PRD, backlog, and tech debt configuration.

Frequently Asked Questions about new-sprint

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

FAQPage Schema
How do I generate the next sprint from a PRD, backlog, and tech debt?▼

To generate the next sprint, you run the /new-sprint command. It reads your PRD, backlog, and tech debt data to detect completed work, then assembles the remaining chunk into ready-to-implement user stories with minimal input.

How does sprint planning handle archiving completed sprints and preserving coding patterns?▼

Sprint planning archives the current sprint when appropriate and preserves existing coding patterns. This ensures consistency across new user stories by referencing established project patterns and aligning branch naming conventions.

Can I use backlog and PRD data to automatically create user stories with acceptance criteria?▼

Yes, the three-source workflow integrates PRD, backlog, and tech debt data to generate detailed user stories. Each story is sized for a single context and includes precise acceptance criteria tied directly to the source data.

Do I need to manually define sprint readiness and prioritization trade-offs?▼

No, sprint readiness and prioritization trade-offs are determined automatically. The workflow identifies the next sprint target by analyzing PRD, backlog, and tech debt data to evaluate what remains and what trade-offs are needed.

What is the best way to detect what is already built across PRD, backlog, and tech debt?▼

The best way to detect built work is running the /new-sprint command. It identifies completed work across PRD, backlog, tech debt, ideas, and archived sprints to determine what remains for the next sprint.

Related Skills

Explore More Product & Management Skills→
farmountainfarmountain
1

Backlog Manager Agent

Prioritize product backlog items and generate sprint plans from capacity data.

Community
Advanced
omeragaakbasomeragaakbas

user-stories

Generate testable user stories with acceptance criteria for product features.

Community
Intermediate
elsa-workflowselsa-workflows
7.9k

speckit-git-validate

Validate Git branch naming conventions and verify associated spec directories.

Official
Basic
OreStudioOreStudio
25

agile-product-owner

Create and prioritize user stories across ORE Studio sprint and product backlogs.

Official
Basic