When should I use the Thinking Archetypes skill?

Use it when a problem keeps recurring despite multiple fixes, when growth has stalled without an obvious cause, or when quick fixes seem to be making things worse over time.

What are Systems Archetypes in software development?

Systems Archetypes are recurring patterns of behavior, such as 'Fixes That Fail' or 'Shifting the Burden,' that describe how complex systems (like codebases or dev teams) fail over time.

Can this skill help with team productivity?

Yes, by identifying archetypes like 'Tragedy of the Commons' or 'Escalation,' it reveals why shared resources degrade or why teams get stuck in counterproductive competitive cycles.

How does this skill help manage technical debt?

It helps Claude identify if a team is applying symptomatic 'quick fixes' that actually increase complexity in the long run, pointing instead toward fundamental architectural resolutions.

Thinking Archetypes

Name: Thinking Archetypes
Author: tjboudreaux

bytjboudreaux

•

Productivity & Workflow

Diagnoses recurring technical and organizational problems using Senge's systems thinking frameworks to identify root causes and high-leverage solutions.

Thinking Archetypes brings Peter Senge's systems thinking patterns to the software development lifecycle. By recognizing recurring cycles like 'Fixes That Fail' or 'Shifting the Burden,' this skill enables Claude to look beyond surface-level symptoms and identify the structural reasons why technical debt accumulates, scaling hits plateaus, or shared resources degrade. It provides developers and leads with a diagnostic framework to predict system behavior and implement interventions that address root causes rather than temporary symptoms.

Key Features

01Pinpoints high-leverage intervention points for complex, recurring problems

02Facilitates strategic decision-making for scaling and resource allocation

03Provides software-specific examples for technical debt and infrastructure management

047 GitHub stars

05Identifies seven core systems archetypes in software and organizational contexts

06Analyzes feedback loops and delays that cause 'quick fixes' to backfire

Use Cases

01Analyzing why technical debt continues to grow despite repeated refactoring efforts

02Strategic planning for system scaling to identify 'Limits to Growth' before they become critical

03Diagnosing bottlenecks in shared infrastructure or CI/CD pipelines to prevent resource degradation

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tjboudreaux/cc-thinking-skills thinking-archetypes

For use in Claude.ai and ChatGPT

Download Skill