antipattern-detector

Detect and analyze technical and organizational anti-patterns in project documents.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/jetmobsol/serene --skill antipattern-detector-jetmobsol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: antipattern-detector
Source: https://github.com/jetmobsol/serene/tree/main/.claude/skills/antipattern-detector
Command: npx skills add https://github.com/jetmobsol/serene --skill antipattern-detector-jetmobsol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify common technical, organizational, and process anti-patterns that lead to project failure, saving time and resources by flagging red flags before they become critical issues.

Core Features & Use Cases

  • Pattern Recognition: Detects over 20 common anti-patterns across architecture, timelines, teams, processes, and technology choices.
  • Risk Assessment: Assigns severity levels (Critical, High, Medium, Low) to identified patterns.
  • Structured Reporting: Generates a clear report detailing detected patterns, evidence, risks, and recommendations.
  • Use Case: When reviewing a new project proposal, use this Skill to automatically scan for potential pitfalls like "Timeline Fantasy" or "Hero Culture" to ensure a more robust and realistic plan.

Quick Start

Use the antipattern-detector skill to analyze the attached document 'project-proposal.md'.

Frequently Asked Questions about antipattern-detector

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

FAQPage Schema
How do I identify technical debt and project risks in a software proposal?

To identify technical debt and project risks in a software proposal, you can analyze architecture documents to detect common anti-patterns. This process flags structural issues, timeline fallacies, and team configuration risks early, providing severity assessments and remediation advice for a more robust plan.

What are common software architecture anti-patterns to look for during a review?

Common software architecture anti-patterns include Timeline Fantasy, Hero Culture, and over 20 other technical, organizational, and process failure modes. Detecting these anti-patterns during an architecture review helps flag potential failure modes related to technology choices and team structures before they become critical.

How do I assess the severity of technical debt and organizational risks in strategic plans?

Assessing the severity of technical debt and organizational risks involves evaluating strategic plans against a catalog of known anti-patterns. This approach assigns severity levels—Critical, High, Medium, or Low—to identified patterns, generating a structured report detailing evidence and recommendations for risk mitigation.

Can I automate process improvement and risk assessment for project management documents?

You can automate process improvement and risk assessment for project management documents by applying a structured detection process to scan proposals. This automatically identifies anti-patterns related to processes and timelines, providing actionable remediation advice to ensure a realistic project plan.

When do I need an anti-pattern analysis for architecture review?

You need an anti-pattern analysis for architecture review when evaluating new project proposals, architecture documents, or strategic plans. This analysis identifies red flags related to technology choices, team structures, and timelines early, saving time and resources by preventing critical project failures.