gstack
garry-tan‘s open-source (MIT) “AI software factory” — 23 specialized agent-skills + 8 power tools that turn Claude Code into a virtual engineering team. A flagship instance of the agentic-coding-harness, and a node that ties much of this wiki together. Tan’s framing: “the point isn’t who typed it, it’s what shipped.”
How it works
A structured sprint — Think → Plan → Build → Review → Test → Ship → Reflect — where each skill feeds the next (design docs inform reviews, test plans guide QA, shipping triggers doc updates). Roles are split across specialist agents: CEO, designer, eng manager, QA lead, security officer, release engineer.
- Commands:
/office-hours,/plan-ceo-review,/review,/qa(real-browser testing + bug-fixing),/design-shotgun,/cso(security),/ship,/document-release. - Parallel sprints via conductor — 10-15 simultaneous sessions.
- Memory via gbrain —
/setup-gbrain(PGLite / Supabase / remote MCP) and/sync-gbrainkeep persistent cross-session knowledge current.
Why it matters here
gstack is the convergence node of the burst: it composes agent-skills (23 of them), agent-orchestration (role-split agents), conductor (parallel sprints), and crucially gbrain (research-wiki’s knowledge base) — its Reflect step is compound-engineering (each sprint codifies learnings). It’s the clearest single example of this wiki’s agentic-coding-harness and its bridge back to research-wiki: the same author’s knowledge-base gbrain is the harness’s memory. (Caveat: README/founder claims.)
Related
garry-tan · gbrain · conductor · agent-skills · agentic-coding-harness · agent-orchestration · compound-engineering