fallback-planning

Fallback planning creates machine-agnostic contingency TODOs for identified high-impact risks during the risk assessment phase. It produces structured tasks with triggers, purpose, implementation steps, and handoff state so another agent can execute the fallback cold.

Fallback planning generates self-contained TODOs with clear triggers, binary success criteria, and context-rich handoff state. This ensures another agent can execute the contingency plan cold, avoiding costly re-starts when the primary approach fails.

You create machine-agnostic fallback TODOs by pulling and ranking the top 2-3 risks from a design review, then generating structured contingency tasks. Each task includes a trigger, purpose, implementation steps, success criteria, and handoff state.

You need contingency planning during the risk assessment phase of a primary plan to prepare for high-impact risks. Creating fallback TODOs ahead of time saves time and avoids costly re-starts if the primary approach fails.

Yes, generating fallback TODOs requires extracted risk data from your primary plan. The skill uses this input to prioritize the top risks and produce structured contingency tasks with triggers, success criteria, and handoff state.

Contingency tasks fail when they lack clear triggers, binary success criteria, and context-rich handoff state. Fallback planning enforces quality validation to ensure generated TODOs are self-contained and executable by another agent without prior context.