メニュー
Core principles and patterns for the Get Shit Done (GSD) framework. Includes questioning, TDD, verification patterns, and UI brand guidelines.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
MUST READ before writing or modifying ADK agent code. ADK API quick reference for Python — agent types, tool definitions, orchestration patterns, callbacks, and state management. Includes an index of all ADK documentation pages. Do NOT use for creating new projects (use adk-scaffold).
MUST READ before deploying any ADK agent. ADK deployment guide — Agent Engine, Cloud Run, GKE, CI/CD pipelines, secrets, observability, and production workflows. Use when deploying agents to Google Cloud or troubleshooting deployments. Do NOT use for API code patterns (use adk-cheatsheet), evaluation (use adk-eval-guide), or project scaffolding (use adk-scaffold).
ALWAYS ACTIVE — read at the start of any ADK agent development session. ADK development lifecycle and mandatory coding guidelines — spec-driven workflow, code preservation rules, model selection, and troubleshooting.
MUST READ before running any ADK evaluation. ADK evaluation methodology — eval metrics, evalset schema, LLM-as-judge, tool trajectory scoring, and common failure causes. Use when evaluating agent quality, running adk eval, or debugging eval results. Do NOT use for API code patterns (use adk-cheatsheet), deployment (use adk-deploy-guide), or project scaffolding (use adk-scaffold).
MUST READ before setting up observability for ADK agents or when analyzing production traffic, debugging agent behavior, or improving agent performance. ADK observability guide — Cloud Trace, prompt-response logging, BigQuery Agent Analytics, third-party integrations, and troubleshooting. Use when configuring monitoring, tracing, or logging for agents, or when understanding how a deployed agent handles real traffic.
MUST READ before creating or enhancing any ADK agent project. Use when the user wants to build a new agent (e.g. "build me a search agent") or enhance an existing project (e.g. "add CI/CD to my project", "add RAG").
| name | gsd-core |
| description | Core principles and patterns for the Get Shit Done (GSD) framework. Includes questioning, TDD, verification patterns, and UI brand guidelines. |
This skill provides the foundational knowledge and patterns for executing the Get Shit Done (GSD) framework.
Project initialization is dream extraction. Be a thinking partner, not an interviewer.
PROJECT.md that downstream phases can act on.Use TDD for business logic, API endpoints, and data transformations.
test(XX-YY): add failing test, feat(XX-YY): implement feature, refactor(XX-YY): cleanup.Existence ≠ Implementation. Check for:
Maintain a premium, consistent look for all GSD-related output.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ style.Commit outcomes, not process.
The project's memory is stored in structured Markdown files in .planning/.
Detailed agent definitions are located in resources/agents/: