failure-memory

Name: failure-memory
Availability: InStock
Author: tasai-lab

Record recurring failure patterns after two occurrences in a local JSON file.

Updated Aug 23, 2026

Search Tags:#debugging #learning #memory #pattern #software #failure #recurrence

Ready to run

npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill failure-memory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: failure-memory
Source: https://github.com/tasai-lab/fractal-dev-workflow/tree/main/skills/failure-memory
Command: npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill failure-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Failure Memory records failure patterns after 2+ occurrences to prevent repeating issues by building a knowledge base of recurrence and learnings.

Core Features & Use Cases

Record recurring failure patterns after 2+ occurrences to create a reusable memory of issues.
Persistent local storage of patterns at ~/.claude/fractal-workflow/failure-memory.json for cross-session access.
Integrations with systematic-debugging and implementation workflows to guide preventive actions.

Quick Start

Record a failure pattern after the second occurrence to update memory and prevent future repeats.

Frequently Asked Questions about failure-memory

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

FAQPage Schema

How do I track recurring software bugs to prevent repeating the same fixes?▼

You can track recurring bugs by recording failure patterns after 2 or more occurrences. This builds a persistent knowledge base of systemic defects, ensuring past learnings guide future preventive actions across software workflows.

What is the best way to record failure patterns for cross-session debugging?▼

Recording failure patterns in a local JSON file enables cross-session debugging access. This persistent storage captures recurrence data, allowing systematic debugging workflows to reference past incidents and apply lasting fixes during development.

How do I build a memory of systemic defects across multiple software projects?▼

Building a memory of systemic defects involves storing recurring failure patterns in a shared local file. This records reliability issues across projects, creating a reusable reference to prevent repeated incidents in future development cycles.

Does failure-memory integrate with systematic-debugging workflows?▼

Yes, failure-memory integrates with systematic-debugging and implementation workflows. By accessing recorded recurrence patterns, these workflows can guide preventive actions and ensure fixes address the root cause of systemic software defects.

When should I record a failure pattern to prevent future software reliability issues?▼

You should record a failure pattern after its second occurrence. This 2+ occurrence threshold ensures only recurring systemic defects are tracked, preventing memory clutter while capturing issues that significantly impact software reliability.

Can I use local file storage for tracking recurring software failures across sessions?▼

Yes, you can use local file storage to track recurring software failures across sessions. Patterns are stored in a local JSON file, providing persistent access to historical failure data and learnings for ongoing debugging workflows.