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
Inside c8c
Matching workflows
Start with these workflows
Start with the flow that best matches the outcome you want.
When
You have a branch that feels close to ready and want one gated preflight pass before shipping.
Input
Repo and branch context, local or staging URL, auth or setup notes, and any risky areas that must be checked
Output
Approved preflight brief with code-review findings, QA evidence, and release recommendation
How
Runs gstack review on the current branch, verifies the resulting branch with report-only QA, merges both signals, and pauses for explicit approval
When
You need a no-code-change quality readout before deciding what to fix next.
Input
Repo path, base URL, auth or setup notes, must-cover journeys, and any flows to ignore
Output
Combined QA and design audit with concrete evidence and prioritized fixes
How
Sends one testing brief into gstack's QA and design-audit roles, then merges both perspectives into a single prioritized quality brief
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.