sprint-simulator

Guide engineers through an end-to-end sprint drill with worktrees and scoring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guided through a safe, end-to-end sprint drill to practice the four 24/7 primitives before touching real practitioner work.

Core Features & Use Cases

  • End-to-end sprint drill: guides the engineer through setup, worktrees, subagents, scoring, and review.
  • Onboarding readiness: helps new engineers build muscle memory before real practitioner work.
  • Structured scoring: provides a scorecard across worktree spawn, subagent dispatch, harvest discipline, cron setup, and goal hygiene.

Quick Start

Invoke as /sprint-simulator to start the guided dry-run.

Frequently Asked Questions about sprint-simulator

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

FAQPage Schema
How do I run a sprint drill for onboarding new engineers?

A sprint drill for onboarding new engineers is a guided end-to-end practice session that builds muscle memory for core workflows. You invoke the simulator to walk through setup, worktrees, subagents, scoring, and review before touching real practitioner work.

What is a worktree workflow and how does it fit into sprint practice?

A worktree workflow is a mechanism for managing isolated development branches during a sprint drill. The simulator requires it to safely guide engineers through setup and execution while scoring the worktree spawn as part of the final scorecard.

Do I need a real backlog ticket to start a sprint dry-run?

Yes, a real backlog ticket is required to start the sprint dry-run. The simulator uses this ticket alongside your worktree workflow and scoring mechanism to provide a structured scorecard across subagent dispatch, harvest discipline, and goal hygiene.

How does subagent dispatch scoring work in a sprint simulator?

Subagent dispatch scoring evaluates how effectively engineers assign tasks to subagents during the sprint drill. The scorecard captures this metric alongside worktree spawn, harvest discipline, cron setup, and goal hygiene to report overall readiness.

Can I use the sprint simulator for calibration sessions outside of onboarding?

Yes, you can use the sprint simulator for calibration sessions and general practice. It drills the four core primitives through a structured scorecard, making it applicable whenever engineers need to practice before taking on real practitioner tasks.

What are the limitations of running a sprint dry-run?

The sprint dry-run requires a real backlog ticket, a worktree workflow, and a scoring mechanism to function. Without these prerequisites, the simulator cannot guide engineers through the end-to-end practice or generate the structured scorecard.