RomanNum3ral
/
gstack
mirror of https://github.com/garrytan/gstack.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: add sprint flow diagram to README 

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.
This commit is contained in:
Doan Bac Tam 2026-03-25 01:46:26 +07:00 committed by GitHub
parent 6156122571
commit 9ab24db252
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
README.md
View File

@ -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. 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 | | 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. | | `/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. |