gstack/SKILL.md.tmpl

---
name: gstack
preamble-tier: 1
version: 1.2.0
description: |
  Router for the gstack skill suite. Sends any gstack request to the right skill
  (planning, review, QA, shipping, debugging, docs, security, design). Routes QA by
  intent and browser interaction to /browse. Use when you invoke gstack without a specific
  skill, or ask "which gstack skill fits this?". (gstack)
allowed-tools:
  - Bash
  - Read
  - AskUserQuestion
triggers:
  - gstack
  - which gstack skill
  - route this with gstack

---

{{PREAMBLE}}

## Route first

This is the gstack router. Its one job is to send the request to the right skill.

1. If the request is to test behavior, find bugs, QA or dogfood software → invoke `/qa`,
   or `/qa-only` when the user wants reporting without fixes. These skills select browser,
   API, CLI, job, worker or webhook surfaces before loading their testing instructions.
   An API URL does not imply browser testing. An explicit skill request keeps its authority.
2. If the request is browser interaction, screenshots, or inspecting a page
   (open a site, take a screenshot, inspect a flow visually) → invoke `/browse`.
   Every gstack browser skill (`/browse`, `/qa`, `/qa-only`, `/design-review`, `/canary`,
   `/benchmark`, `/scrape`) drives the Aside browser first — the user's real browser with
   their real logged-in sessions — and falls back to gstack's own browser when Aside is not
   installed or not running. Route "open the browser" / "import cookies" requests to the
   fallback-browser skills below only when the user is clearly on that path (Linux,
   Windows, or Aside closed); on Aside there is nothing to open or import.
3. Otherwise, route by the rules below. If nothing matches, answer directly.

Best-effort, record which way you routed (never block on it). Set `ROUTE_OUTCOME` to
`browse` (sent to /browse), `routed` (sent to another skill), or `direct` (answered
directly, no skill matched), and replace `SESSION_ID` with the value the skill-start
output echoed:
```bash
~/.claude/skills/gstack/bin/gstack-telemetry-log --event-type route --skill gstack --outcome ROUTE_OUTCOME --session-id "SESSION_ID" 2>/dev/null || true
```

If `PROACTIVE` is `false` or `off`: do not proactively invoke or suggest other gstack
skills during this session, including by asking whether to run one ("want me to run /X?").
Only run skills the user explicitly invokes. This preference persists across sessions via
`gstack-config`.

If `PROACTIVE` is `core` (default): **invoke the Skill tool** only for the four core
skills when the user's request matches their rule below: `/office-hours`, `/review`,
`/qa` and `/ship`. For every other rule, answer directly and do not suggest the skill;
the user types it. The browser step above and the **Failures** branches below follow the
same rule: under `core`, name `/browse` or `/investigate` for the user to type instead of
invoking it. A skill the user names is always invoked, whatever this setting says,
and a step inside a skill that is already running (a handoff, a review gate, a subagent it
dispatches) is part of that skill, not a suggestion.

If `PROACTIVE` is `all` (or `true`): **invoke the Skill tool** when the user's request
matches any skill's purpose. Do NOT answer directly when a skill exists for the task.
Use the Skill tool to invoke it. The skill has specialized workflows, checklists, and
quality gates that produce better results than answering inline.

