TrevorEdris/fellowship-of-the-workflows

Repository to share AI-agent workflows

This repository also configures its own agents. See what fellowship-of-the-workflows tells them →

2Stars on the repository
136Mods indexed here, across every type
2mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

reverse-engineer

49

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Extract PRDs, design docs, and architecture diagrams from existing codebases. Reverse-engineer undocumented projects into structured documentation. Triggered by: reverse engineer, extract PRD, generate requirements, document existing code, what does this codebase do, create PRD from code, extract requirements…

not rated 2 2mo ago A 65 tokens

security-review

50

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Perform security-focused code review to identify HIGH-CONFIDENCE vulnerabilities with real exploitation potential. Based on Anthropic's claude-code-security-review. Minimizes false positives with >80% confidence threshold. Use when reviewing PRs for security issues.

not rated 2 2mo ago A 51 tokens

session-handoff

51

TrevorEdris/fellowship-of-the-workflows

Skill Claude CodeCodex

Creates handoff documents for AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6)…

not rated 2 2mo ago A 139 tokens

switch-persona

53

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Switch AI assistant personas interactively. Lists available personas, lets user select one, choose intensity level, and auto-updates the persona.yaml config.

not rated 2 2mo ago A 33 tokens

system-design

54

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Design and review distributed system architecture. Covers resilience patterns (circuit breaker, retry, bulkhead, idempotency), scalability (caching selection, sharding, CQRS), messaging selection (sync vs async, queue vs stream), data patterns (CDC, polyglot persistence, multi-tenancy), and migration strategies…

not rated 2 2mo ago A 93 tokens

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Structured root-cause analysis for bugs, test failures, and unexpected behavior. Four-phase methodology: investigate, analyze patterns, hypothesize, implement fix. Use when encountering any technical issue before proposing fixes. Prevents brute-force retry loops.

not rated 2 2mo ago A 52 tokens

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Enforce RED-GREEN-REFACTOR cycle for any implementation task. Write failing test first, implement minimally, refactor. Triggered by: write tests first, do TDD, red-green-refactor, test-first approach, I want to follow TDD, test-driven. Use when implementing features, fixing bugs, or refactoring code.

not rated 2 2mo ago A 74 tokens

update-docs

57

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Sync documentation with code changes. Detects stale docs, generates/updates READMEs, changelogs, and API docs after implementation. Use after completing a feature, fixing a bug, or before a release.

not rated 2 2mo ago A 47 tokens

velocity-forecast

58

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Analyze GitHub velocity and technical debt trends. Forecasts sprint bottlenecks and tracks debt accumulation. Use for sprint planning, retros, or health checks.

not rated 2 2mo ago A 35 tokens

work-review

59

TrevorEdris/fellowship-of-the-workflows

Skill Claude CodeCodex

Review work accomplished over a time period by correlating Jira tickets with git commits. Triggered by: what did I do this sprint, prepare for standup, self-review, peer review, sprint retro, summarize my work, performance review prep, what have I been working on, status update. Use for self-reviews, peer reviews…

not rated 2 2mo ago A 79 tokens

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Use when writing prose humans will read — documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing. Triggered by: clean up this text, rewrite this, make this clearer, fix this README, improve this error message…

not rated 2 2mo ago A 87 tokens

team

61

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Create an Agent Team from a predefined roster. Spawns multiple Claude Code sessions that coordinate via shared tasks and direct messaging.

not rated 2 2mo ago A 26 tokens

better-stack

62

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Better Stack specialist. Configures Better Stack's unified monitoring, alerting, on-call scheduling, and status pages. Includes Terraform (BetterStackHQ/better-uptime provider) and MCP server usage. Best fit for startups and mid-market teams wanting consolidated uptime monitoring + log aggregation + alerting + status…

not rated 2 2mo ago A 76 tokens

grafana-irm

63

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Grafana Cloud IRM specialist. Configures Grafana IRM (formerly OnCall + Grafana Incident) for alert routing, on-call scheduling, escalation chains, and incident response. Includes Terraform (grafanaoncall resources) and MCP (mcp-grafana) usage. Use for teams on the Grafana + Prometheus + OTel stack.

not rated 2 2mo ago A 78 tokens

incident-io

64

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Skill "incident-io" from TrevorEdris/fellowship-of-the-workflows, covering incident.io, when to use, platform context, modes and setup.

not rated 2 2mo ago A 58 tokens

pagerduty

65

TrevorEdris/fellowship-of-the-workflows

Skill Claude Code

Configure PagerDuty services, escalation policies, on-call schedules, event routing, and IaC. Modes: setup, routing, incidents, terraform.

not rated 2 2mo ago A 33 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: