メニュー
Gest Spec. Draft or update a Gest spec artifact for substantial or unclear work, then ensure implementation happens through follow-on Gest tasks.
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 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.
| name | gsp |
| description | Gest Spec. Draft or update a Gest spec artifact for substantial or unclear work, then ensure implementation happens through follow-on Gest tasks. |
Use when work needs product/design shaping before implementation.
Create a spec when behavior is unclear, there are meaningful trade-offs, acceptance criteria need negotiation, multiple systems are affected, or GitHub visible development is likely.
Before drafting or updating a spec, search Gest for related specs, tasks, iterations, prior decisions, and follow-ups:
gest search "<spec topic>" --all --json --limit 20
gest search "<affected feature/module>" --all --json --limit 20
Inspect relevant hits with gest task show, gest task note list, and
gest iteration show. Include durable references in the spec's References
section when they shape the proposal.
# Spec: <Title>
## Problem Statement
## Proposed Solution
## Scope
### In Scope
### Out of Scope
## Acceptance Criteria
## Open Questions
## References
Keep specs concise enough to read quickly.
Save as a Gest artifact tagged spec plus area tags:
gest artifact create "<title>" --tag spec --tag <area> --body "<body>" --quiet
Link to outline tasks where appropriate. Do not implement directly from the
artifact; use gpl/gis to create follow-on tasks.
Specs should run the discovery pass from references/tag_dependency_workflow.md so the spec identifies existing semantic tags, new tags if needed, and coupled code or UI concepts that should later be checked with ast-grep.