escalation-l1

Run three parallel lenses to propose file-specific solutions or escalate to L2.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill escalation-l1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: escalation-l1
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/escalation-l1
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill escalation-l1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The L1 escalation skill autonomously responds to in-architecture obstacles by spawning three parallel subagents (Reuse, Compose, Extend-one-function) to explore alternative execution strategies without altering the locked architecture.

Core Features & Use Cases

  • Triggers an autonomous, parallel-lens exploration when direct solutions within the architecture are blocked.
  • Produces 1–3 concrete proposals per lens, each tied to existing files and functions, and evaluates risk, effort, and acceptance-criteria coverage.
  • Synthesizes a best-fit path or escalates to L2 when all lenses fail, updating the capability plan accordingly.

Quick Start

Trigger the L1 escalation using the /escalation-l1 command inside the locked architecture.

Frequently Asked Questions about escalation-l1

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

FAQPage Schema
How do I resolve in-architecture obstacles when direct code changes are blocked?

To resolve in-architecture obstacles, run three parallel subagent lenses that explore reuse, compose, and extend-one-function strategies without altering the locked architecture, outputting concrete proposals.

What is autonomous L1 escalation and when do I need it?

Autonomous L1 escalation is a parallel exploration process needed when straightforward architectural changes fail, spawning three subagents to evaluate risk, effort, and acceptance criteria for alternative execution strategies.

How to trigger autonomous escalation within a locked architecture?

Trigger autonomous escalation within a locked architecture by using the /escalation-l1 command, which initiates the parallel subagent lenses to generate one to three proposals tied to specific files.

Can I use parallel subagent lenses for obstacles within plan and spec constraints?

Yes, you can use parallel subagent lenses for obstacles within plan and spec constraints, as the skill targets issues that cannot be solved with straightforward in-architecture changes while respecting existing limits.

What happens when all parallel architecture lenses fail to produce a viable proposal?

When all parallel architecture lenses fail, the synthesis step escalates the obstacle to L2 and updates the capability plan, ensuring unresolved in-architecture obstacles receive higher-level intervention.

Best way to synthesize alternative execution strategies from multiple subagent proposals?

The best way to synthesize alternative execution strategies is a dedicated synthesis step that evaluates risk, effort, and acceptance-criteria coverage across all subagent proposals to select the best-fit path.