Problem
What problem this solves
A user can lose momentum before work starts by having to choose between build, bug, maintenance, content, design, deploy, skill, and audit workflows.
Menu Open navigation menu Close navigation menu
Plan & Decide Featured
Skill Detail
shipglows
Start with one plain instruction and let ShipGlows choose the right workflow.
The primary non-technical router for answering questions, executing deterministic micro-edits directly, or handing substantive work to the right ShipGlows skill.
Outcome
What changes when it works
You get one first command that answers directly, performs deterministic micro-edits with focused validation, routes substantive work to the right ShipGlows skill, or asks one numbered clarification question when no context-safe route exists.
Why It Matters
What this changes for a solo founder
The router keeps the first move simple. You describe the business or product need, and ShipGlows chooses whether the work is conversation, build, maintenance, bug, release, content, design, skill maintenance, or audit. The router also steers requests into product-aware content and docs paths when declared products or public claims are part of the work.
When to use it
- When you want the recommended first command and do not know which skill to launch
- When the request might be a feature, bug, maintenance run, content task, design task, deploy proof, skill change, audit, or simple question
- When you want the selected master skill to own its normal lifecycle after routing
- When you want the first answer to preserve product coherence instead of treating claims or surfaces as incidental
What you give it
- A plain-language instruction
- Any known target file, feature, bug symptom, deployment, content surface, or audit concern
What you get back
- A direct conversational answer for pure questions
- Direct execution with focused validation for deterministic micro-edits
- A direct main-thread handoff to the selected skill for substantive work
- One numbered question when the route is ambiguous
- No hidden master-skill-in-subagent nesting
- A route that keeps product governance, claims, and surface coherence visible when the task touches shipped or market-facing material
Typical examples
- shipglows explain which docs govern skill runtime
- shipglows fix the checkout bug
- shipglows prepare this change for deploy proof
Limits
- It does not replace the selected skill's lifecycle gates
- It uses context-safe defaults only when they are clear, low-risk, reversible, and verifiable
- It asks a numbered question with the reason and recommended route instead of guessing when routing is ambiguous
- It does not run master skills inside hidden subagents
Arguments
Some arguments change the workflow, not just the wording.
These are the argument switches documented for this skill. For the general rule behind skill arguments, read the skill modes tutorial.
<instruction>
Classifies the request and either answers directly, executes a deterministic micro-edit directly, or hands the main thread to the selected ShipGlows skill.
Consequence
Routes feature/code/docs to sg-build, mixed build-plus-customer requests to sg-build first with a post-build sg-customer gate, maintenance to sg-maintain, bugs to sg-bug, release/deploy/prod proof to sg-deploy, content to sg-content, design to sg-design, customer-experience work to sg-customer, internal skill maintenance to the internal 900 core workflow, and obvious specialist audits to sg-audit-*.
Related Skills
See the rest of the loop around this move.
Build & Fix
sg-build
Run non-trivial work from story to spec, build, verification, closeout, and ship without making the user drive every gate.
The master user-facing lifecycle orchestrator for carrying a story, bug, or goal through ShipGlows's spec, readiness, implementation, verification, onboarding consideration, documentation, closure, and shipping gates.
Open skill page Operate & Ship
sg-maintain
Run project maintenance from triage through delegated fixes, verification, and ship routing.
A master maintenance lifecycle skill for reviewing project health, creating or continuing specs when needed, delegating remediation, verifying results, and routing ship or deploy.
Open skill page Build & Fix
sg-bug
Run a bug from report to dossier, fix, retest, verification, and ship risk without skipping gates.
A professional bug loop executor that reads bug state and continues through the right ShipGlows owner skills when safe.
Open skill page Operate & Ship
sg-deploy
Run the whole release confidence loop instead of stitching checks, ship, prod, browser proof, and verification by hand.
A release orchestration skill for moving work through technical checks, bounded shipping, deployment readiness, post-deploy evidence, final verification, and optional changelog routing.
Open skill page Research & Grow
sg-content
Manage content work through one lifecycle instead of guessing which writing, audit, docs, or SEO skill to launch.
A master content lifecycle skill for routing strategy, repurposing, drafting, enrichment, audits, public-content governance, validation, and ship readiness through the right owner skills.
Open skill page Build & Fix
sg-design
One design skill, with explicit modes and rigorous playbooks.
The single public design entrypoint for system creation, playgrounds, UI/token/component/accessibility audits, implementation, proof, verification, and shipping.
Open skill page Build & Fix
sg-customer
Turn shipped features into clear, trusted customer journeys.
A customer-experience skill for UX/UI clarity, friction, trust, first-success paths, onboarding, setup sequencing, recoverable states, docs coherence, and proof routing.
Open skill page Audit & Improve
sg-audit
Run a broad project audit when you need a high-level map of what is weak before you decide what to fix.
The top-level audit skill scans across multiple quality domains so you can see where the real risk or drift sits.
Open skill pageGo Deeper
This public page explains the move. The repository explains the execution contract.
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.