Guide progression from In-Loop to Out-Loop to Zero-Touch Engineering. Use when assessing agentic maturity, planning ZTE progression, or identifying requirements for autonomous operation.
Assesses agentic maturity and guides progression from interactive prompting to full automation. Triggers when evaluating workflow success rates, planning ZTE adoption, or identifying blockers to autonomous operation.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install google-ecosystem@melodic-softwareThis skill is limited to using the following tools:
Guide teams through the three levels of agentic coding: In-Loop, Out-Loop, and Zero-Touch Engineering.
| Level | Presence KPI | Description |
|---|---|---|
| In-Loop | Constant | Interactive prompting |
| Out-Loop | 2 (prompt + review) | AFK agents with review |
| Zero-Touch | 1 (prompt only) | Full automation |
In-Loop -> Out-Loop:
Out-Loop -> ZTE:
Search for agentic workflow indicators:
Look for:
- Manual prompting patterns (In-Loop)
- Automated workflows with review (Out-Loop)
- Fully automated shipping (ZTE)
Review KPI data if available:
Check @agentic-kpis.md or equivalent:
- Attempt counts
- Success streaks
- Review catch rates
Common blockers to progression:
| Blocker | Mitigation |
|---|---|
| Low test coverage | Improve tests before progressing |
| Inconsistent success | Analyze failures, improve prompts |
| Review catches issues | Tests need to catch these first |
| No rollback capability | Add before enabling ZTE |
Based on current level, recommend:
At In-Loop:
At Out-Loop:
Near ZTE:
Provide assessment:
## ZTE Assessment
**Current Level:** [In-Loop | Out-Loop | ZTE]
**Problem Classes Assessed:** [chores, bugs, features]
### Indicators Found
- [Evidence of current level]
### Blockers to Progression
- [Identified blockers]
### Recommendations
1. [Specific next step]
2. [Specific next step]
### Target Timeline
- [Realistic progression timeline]
Date: 2025-12-26 Model: claude-opus-4-5-20251101
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.