From 9ab24db252b5552a873dbd1772db9e6ea3a21d8a Mon Sep 17 00:00:00 2001 From: Doan Bac Tam Date: Wed, 25 Mar 2026 01:46:26 +0700 Subject: [PATCH 1/2] docs: add sprint flow diagram to README MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds a Mermaid flowchart showing the skill execution order and data flow between skills (design doc, test plan artifact, etc.) — placed before the skill table in "The sprint" section to give readers a visual map before the detail. --- README.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/README.md b/README.md index 253d54252..4928dca6d 100644 --- a/README.md +++ b/README.md @@ -138,6 +138,34 @@ gstack is a process, not a collection of tools. The skills run in the order a sp 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. +## Sprint sequence +```mermaid +flowchart TD + OH["/office-hours"] --> DD["design doc"] + DD --> CEO["/plan-ceo-review"] + DD --> ENG["/plan-eng-review — required gate"] + DD --> DES["/plan-design-review"] + CEO --> CODE["User + AI codes"] + ENG --> CODE + DES --> CODE + ENG --> QAP["test plan artifact"] + QAP --> QA + CODE --> REV["/review"] + CODE --> INV["/investigate"] + CODE --> CSO["/cso"] + REV --> QA["/qa"] + INV --> QA + CSO --> QA + QA --> SHIP["/ship"] + SHIP --> LD["/land-and-deploy"] + LD --> CAN["/canary"] + CAN --> DOC["/document-release"] + DOC --> RET["/retro"] + RET -- next sprint --> OH + + style ENG stroke:#E24B4A,stroke-width:2px +``` + | Skill | Your specialist | What they do | |-------|----------------|--------------| | `/office-hours` | **YC Office Hours** | Start here. Six forcing questions that reframe your product before you write code. Pushes back on your framing, challenges premises, generates implementation alternatives. Design doc feeds into every downstream skill. | From b282e94485c3d723f40278b3fe56a5990e1a9ab0 Mon Sep 17 00:00:00 2001 From: Doan Bac Tam Date: Wed, 25 Mar 2026 01:49:17 +0700 Subject: [PATCH 2/2] Update README.md --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4928dca6d..663aa05e1 100644 --- a/README.md +++ b/README.md @@ -139,23 +139,24 @@ gstack is a process, not a collection of tools. The skills run in the order a sp 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. ## Sprint sequence + ```mermaid flowchart TD OH["/office-hours"] --> DD["design doc"] DD --> CEO["/plan-ceo-review"] - DD --> ENG["/plan-eng-review — required gate"] + DD --> ENG["/plan-eng-review"] DD --> DES["/plan-design-review"] CEO --> CODE["User + AI codes"] ENG --> CODE DES --> CODE ENG --> QAP["test plan artifact"] - QAP --> QA CODE --> REV["/review"] CODE --> INV["/investigate"] CODE --> CSO["/cso"] REV --> QA["/qa"] INV --> QA CSO --> QA + QAP --> QA QA --> SHIP["/ship"] SHIP --> LD["/land-and-deploy"] LD --> CAN["/canary"]