failure-modes

A pre-execution failure mode checklist surfaces named risks before starting planning, architecture, or implementation tasks. You need it when beginning complex work to enforce explicit acknowledgment of binary STOP conditions and structured mitigation before proceeding.

To apply risk management checks, classify your task into planning, architecture, or implementation, load the relevant failure mode catalog, and require explicit acknowledgment of all binary STOP conditions before generating code or drafting plans.

Yes, you can enforce quality gates during code generation and planning workflows by presenting a numbered checklist of failure modes. It requires explicit acknowledgment of each applicable risk to ensure missing safeguards are resolved before proceeding.

The best way to prevent misalignment is using a pre-execution checklist that enforces a binary STOP condition for each identified failure mode, ensuring misalignment or missing safeguards are surfaced and resolved before implementation begins.

Yes, the failure modes checklist works for both software architecture and project planning by classifying the task type and loading the appropriate failure mode catalog to present relevant governance and risk-management checks before work proceeds.