ladder

Escalate blocked tasks through ADR-backed rungs with budgets and parking logic.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill ladder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ladder
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/ladder
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill ladder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a formal, ADR-backed ladder to escalate and unblock tasks that are blocked by context, repeated fix-loops, or cross-council disagreements, reducing firefighting and wasted cycles.

Core Features & Use Cases

  • Rung-based escalation guides teams from retry (Rung 0) to cross-council escalation (Rung 3) and user involvement (Rung 6), with documented ADRs.
  • Budgets and metrics enforce disciplined attempts, ensure traceability, and support pivot or parking decisions when necessary.
  • Parking and revival readiness preserves work artifacts and records reconsider triggers for future revival when conditions change.

Quick Start

Initiate a blocked task, reference ladder-matrix, dispatch Rung 0, and log ADRs for each rung transition.

Frequently Asked Questions about ladder

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

FAQPage Schema
How do I unblock tasks stuck in repeated fix-loops or context failures?

To unblock tasks stuck in fix-loops or context failures, use a structured escalation ladder that guides teams from initial retries to cross-council disputes, enforcing attempt budgets and logging ADRs for traceability.

What is an ADR-backed escalation ladder for governance and taskflow management?

An ADR-backed escalation ladder is a formal governance process that moves blocked tasks through defined rungs, from Rung 0 retries to Rung 6 user involvement, documenting architectural decisions to reduce wasted cycles and firefighting.

How do I escalate cross-council disputes blocking my development tasks?

Escalate cross-council disputes by advancing the blocked task up the escalation ladder to Rung 3, applying rung budgets to constrain attempts and recording ADRs to ensure formal governance and dispute resolution traceability.

When should I park a blocked task instead of continuing to retry fixes?

Park a blocked task when fix-loop exhaustion or context failures persist beyond defined rung budgets, preserving work artifacts and logging parking triggers in status.json to support future revival when conditions change.

How do I start an escalation process for user-dependent blockers?

Initiate the escalation process for user-dependent blockers by dispatching Rung 0, referencing the ladder-matrix, and progressively advancing through rungs up to Rung 6 while logging ADRs for each transition to ensure accountability.

Can I trace the state and parking triggers of blocked tasks across a project?

Trace blocked task states by storing rung state in status.json and logging parking triggers, which preserves revival readiness and ensures work artifacts remain documented for future reconsideration when conditions change.