---
title: "Bisque gstack"
description: "Your gstack team can present their work."
canonical: https://bisque.cloud/docs/gstack
---

# gstack

Your gstack team can present their work.

Page: https://bisque.cloud/docs/gstack
Install: `npx skills add bisque-cloud/presenter`

`npx skills add bisque-cloud/presenter` copies the Agent Skills into any agent's skills directory. In Claude Code you can install them as a plugin instead, from a terminal: `claude plugin marketplace add bisque-cloud/presenter`, then `claude plugin install presenter@bisque-cloud`. The plugin's skills are `/presenter:present`, `/presenter:watch` and `/presenter:video`.

Every [gstack](https://github.com/garrytan/gstack) command ends with a report
in your terminal: a reviewed plan, a bug list, a security audit, the week in
review. `present` turns that report into a narrated presentation, so you can
sit back and watch it instead of scrolling it. The finding comes first, then
the reasoning, then the evidence, in a few minutes.

It's a link, so if someone else needs the same thing, you send it to them.

Skills stack. Put `/present` on the same line as any gstack command and the
report gets presented as soon as it's written.

## See it work

> **You:** /retro /present
>
> **Agent:** Twelve merges this week, 765 files touched. Ship of the week: …
>
> Presenting that. Eight slides, four minutes.
> https://bisque.today/p/you/the-week-of-august-19
>
> **You:** I'm sending this to my investors. Start with what shipped, skip
> the file names, and get it under three minutes.
>
> **Agent:** Reordered, five slides, 2:40. Same link. Want it public, or
> keep it unlisted for just them?
>
> **You:** unlisted

Sit back while the agent's work is presented to you. If someone else needs
it, send them the link.

## What each stack becomes

| Type                     | You watch                                                                              |
| ------------------------ | -------------------------------------------------------------------------------------- |
| `/retro /present`        | The week: what shipped, what to fix, what to do differently next week                  |
| `/office-hours /present` | The idea you brought, the premises it challenged, three approaches, and the assignment |
| `/autoplan /present`     | The plan after four reviews, what each reviewer changed, and the calls left to you     |
| `/qa /present`           | Every bug it found, the screenshot for each, and which ones it already fixed           |
| `/cso /present`          | Findings ranked by severity and confidence, what was checked and came back clean       |
| `/ship /present`         | What went out, the tests that ran, and the link to the pull request                    |

The presentation is built from the report the command already produced. There
is nothing extra to write.

## Changing it

The agent republishes to the same link, so anything you already sent keeps
working.

| You want                       | Say                                       |
| ------------------------------ | ----------------------------------------- |
| It shorter                     | "get this under two minutes"              |
| The finding first              | "open on the biggest bug, then the rest"  |
| Less detail for a non-engineer | "this is for the CEO, cut the file names" |
| A slide reworded               | "slide three is too long, cut it in half" |
| A file for Slack or YouTube    | "make that a video I can upload"          |

## The first time

The first `/present` signs you in, asks you to pick a handle, and asks you to
pick a voice. The voices are downloads, from a few hundred megabytes to a few
gigabytes, so the first presentation takes a few extra minutes. Every one after
that goes straight from command to link.

## Where it fits

This page is about stacking `present` onto gstack. For everything else it can
do, and what to say when something looks wrong, see [present](/docs/present).
For turning the link into a file, see [video](/docs/video).