**Routing rules — when you see these patterns, INVOKE the skill via the Skill tool** (under
`core`, only the four core rules auto-invoke):
- User describes a new idea, asks "is this worth building", brainstorms, pitches a concept → invoke `/office-hours`
- User asks to spec something out, file an issue, write up a ticket, "turn this into a GitHub issue", "backlog item" → invoke `/spec`
- User asks about strategy, scope, ambition, "think bigger", "what should we build" → invoke `/plan-ceo-review`
- User asks to review architecture, lock in the plan, "does this design make sense" → invoke `/plan-eng-review`
- User asks about design system, brand, visual identity, "how should this look" → invoke `/design-consultation`
- User asks to review design of a plan → invoke `/plan-design-review`
- User asks about developer experience of a plan, API/CLI/SDK design → invoke `/plan-devex-review`
- User wants all reviews done automatically, "review everything" → invoke `/autoplan`
- User reports a bug, error, failing test or broken behavior, "why is this broken", "this doesn't work", "wtf", "something's wrong" → check the cause by **Failures** below, then fix it or invoke `/investigate`
- User asks to test the site, find bugs, QA, "does this work", "check the deploy" → invoke `/qa`
- User asks to just report bugs without fixing → invoke `/qa-only`
- User asks to review code, check the diff, pre-landing review, "look at my changes" → invoke `/review`
- User asks to find code worth sharing, shared-code extractions, or duplication worth consolidating → invoke `/deslop-shared-libs`
- User asks to audit, prune or find low-value tests in the existing suite → invoke `/test-audit`
- User asks to write a skill, improve or slim a skill, or add a lesson to a named skill → invoke `/write-skill`
- User asks about visual polish, design audit of a live site, "this looks off" → invoke `/design-review`
- User asks to audit the live developer experience, time-to-hello-world → invoke `/devex-review`
- User asks to run the checks, make the tests pass, "verify my change", "check my work" while building → invoke `/verify`
- User asks to ship, deploy, push, create a PR, "let's land this", "send it" → invoke `/ship`
- User asks to merge + deploy + verify as one flow → invoke `/land-and-deploy`
- User asks to rebase or revive an old PR, "modernize this PR", whether a stale PR is still worth landing → invoke `/modernize`
- User asks to configure deployment for the project → invoke `/setup-deploy`
- User asks to monitor prod after shipping, post-deploy checks → invoke `/canary`
- User asks to update docs after shipping → invoke `/document-release`
- User asks to write docs from scratch, generate documentation, "document this feature/module" → invoke `/document-generate`
- User asks for a weekly retro, what did we ship, "how'd we do" → invoke `/retro`
- User asks to run a crew of agents, coordinate lanes, build a merge train, call a slot, validate a READY block, write the crew digest, "set up a captain", "run the crew" → invoke `/captain`
{{OUTSIDE_VOICE_ROUTING}}
- User asks for safety mode, careful mode → invoke `/careful` or `/guard`
- User asks to restrict edits to a directory → invoke `/freeze` or `/unfreeze`
- User asks to upgrade gstack → invoke `/gstack-upgrade`
- User asks to save progress, checkpoint, "save my work" → invoke `/context-save`
- User asks to resume, restore, "where was I" → invoke `/context-restore`
- User asks about security, OWASP, vulnerabilities, "is this secure" → invoke `/cso`
- User asks to make a PDF, document, publication → invoke `/make-pdf`
- User asks to pull data off a web page, "grab the table from", "extract the prices" → invoke `/scrape`
- User asks to launch a real browser for QA, "open the browser" → invoke `/open-gstack-browser` (fallback browser; on Aside the tabs are already visible)
- User asks to import cookies for authenticated testing → invoke `/setup-browser-cookies` (fallback browser; Aside already has the sessions)
- User asks to share the browser with another agent, "pair OpenClaw/Codex with my browser" → invoke `/pair-agent` (fallback browser)
- User asks to codify or save the last `/scrape` as a reusable skill → invoke `/skillify` (fallback browser)
- User asks about page speed, web performance regression → invoke `/benchmark`; model or skill benchmarks → invoke `/benchmark-models`
- User asks to plan, preregister, price or pilot a paid eval → invoke `/eval-plan`
- User asks to run a suite, build or eval on Ubicloud → invoke `/ubicloud`
- User asks what gstack has learned, "show learnings" → invoke `/learn`
- User asks to tune question sensitivity, "stop asking me that" → invoke `/plan-tune`
- User asks for code quality dashboard, "health check" → invoke `/health`{{VOICE_TRIGGER_ROUTING}}

**Failures: check the cause, then route.** A failing test, error or stack trace shows where a failure surfaces, not its root cause.

- **Cause supplied** (the user names a specific cause and a narrow fix): make one read-only check of the evidence it rests on, such as the named file, test or log. If that confirms the cause, make the fix and run the focused test that covers it. If it does not, invoke `/investigate` before any further tracing or edit.
- **Cause unknown:** make one read-only triage pass over the supplied evidence and the directly implicated test and code. Do not reproduce, test hypotheses or search wider. If that pass establishes the root cause and a narrow fix, make the fix and run the focused test that covers it. If the cause, scope or intended behavior is still unclear, invoke `/investigate` before any broader diagnosis or edit.

**Route only to skills in your available-skills list.** A rule above whose skill is
not listed there is turned off on this install; skip it, never try to invoke it.

**When to invoke, and when not to.** Invoke when the request matches a skill's purpose:
the skill's workflow, checklists and gates beat an ad-hoc answer. Answer directly when
no skill matches, for a quick factual question or a small edit the user scoped
themselves, and when the user asks for a direct answer instead of a workflow.

If the user opts out of suggestions, run `gstack-config set proactive off`. If they want
every skill suggested, run `gstack-config set proactive all`. `gstack-config set proactive
core` restores the default (the four core skills only).