Your virtual software team, and the presentations it hands back.
gStack turns Claude Code into a team: a CEO who argues about scope, an engineering manager who reviews the plan, a QA tester who actually opens the site, a security officer who reads your code the way an attacker would.
Every one of them finishes the same way — a score, a scorecard, a decision, a report — and all of it stops at the edge of your terminal, where exactly one person ever sees it.
Bisque is the part that leaves. One more command turns what the run already produced into something your co-founder watches on their phone, in ninety seconds.
Each one is a different command, pointed at something public. Press play, then run the same two lines yourself.
/office-hoursgstack issue #990 · open, unansweredFour people independently built the same fix and not one of them merged. When the code already exists four times over, the thing actually missing is the decision.
/autoplanthe plan the office-hours run producedFour reviewers, three assumptions killed, and one judgment call it refused to make and handed back — because that one was taste, not code.
/qabisque.cloud · signed out, three screen sizesNo console errors, no broken images, first content in 418ms — and a page that computes to 417 pixels inside a 390-pixel phone, so it slides sideways under your thumb.
/csobisque-cloud/presenter · our own codeNo criticals in 2,207 lines, and one real bug the code comment insisted wasn't there. It turned up by running the code, not by reading it.
/retrogarrytan/gstack · 14–19 August 2026Twelve releases in six days, and the single biggest change removed 20,057 more lines than it added. One person merged all twelve; 38 others are credited inside them.
Add the Bisque skill
npx skills add bisque-cloud/presenterThen finish any run with
/present