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.
Limited to specific tools
Additional assets for this skill
This 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]
```markdown
## Anti-Patterns to Identify
- Skipping levels (Out-Loop before tests exist)
- All-or-nothing thinking (must ZTE everything)
- Ignoring failure signals (pushing forward despite issues)
- Review theater (reviewing without catching anything)