Ship the work.
Keep the judgment.
gstack is a set of specialist workflows for the whole engineering loop — from understanding the real product to a release you can verify. This tiny deck is a demonstration of the /deck skill itself.
An AI agent is better with a crew around it.
The model can write code. gstack gives the work a repeatable rhythm: a product lens, an architecture lens, a designer's eye, a QA lead, and a release gate.
Core promise judgment at every handoffStart with the real thing.
Before a plan, see the site, product, routes, constraints, and evidence. The first move is not “pick a framework”; it is “understand what exists.”
Use /browse for the live flow; use /scrape when structured evidence is the job.
/investigate traces symptoms to a root cause before anyone edits the code.
Access, privacy, and deployment choices become explicit instead of accidental.
Turn a vague request into a decision.
The planning skills force the useful questions early: what matters to the user, what is technically true, what should be beautiful, and what can wait.
/plan-ceo-review finds the sharpest product hiding in the request.
/plan-eng-review closes architecture and edge-case gaps.
/plan-design-review turns taste into an explicit bar.
/plan-devex-review tests the path a real person must take.
Make the important path feel obvious.
Specialists are useful when their output is a handoff, not a performance. Build the product, the design system, the deck, or the diagram with the next reviewer already in mind.
Prefer the actual workflow, screenshot, interaction, or evidence over feature-card fog.
Mobile is a composition with its own hierarchy, not a desktop layout squeezed narrower.
Deep links, keyboard controls, readable contrast, and focus states are part of “done.”
Confidence comes from seeing it fail.
A green unit test is not a usable product. gstack puts real browser behavior, visual review, security, performance, and staff-level review in the same loop.
/design-review catches density, clipping, hierarchy, and AI-slop patterns.
/qa opens the real browser, finds bugs, and re-verifies the fix.
/review, /cso, and /benchmark look for the failures CI cannot see.
Release with a receipt.
The finish line is not “merged.” It is a change that has been reviewed, deployed through the project's real path, and checked where users will meet it.
Run the repository's tests and source review before the PR leaves the workspace.
Direct links, refreshes, assets, headers, and the normal site path all get checked.
/canary monitors the live surface after deployment instead of declaring victory early.
Every release should make the next one smarter.
Context survives the session. Retros turn the work into better defaults. Documentation closes the loop for the next human and the next agent.
This is a static demonstration of gstack's workflow. It makes no network requests, collects no analytics, and contains no product-specific customer evidence.