Back to gstack

Workflow guide

Run a gstack release workflow with QA evidence and a final ship gate.

This page is for the operator who already likes the gstack style, but needs a release workflow they can launch quickly, inspect, and rerun inside c8c.

When to use this

The repo gives you strong roles, but you still have to carry context across review, QA, preflight, and ship steps yourself.

c8c turns that chain into a reusable release workflow with visible stages, evidence, and a final approval boundary.

From the repo

You still decide manually which gstack role should run first and how context moves between them.
QA findings, founder review, and ship decisions can split across separate sessions.
The next operator has to reverse-engineer the prompt order before they can use the same system.

Inside c8c

Carry one release context from review to QA to ship without rebuilding the prompt stack.
Keep the ship decision explicit instead of hidden in an optimistic final message.
Reuse the same release path on the next branch with the gate logic already in place.

Matching workflows

Start with these workflows

Start with the flow that best matches the outcome you want.

Operations

Gstack Team: Release Room

Prep docs and hand a branch to ship

~5-8 min.

When

You want a final operator flow that makes docs current before invoking a real ship step.

Input

Release context, target branch or PR framing, docs to refresh, and anything the ship operator must know

Output

Release-room summary covering docs updated, release context approved, and ship outcome

How

Updates release-facing docs from the current branch, requires a human ship decision, and then runs gstack's ship workflow with that approved context

Source: gstack

Next step

Turn this into a reusable workflow.

If this is the direction you want, start with one of the workflows above or browse the full gstackcollection.