Survival
Keep the mission alive when the map is wrong and supplies are running out.
Overview
Survival is interpreted here as a metaphorical skill with a shipping-now execution model.
Canonical source: Survival (skill)
Provider target: OpenClaw
When To Use
- You are working offline, under partial outage, or with a stripped-down toolchain.
- API quota, compute budget, time, or operator attention is severely constrained.
- The goal is to keep the project moving at all, not to work in ideal conditions.
Workflow
- Inventory the resources still available and the non-negotiable outcomes that must survive.
- Choose the leanest route that preserves essentials and stretches the remaining runway.
- Return a contingency plan with rationing rules, hidden dependencies, and fallback triggers.
Deliverables
- A stripped-down operating plan for degraded conditions.
- A resource budget with conservation rules and tradeoffs.
- A fallback ladder for what to cut or switch if conditions worsen.
Guardrails
- Do not spend scarce capacity on polish or optional scope while essentials are at risk.
- Make hidden dependencies explicit, because surprises are lethal in degraded mode.
Default Invocation
Use $survival to keep this work moving under degraded conditions and show me the minimum viable route.