Install ShipGlows

Install ShipGlows once. Stop losing time on the first move.

ShipGlows is the shortest serious path from “I have work to do” to “the right workflow is actually running.” You install one Codex plugin named shipglows, add the marketplace source once, and start with one plain instruction instead of memorizing a long command catalog.

Install ShipGlows now See what the router does

Who this is for

Founders, operators, and builders who want Codex to route real work more cleanly without starting every thread from scratch.

What changes after install

You get one public entrypoint that can answer directly, choose the right ShipGlows workflow, or ask one bounded clarification when the route is genuinely ambiguous.

You can also steer the AI with simple fast tags like #offer, #clarity, or #shipglows instead of rewriting the whole instruction.

Open the focus-tags cheatsheet

What this is not

Not a pile of disconnected prompts, and not a claim that the plugin already contains every private reference. It is the clean public starting layer.

1. Add the marketplace source

This tells Codex where the ShipGlows plugin marketplace lives in the public repository.

codex plugin marketplace add dianedef/ShipGlows --ref main --sparse .agents/plugins --sparse plugins/shipglows

2. Restart Codex

Restart Codex so the new marketplace source is loaded into the plugin directory.

3. Install the plugin

Open the plugin directory, choose the ShipGlows marketplace, then install the shipglows plugin.

4. Start with one plain instruction

The fastest first-success command is:

$shipglows help me choose the right workflow

First-run outcome

You do not need to decide between build, bug, deploy, content, or docs first.

The public plugin is intentionally lightweight, but it already gives you the part that matters first: a visible routing layer. ShipGlows can answer a simple question, choose the right workflow move, and keep the handoff visible in the main thread. When a workflow needs the fuller corpus, ShipGlows can route you there explicitly instead of pretending the plugin is something it is not.

Open the shipglows skill page Read the workflow cheatsheet

What happens in the first five minutes

Install the plugin, run one plain request, and let ShipGlows decide whether the next move is a build flow, bug loop, maintenance pass, release path, content workflow, design route, or a direct answer.

If you need the full corpus

Some workflows still need the optional complete ShipGlows source tree. The plugin can route you there explicitly when that happens.

If you want the pack roadmap

ShipGlows keeps one public plugin first. Internal packs remain packaging infrastructure until they are genuinely portable and ready for public installation.

Open the docs overview

If you are still evaluating

Read the public skill page first. It explains what the `shipglows` entrypoint actually does before you commit to the wider framework.

Open the shipglows page