mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-08 01:38:10 +01:00
Garry Tanandcapy-ai[bot]
3742ee9527
* feat: cut standalone /plan-eng-review; /autoplan keeps its eng phase (GST-1698) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: lower shrunk SKILL.md size pins; keep the retired methodology's pins measured beside /autoplan Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix: carry /autoplan's plan-eng-review.md into Kiro installs Kiro's per-skill loop copied only SKILL.md and sections, so ~/.kiro/skills/gstack-autoplan lacked the Phase 3 methodology file its SKILL.md reads. Generated sibling *.md files now travel with SKILL.md under the same ownership guards. Review-Finding: p1/specialist-batched#1 reader=red-team Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs: file /plan-eng-review retirement follow-ups; scope the changelog claim to ./setup Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix: route architecture-review requests to /autoplan by its description (journey-plan-eng) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
# Voice input (AquaVoice, Whisper, etc.)
|
|
|
|
Many gstack skills list speech-to-text aliases (`voice-triggers:` in their
|
|
templates): "security check" for `/cso`, "run QA" or "test the app" for `/qa`.
|
|
Say one of those naturally and the right
|
|
skill can be picked without the slash command name. On Claude Code the aliases
|
|
are routing lines in the root `/gstack` router; on Codex and the other hosts
|
|
they are appended to each skill's description, which is what those hosts match
|
|
on.
|
|
|
|
The separate `triggers:` list in a skill's frontmatter is gstack metadata, not a
|
|
matching surface. Claude Code and Codex choose a skill from its name and
|
|
description, so a phrase that appears only under `triggers:` does not activate
|
|
the skill (Codex output drops the field; the GBrain host keeps it). The four core
|
|
skills (/office-hours, /review, /qa, /ship) carry their `triggers:` phrases in
|
|
the description itself: every phrase in the full description, and at least one
|
|
in the one-line catalog entry Claude Code reads ("test the site" for /qa, "ship
|
|
it" for /ship). The other skills do not, because under the `core` default they
|
|
wait for you to type them (docs/proactive.md).
|