escalate

Escalate stalled BUILD or QA processes by upgrading to a stronger model.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/jackson2787/torque-coding --skill escalate-jackson2787
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: escalate
Source: https://github.com/jackson2787/torque-coding/tree/main/skills/state-machine/escalate
Command: npx skills add https://github.com/jackson2787/torque-coding --skill escalate-jackson2787

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Escalation handles stalled BUILD or QA cycles by upgrading to a stronger model while preserving the memory-bank context so progress can continue without losing task state.

Core Features & Use Cases

  • Primary path: spawn a subagent with a higher rung using the ladder defined by limits.md and pass an escalation-brief as the prompt.
  • Fallback path: gracefully instructs the user to switch models if subagent execution is unavailable, ensuring no data loss.
  • Audit trail: writes escalation-brief.md and records each attempt in current-task/build-log.md for traceability across ladder steps.
  • Resume flow: after escalation, returns control to BUILD or QA to re-check and finish the task.

Quick Start

Trigger escalation automatically when a stall is detected, or manually switch to a stronger model and re-enter the project to resume BUILD or QA.

Frequently Asked Questions about escalate

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

FAQPage Schema
How do I resume a stalled build or QA cycle without losing task context?

Escalating stalled build or QA processes involves upgrading to a stronger model while preserving memory-bank context. It spawns a subagent on a higher rung using a configured ladder and passes an escalation-brief to resume the task.

When should I escalate a stalled build process to a stronger model?

You should escalate stalled builds or QA cycles when they stall due to repeated errors or time limits. The escalation mechanism detects these stalls and records progress before upgrading the model to continue execution.

How do I configure the model ladder for build and QA escalations?

Configuring the model ladder requires defining rung limits in the .memory-bank-v2/machine/limits.md file. This configuration dictates which stronger model the subagent will spawn with when an escalation is triggered.

What happens if subagent execution is unavailable during an escalation?

If subagent execution is unavailable, the fallback path gracefully instructs you to manually switch to a stronger model and re-enter the project to resume the build or QA task, ensuring no data loss.

How are escalation attempts tracked across model upgrades?

Escalation attempts are tracked by writing an escalation-brief.md file at a specified location and recording each attempt in the current-task/build-log.md, providing a full audit trail across ladder steps.

Does the escalation flow return control to the original build or QA process?

Yes, the resume flow returns control to the BUILD or QA process after an escalation completes. This allows the upgraded model to re-check the task state and finish the stalled work.