From dbb76c9e3a85694fc038f434103405a73f00782e Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Tue, 14 Apr 2026 10:52:33 -0700 Subject: [PATCH] docs: add Karpathy compatibility note to README Positions gstack as the workflow enforcement layer for Karpathy-style CLAUDE.md rules (17K stars). Links to forrestchang/andrej-karpathy-skills. Maps each Karpathy failure mode to the gstack skill that addresses it. Co-Authored-By: Claude Opus 4.6 (1M context) --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 71c63cf5..69872622 100644 --- a/README.md +++ b/README.md @@ -236,6 +236,10 @@ Each skill feeds into the next. `/office-hours` writes a design doc that `/plan- **[Deep dives with examples and philosophy for every skill →](docs/skills.md)** +### Karpathy's four failure modes? Already covered. + +Andrej Karpathy's [AI coding rules](https://github.com/forrestchang/andrej-karpathy-skills) (17K stars) nail four failure modes: wrong assumptions, overcomplexity, orthogonal edits, imperative over declarative. gstack's workflow skills enforce all four. `/office-hours` forces assumptions into the open before code is written. The Confusion Protocol stops Claude from guessing on architectural decisions. `/review` catches unnecessary complexity and drive-by edits. `/ship` transforms tasks into verifiable goals with test-first execution. If you already use Karpathy-style CLAUDE.md rules, gstack is the workflow enforcement layer that makes them stick across entire sprints, not just single prompts. + ## Parallel sprints gstack works well with one sprint. It gets interesting with ten running at once.