failure-pattern-guard

Pattern matching for founder failure patterns works by loading documented failure patterns from a local markdown file and comparing them to your current commitments. When a match is found, it proposes an antidote hypothesis and pauses your workflow for evaluation.

Yes, you can check your current decisions against documented founder failure patterns. The system reads your specific failure patterns from a local markdown file and matches them against your active plans, explorations, or commitments to surface potential risks.

You need to document your personal failure patterns in a local markdown file at a specific directory path. The tool loads this file to compare against your current plans and propose contextual antidote hypotheses.

Yes, the failure pattern matching process pauses execution before committing. When it detects a pattern match in your plan, it presents an antidote hypothesis and explicitly pauses for founder reflection and evaluation before you proceed.

A key limitation is that the tool cannot surface patterns if the local markdown file is missing or empty. You must manually maintain accurate and updated failure pattern documentation for the antidote hypothesis generation to function correctly.