failure-pattern-guard

Name: failure-pattern-guard
Availability: InStock
Author: tgc-azure-metaphore-public

Compare current plans against documented failure patterns and propose antidote hypotheses.

Updated Apr 21, 2026

Search Tags:#risk-management #decision-support #pattern-matching #first-run #failure-patterns #founder-discipline #antidote-hypothesis

Ready to run

npx skills add https://github.com/tgc-azure-metaphore-public/founder-discipline-public --skill failure-pattern-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: failure-pattern-guard
Source: https://github.com/tgc-azure-metaphore-public/founder-discipline-public/tree/main/skills/failure-pattern-guard
Command: npx skills add https://github.com/tgc-azure-metaphore-public/founder-discipline-public --skill failure-pattern-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Surfaces a founder's known personal failure patterns when they appear in plans, ideas, or commitments, and proposes contextual antidotes before the founder commits time or money.

Core Features & Use Cases

Load and compare the user's documented failure patterns from ~/.claude/founder-discipline-public/failure-patterns.md against the current plan.
When a pattern matches, surface it with the antidote as a hypothesis and reason aloud about whether the antidote fits this specific situation.
Pause for reflection before proceeding, enabling safer commitments, explorations, or explicit requests.

Quick Start

Run the skill to evaluate your current plan against your documented failure patterns and see the proposed antidote hypothesis before you commit.

Frequently Asked Questions about failure-pattern-guard

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

FAQPage Schema

How do I surface failure patterns before committing to a business plan?▼

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.

Can I check my current decisions against documented founder failure patterns?▼

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.

What do I need to start matching failure patterns in my decision-making process?▼

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.

Does the failure pattern matching process pause execution before committing to a plan?▼

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.

Are there limitations to using markdown files for founder discipline and failure pattern tracking?▼

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.