メニュー
Gest Brainstorm. Explore rough ideas or ambiguous requests, inspect existing code/docs/Gest context, ask clarifying questions when needed, and decide whether to create a spec, outline issue, plan, or session task.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Gest Format. Run formatting, linting, typechecking, compile/static checks, and mechanical diff hygiene; fix mechanical issues. Use gte for tests and gdo for documentation.
Gest Implement. Implement one concrete Gest task end to end by reading, claiming, splitting if too broad, editing, verifying, reviewing, formatting as appropriate, and completing it.
Gest Setup. Bootstrap or refresh a Gest-tracked repository workflow surface across tool checks, project command contracts, Justfile targets, AGENTS.md mappings, docs, tests, and setup follow-ups.
Gest Test. Run unit, API regression, smoke, regression, and integration tests appropriate to the changed code; add missing tests when the task changes callable behavior.
Gest Track Work. Use for substantial coding, debugging, implementation, refactoring, documentation, verification, GitHub issue planning, or project work. GTW is the router that classifies requests, chooses/creates Gest outline parents, creates session or development tasks, decides whether a spec or parallel work is needed, and routes to the g* stage skills.
Gest Commit. Create a Git commit for the current changes, using conventional commit style and GitHub metadata when present.
| name | gbs |
| description | Gest Brainstorm. Explore rough ideas or ambiguous requests, inspect existing code/docs/Gest context, ask clarifying questions when needed, and decide whether to create a spec, outline issue, plan, or session task. |
Use when the user has a rough idea, fuzzy feature, or exploratory direction.
gest search "<topic>" --all --json --limit 20, then inspect likely hits
with gest task show, gest task note list, or gest iteration show.gisgspgplgprBrainstorming itself can be tracked as a session leaf when it is part of a larger workflow. Do not create implementation tasks until the desired behavior is clear enough to write acceptance criteria.
Use Gest notes to recover prior decisions, rejected approaches, browser-audit findings, and unresolved follow-ups before recommending a path.
For brainstorms that may become tasks, use references/tag_dependency_workflow.md to surface existing semantic tags, likely near-miss tags, and coupled concepts early. This is a lightweight discovery pass, not a reason to over-plan tiny discussions.