adk-dev-guide

Enforce spec-first ADK agent development with adk eval workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SeanChenR/maestro-agent --skill adk-dev-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adk-dev-guide
Source: https://github.com/SeanChenR/maestro-agent/tree/main/.agents/skills/adk-dev-guide
Command: npx skills add https://github.com/SeanChenR/maestro-agent --skill adk-dev-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, prescriptive development workflow and mandatory coding guidelines that prevent unintended changes, reduce iteration waste, and ensure ADK agents meet spec-driven quality and evaluation thresholds.

Core Features & Use Cases

  • Spec-first development: Directs developers to read DESIGN_SPEC.md as the primary source of truth and align implementation decisions to the spec.
  • Code preservation rules: Defines surgical edit practices so only targeted lines change and unrelated code, configuration, and model settings are preserved.
  • Evaluation-first lifecycle: Mandates iterative adk eval workflows, starting small and expanding test coverage only after core cases pass.
  • Troubleshooting & deployment guardrails: Covers model selection rules, location troubleshooting, tool import precision, loop-breaking heuristics, and the requirement for explicit human approval before deploy.
  • Use case: Onboard a new ADK developer to implement an agent feature, run focused evaluations, fix failures, and prepare a safe deploy pipeline.

Quick Start

Read the project's DESIGN_SPEC.md, then implement changes with surgical precision, run adk eval for iterative evaluation, and obtain explicit human approval before deploying.

Frequently Asked Questions about adk-dev-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate an ADK agent during development?

To evaluate an ADK agent during development, run iterative adk eval workflows starting with small test cases. Expand test coverage only after core cases pass, ensuring the agent meets spec-driven quality thresholds.

What is spec-driven ADK agent development?

Spec-driven ADK agent development uses DESIGN_SPEC.md as the primary source of truth for implementation decisions. It enforces strict code preservation rules and surgical edits to prevent unintended changes to configuration and model settings.

How do I troubleshoot ADK model location and tool import issues?

Troubleshoot ADK model location issues by applying model selection policies and verifying tool import precision. The development workflow includes guardrails for location troubleshooting and loop-breaking heuristics to resolve these failures.

Do I need explicit approval before deploying an ADK agent?

Yes, explicit human approval is required before deploying an ADK agent. The development workflow mandates this deployment guardrail alongside model selection rules and stepwise evaluation procedures to ensure safe deploy pipelines.

What is the best way to preserve code when editing ADK agent logic?

The best way to preserve code when editing ADK agent logic is applying surgical edit practices so only targeted lines change. This prevents unintended modifications to unrelated code, configuration, and model settings during implementation.

Why does my ADK agent evaluation fail on edge cases?

ADK agent evaluation may fail on edge cases if iterative workflows expand test coverage too quickly. The mandated stepwise evaluation procedure requires starting small and only expanding after core cases pass to isolate failures.