rally

Coordinate an 11-phase development rally from requirements to production deployment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This rally process provides a structured, repeatable framework to move ideas from spec to production in a single, managed session, reducing chaos and misalignment across teams.

Core Features & Use Cases

  • A clearly defined 11-phase lifecycle from requirements to recap, including artifacts and milestones for each phase.
  • Supports artifact generation, phase gates, and collaboration among product, engineering, and QA to ensure verifiable progress.
  • Use Case: When starting a new feature, run a rally to lock requirements, select top 3, implement v1, write tests, rewrite, and prepare for staging & release.

Quick Start

Kick off and run a complete 11-phase rally in a single session to move requirements from spec to ship.

Frequently Asked Questions about rally

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

FAQPage Schema
How do I run a phased development cycle to ship features in a single session?

A phased development cycle moves features from spec to ship by executing an 11-phase rally within a single session. This process coordinates requirements, implementation, tests, rewrites, and production deployment through enforced phase gates and documented artifacts.

What is an 11-phase rally in release management?

An 11-phase rally is a structured, repeatable lifecycle framework for release management that guides product and engineering teams from initial requirements through final recap. It enforces standard deliverables and milestones at each phase to reduce chaos and misalignment across teams.

How do I enforce phase gates and artifact generation during project management?

Enforcing phase gates during project management requires a formal rally process that validates documented artifacts before advancing. This ensures verifiable progress across product, engineering, and QA collaboration milestones like requirements locking, test writing, and staging preparation.

Does the rally process work for locking requirements and selecting top 3 features?

Yes, the rally process explicitly supports locking requirements and selecting top 3 features during its initial phases. It structures these early project management steps to ensure alignment before proceeding to v1 implementation and rewrite phases.

Can I use a single-session rally to coordinate QA tests and staging preparation?

Yes, you can coordinate QA tests and staging preparation within a single-session rally. The framework integrates test writing, rewrites, and production deployment milestones sequentially, allowing product teams and engineering orgs to manage the entire development cycle cohesively.