From 8617d5d1e94a1a7750cbad9af49118ebb92b6988 Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Wed, 18 Mar 2026 09:31:34 -0700 Subject: [PATCH] docs: frame skills as a sprint process, not a tool collection MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Think → Plan → Build → Review → Test → Ship → Reflect. Each skill feeds into the next. 10-15 parallel sprints is the practical max. Co-Authored-By: Claude Opus 4.6 (1M context) --- README.md | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 01f2c2f4..86aeea66 100644 --- a/README.md +++ b/README.md @@ -99,7 +99,15 @@ You: /ship You said "daily briefing app." The agent said "you're building a chief of staff AI" — because it listened to your pain, not your feature request. Then it challenged your premises, generated three approaches, recommended the narrowest wedge, and wrote a design doc that fed into every downstream skill. Eight commands. That is not a copilot. That is a team. -## The team +## The sprint + +gstack is a process, not a collection of tools. The skills are ordered the way a sprint runs: + +**Think → Plan → Build → Review → Test → Ship → Reflect** + +Each skill feeds into the next. `/office-hours` writes a design doc that `/plan-ceo-review` reads. `/plan-eng-review` writes a test plan that `/qa` picks up. `/review` catches bugs that `/ship` verifies are fixed. Nothing falls through the cracks because every step knows what came before it. + +One sprint, one person, one feature — that takes about 30 minutes with gstack. But here's what changes everything: you can run 10-15 of these sprints in parallel. Different features, different branches, different agents — all at the same time. That is how I ship 10,000+ lines of production code per day while doing my actual job. | Skill | Your specialist | What they do | |-------|----------------|--------------| @@ -135,13 +143,13 @@ You said "daily briefing app." The agent said "you're building a chief of staff **`/document-release` is the engineer you never had.** It reads every doc file in your project, cross-references the diff, and updates everything that drifted. README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, TODOS — all kept current automatically. -## 10 sessions at once +## 10-15 parallel sprints -gstack is powerful with one session. It is transformative with ten. +gstack is powerful with one sprint. It is transformative with ten running at once. -[Conductor](https://conductor.build) runs multiple Claude Code sessions in parallel — each in its own isolated workspace. One session running `/qa` on staging, another doing `/review` on a PR, a third implementing a feature, and seven more on other branches. All at the same time. +[Conductor](https://conductor.build) runs multiple Claude Code sessions in parallel — each in its own isolated workspace. One session running `/office-hours` on a new idea, another doing `/review` on a PR, a third implementing a feature, a fourth running `/qa` on staging, and six more on other branches. All at the same time. I regularly run 10-15 parallel sprints — that's the practical max right now. -One person, ten parallel agents, each with the right cognitive mode. That is a different way of building software. +The sprint structure is what makes parallelism work. Without a process, ten agents is ten sources of chaos. With a process — think, plan, build, review, test, ship — each agent knows exactly what to do and when to stop. You manage them the way a CEO manages a team: check in on the decisions that matter, let the rest run. ---