rally-mode

Coordinate an 11-phase test-driven sprint workflow with GitSync enforcement.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/wbic16/exo-plan --skill rally-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rally-mode
Source: https://github.com/wbic16/exo-plan/tree/main/process
Command: npx skills add https://github.com/wbic16/exo-plan --skill rally-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Rally Mode eliminates unfocused sprint work, inconsistent testing, and merge/stomp conflicts by prescribing a repeatable, 11-phase process that combines test-driven rewrites with a mandatory GitSync discipline to produce shippable increments reliably.

Core Features & Use Cases

  • 11-phase rally process: From requirements and Top-3 selection through v1/v2/v3 rewrites, E2E testing, staging, and production deploys.
  • GitSync protocol and enforcement: Pull/rebase cadence, AGENTS.md coordination, pre-push validation and helper scripts to avoid merge conflicts and lost work.
  • Automation helpers: Scripts to create rally checklists, run pre-push validations, and perform periodic Git status checks for active participants.
  • Use Case: A compact engineering team runs R18: they select top 3 features, implement v1, write tests, rewrite to v2/v3 with CI, validate on staging, and deploy with a documented sign-off.

Quick Start

Initialize a rally by running the provided rally-checklist script with your rally identifier to create and open the rally checklist for editing.

Frequently Asked Questions about rally-mode

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

FAQPage Schema
How do I manage sprint workflows with test-driven rewrites to avoid merge conflicts?

A rally development workflow coordinates an 11-phase process combining test-driven v1–v3 rewrites, E2E testing, and staging validation to eliminate unfocused sprint work and produce shippable feature increments reliably.

How do I start a rally sprint using the provided scripts?

To start a rally sprint, run the provided rally-checklist script with your rally identifier to automatically create and open a rally checklist for editing your team's focused development phases.

Does the rally workflow require existing CI pipelines and Git tracking to function?

Yes, the rally workflow requires basic CI, existing tests, and Git tracking to enforce GitSync discipline, ensure reproducible merges, and validate safe production releases.

Can my small engineering team use this for v1 to v3 feature rewrites and staging validation?

Small to medium engineering teams use this 11-phase process to select top 3 features, implement v1, write tests, rewrite through v2/v3 with CI, and validate on staging before production deployment.

What is the best way to coordinate GitSync pull and rebase cadence across multiple developers?

Coordinating GitSync cadence is best achieved using AGENTS.md coordination alongside helper scripts that perform periodic Git status checks and run pre-push validations for active rally participants.

When should I not use a structured rally process for sprint development?

Avoid using the rally process if your project lacks basic CI, automated tests, or Git tracking, as the workflow strictly depends on these to enforce pre-push checks and ensure reproducible merges.