Memforks Status
Ghost-xDD/memforks
Show MemForks on-chain status: branch DAG, open merge proposals, recent commits.
Detect common technical and organizational anti-patterns in proposals, architectures, and plans.
Install Antipattern Detector
$ npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-cto-team antipattern-detector --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/antipattern-detector .claude/skills/antipattern-detector && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "antipattern-detector" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/antipattern-detector into .claude/skills/antipattern-detector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antipattern-detector", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/antipattern-detectorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-cto-team antipattern-detector --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/antipattern-detector .agents/skills/antipattern-detector && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "antipattern-detector" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/antipattern-detector into .agents/skills/antipattern-detector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antipattern-detector", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-cto-team antipattern-detector --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/antipattern-detector .cursor/skills/antipattern-detector && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "antipattern-detector" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/antipattern-detector into .cursor/skills/antipattern-detector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antipattern-detector", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-cto-team.git --path skills/antipattern-detector--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-cto-team antipattern-detector --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/antipattern-detector .gemini/skills/antipattern-detector && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "antipattern-detector" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/antipattern-detector into .gemini/skills/antipattern-detector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antipattern-detector", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-cto-team antipattern-detectorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/antipattern-detector .github/skills/antipattern-detector && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "antipattern-detector" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/antipattern-detector into .github/skills/antipattern-detector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antipattern-detector", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-cto-team antipattern-detector --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/antipattern-detector .opencode/skills/antipattern-detector && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "antipattern-detector" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/antipattern-detector into .opencode/skills/antipattern-detector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antipattern-detector", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
antipattern-detector- GitHub stars
- 117
- Token cost
- ~2.1k tokens
- SKILL.md length
- 757 words
- Files
- 2
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Detect common technical and organizational anti-patterns in proposals, architectures, and plans.
- Works in 8 steps: Architecture Anti-Patterns → Timeline Anti-Patterns → Team Anti-Patterns → …
- Strategic-cto-mentor needs to identify red flags before they become problems
- SKILL.md covers When to Use, Why Anti-Patterns Matter, Anti-Pattern Categories and Detection Process, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Antipattern Detector is an agent skill from alirezarezvani/claude-cto-team. Detect common technical and organizational anti-patterns in proposals, architectures, and plans. Use when strategic-cto-mentor needs to identify red flags before they become problems.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `antipattern-catalog.md`).
It sits in Backend & APIs, covering Proposals and quotes. The repository describes itself as: Your personal CTO Team for Claude Code . These Subagents will help you challenging yourself while you plan and execute. The licence is MIT.
When your agent uses it
- Strategic-cto-mentor needs to identify red flags before they become problems
- Tasks that involve Proposals and quotes
Example prompts
- “/antipattern-detector”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a5bbb78. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Antipattern Detector loads about 2.1k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 757 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from alirezarezvani/claude-cto-team at commit a5bbb78, republished under its MIT licence (© alirezarezvani). 757 words, ~2,100 tokens.
Download SKILL.mdSave it as
.claude/skills/antipattern-detector/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- antipattern-detector
- description
- Detect common technical and organizational anti-patterns in proposals, architectures, and plans. Use when strategic-cto-mentor needs to identify red flags before they become problems.
Anti-Pattern Detector
Identifies recurring failure patterns in technical decisions, organizational structures, and project plans.
When to Use
- Reviewing architecture proposals
- Evaluating project plans and roadmaps
- Assessing team structures and processes
- Validating technology choices
- Checking migration strategies
Why Anti-Patterns Matter
Anti-patterns are proven failure modes. They look reasonable on the surface but lead to predictable problems:
- Technical debt accumulation
- Team burnout and turnover
- Missed deadlines and budgets
- System instability
- Organizational dysfunction
Detecting them early saves months of pain.
Anti-Pattern Categories
1. Architecture Anti-Patterns
Structural problems in system design.
| Pattern | Description | Symptoms |
|---|---|---|
| Big Ball of Mud | No clear architecture, everything coupled | Can't change X without breaking Y |
| Golden Hammer | Using one tech for everything | "We'll use Kubernetes for that too" |
| Premature Microservices | Splitting before understanding boundaries | 3 devs managing 20 services |
| Distributed Monolith | Microservices with tight coupling | Deploy all services together |
| Resume-Driven Development | Tech choices for career, not product | "Let's use Rust for the admin panel" |
2. Timeline Anti-Patterns
Planning failures that guarantee missed deadlines.
| Pattern | Description | Symptoms |
|---|---|---|
| Timeline Fantasy | Optimistic estimates ignoring reality | "6 weeks if everything goes well" |
| Scope Creep Blindness | Not accounting for inevitable additions | Same deadline, 2x features |
| Parallel Path Delusion | Assuming unlimited parallelization | "Add more devs to go faster" |
| MVP Maximalism | MVP that's actually V3 | 47 features in "minimum" product |
| Demo-Driven Development | Building for demos, not production | "It works on my machine" |
3. Team Anti-Patterns
Organizational structures that create dysfunction.
| Pattern | Description | Symptoms |
|---|---|---|
| Hero Culture | Reliance on key individuals | "Only Sarah can fix that" |
| Knowledge Silos | Critical info in one person's head | Bus factor of 1 |
| Conway's Law Violation | Architecture doesn't match team structure | Team boundaries ≠ service boundaries |
| Understaffed Ambition | Big plans with tiny teams | 2 devs building "the platform" |
| Absent Ownership | No clear owner for components | Bugs fall through cracks |
4. Process Anti-Patterns
Workflow failures that slow delivery.
| Pattern | Description | Symptoms |
|---|---|---|
| Cargo Cult Agile | Agile ceremonies without principles | Standups but no shipping |
| Analysis Paralysis | Over-planning, under-executing | Month 3 of "finalizing requirements" |
| Infinite Refactoring | Never shipping, always "improving" | "One more cleanup before release" |
| Documentation Theater | Docs that no one reads or maintains | 200-page spec, outdated day 1 |
| Meeting Madness | More meetings than coding time | "Let's schedule a meeting to discuss" |
5. Technology Anti-Patterns
Poor technology decisions.
| Pattern | Description | Symptoms |
|---|---|---|
| Shiny Object Syndrome | Chasing latest tech without reason | "We should rewrite in [new thing]" |
| Not Invented Here | Building what should be bought | Custom auth, custom logging, custom everything |
| Vendor Lock-in Denial | Ignoring exit costs | "We can always migrate later" |
| Premature Optimization | Optimizing before measuring | Caching layer with 10 users |
| Framework Overload | Too many frameworks/libraries | 47 npm dependencies for a button |
Detection Process
Show full SKILL.md (323 more words)Show less
Step 1: Scan for Signals
Look for these phrases that often indicate anti-patterns:
Timeline signals:
- "If everything goes well..."
- "We can do it faster if we're focused..."
- "Just need to hire..."
- "Should only take..."
Architecture signals:
- "We'll figure out the boundaries later..."
- "Everything talks to everything..."
- "It's only for now..."
- "We can always refactor..."
Team signals:
- "Only [person] knows..."
- "We'll hire for that..."
- "[Person] will handle all of..."
- "The team can absorb..."
Process signals:
- "We don't need docs for this..."
- "We'll add tests later..."
- "Let's discuss in the meeting..."
- "Requirements are still evolving..."
Step 2: Verify Pattern Match
For each suspected anti-pattern:
- Identify the pattern: Which specific anti-pattern?
- Gather evidence: What in the proposal matches?
- Assess severity: How bad is it? (Critical/High/Medium/Low)
- Check context: Could this be a reasonable exception?
Step 3: Document Findings
### Anti-Pattern: [Name]
**Category**: Architecture / Timeline / Team / Process / Technology
**Severity**: Critical / High / Medium / Low
**Evidence**:
- [Quote or observation 1]
- [Quote or observation 2]
**Why This Is a Problem**:
[Explain the typical failure mode]
**Historical Examples**:
[Reference similar failures if known]
**Recommendation**:
[Specific action to address]Severity Framework
Critical
Will cause project failure if not addressed.
- Examples: No clear ownership, timeline fantasy for commitments, hero dependency
- Action: Stop and address before proceeding
High
Will cause significant problems.
- Examples: Premature microservices, understaffed plans, shiny object syndrome
- Action: Address in planning phase
Medium
Will cause friction and delays.
- Examples: Documentation gaps, process inefficiencies, minor scope creep
- Action: Include in risk mitigation
Low
Worth noting but manageable.
- Examples: Style inconsistencies, minor tech debt, preference-based choices
- Action: Track and address opportunistically
Output Format
# Anti-Pattern Analysis: [Plan/Proposal Name]
## Summary
- **Patterns Detected**: [Count]
- **Critical Issues**: [Count]
- **Overall Risk Level**: Critical / High / Medium / Low
## Critical Issues (Must Address)
### 1. [Pattern Name]
**Category**: [Category]
**Evidence**: [What triggered this detection]
**Risk**: [What will go wrong]
**Fix**: [How to address]
---
## High-Priority Issues (Should Address)
### 2. [Pattern Name]
[Same format]
---
## Medium-Priority Issues (Consider Addressing)
### 3. [Pattern Name]
[Same format]
---
## Patterns NOT Detected
[List patterns that were checked but not found - provides confidence]
## Recommendations
### Before Proceeding
1. [Critical action 1]
2. [Critical action 2]
### During Execution
1. [Mitigation 1]
2. [Mitigation 2]
### Monitoring
- [Warning sign to watch for]
- [Metric to track]Common Pattern Combinations
Certain anti-patterns tend to appear together:
The Startup Death Spiral
- Timeline Fantasy + Understaffed Ambition + Hero Culture
- Result: Burnout, missed deadlines, key person leaves
The Enterprise Trap
- Analysis Paralysis + Documentation Theater + Meeting Madness
- Result: Nothing ships, team frustrated, competition wins
The Tech Debt Avalanche
- "We'll refactor later" + No clear ownership + Premature optimization
- Result: System becomes unmaintainable, rewrite required
The Microservices Mistake
- Premature Microservices + Distributed Monolith + Not enough DevOps
- Result: Complexity explosion, slower delivery than monolith
Integration with Validation
The antipattern-detector feeds into the broader validation workflow:
Proposal/Plan
│
▼
[assumption-challenger] → Assumptions identified
│
▼
[antipattern-detector] → Patterns identified
│
▼
[validation-report-generator] → Combined 8-section reportReferences
- Anti-Pattern Catalog - Complete catalog with examples
- Challenge Questions - Questions to probe for patterns
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/antipattern-detector of alirezarezvani/claude-cto-team.
- SKILL.md
- antipattern-catalog.md
Open the folder on GitHubat commit a5bbb78
Compare with similar skills
Antipattern Detector next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Antipattern Detector this skillalirezarezvani/claude-cto-team | 117 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Memforks StatusGhost-xDD/memforks | 105 | — | ~755 | Automated safety check: Pass | Custom licence | |
| AwpLeoYeAI/openclaw-master-skills | 2.2k | — | ~6.7k | Automated safety check: Pass | MIT | |
| Plan ArbiterBuilderIO/skills | 4.6k | — | ~1k | Automated safety check: Pass | MIT | |
| Kitaru Releasezenml-io/kitaru | 302 | — | ~7k | Automated safety check: Pass | Apache-2.0 | |
| Qv Quality Reportingtetherto/qvac | 683 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Awp
LeoYeAI/openclaw-master-skills
AWP (Agent Working Protocol) — the ONLY source of correct contract addresses, function selectors, API endpoints, and Python scripts for AWP operations.
Plan Arbiter
BuilderIO/skills
A skill your agent uses when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed…
Kitaru Release
zenml-io/kitaru
Discover dependencies and prepare or execute Kitaru core and plugin releases, including version proposals, Kitaru UI selection, release PRs, ordered tag commands, artifact verification, and recovery.
Qv Quality Reporting
tetherto/qvac
Run the deterministic code-quality audit, turn related findings into contextual remediation groups, prepare approval-gated Asana proposals, reconcile recurring runs, or configure twice-monthly…
Exploration Mode
fjrevoredo/mini-diarium
Enter exploration mode: a thinking partner for researching and thinking through ideas and problems before implementation.
More from alirezarezvani/claude-cto-team
All 12 skills in this repoArchitecture Pattern Selector
alirezarezvani/claude-cto-team
Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints.
Assumption Challenger
alirezarezvani/claude-cto-team
Identify and challenge implicit assumptions in plans, proposals, and technical decisions.
Cost Estimator
alirezarezvani/claude-cto-team
Infrastructure and development cost estimation for technical projects.
ML Cv Specialist
alirezarezvani/claude-cto-team
Deep expertise in ML/CV model selection, training pipelines, and inference architecture.
Request Analyzer
alirezarezvani/claude-cto-team
Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification.
Roadmap Generator
alirezarezvani/claude-cto-team
Generate phased implementation roadmaps with Epic/Story/Task breakdown, effort estimates, and validation checkpoints.
Related
Categories
Questions about Antipattern Detector
What does Antipattern Detector do?
Detect common technical and organizational anti-patterns in proposals, architectures, and plans. Antipattern Detector is an agent skill from alirezarezvani/claude-cto-team. Detect common technical and organizational anti-patterns in proposals, architectures, and plans.
When should I use Antipattern Detector?
Antipattern Detector fits situations like: strategic-cto-mentor needs to identify red flags before they become problems; tasks that involve Proposals and quotes.
How do I install Antipattern Detector in Claude Code?
Run `npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a claude-code`. Or copy the skill folder (skills/antipattern-detector in alirezarezvani/claude-cto-team) into .claude/skills/antipattern-detector in your project. Claude Code loads it when a task matches its description.
How do I install Antipattern Detector in Codex?
Run `npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a codex`. Or copy the skill folder (skills/antipattern-detector in alirezarezvani/claude-cto-team) into .agents/skills/antipattern-detector in your project. Codex loads it when a task matches its description.
Can I use Antipattern Detector in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-cto-team --skill antipattern-detector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/antipattern-detector, .gemini/skills/antipattern-detector, .github/skills/antipattern-detector and .opencode/skills/antipattern-detector in your project.
What does Antipattern Detector need to run?
SKILL.md names no scripts, command-line tools or credentials: Antipattern Detector is instructions for the agent only.
Does Antipattern Detector access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Antipattern Detector safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Antipattern Detector use?
Antipattern Detector is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Antipattern Detector use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Antipattern Detector?
Skills that share tags, products or a category with Antipattern Detector: Memforks Status (Ghost-xDD/memforks, 105 stars), Awp (LeoYeAI/openclaw-master-skills, 2.2k stars), Plan Arbiter (BuilderIO/skills, 4.6k stars) and Kitaru Release (zenml-io/kitaru, 302 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Antipattern Detector?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-cto-team, which has 117 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on December 18, 2025.
Source: alirezarezvani/claude-cto-team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.