By eveld
Plan and execute multi-step development workflows with agent-awareness and platform debugging orchestration.
You are implementing an approved plan systematically.
You are creating a detailed implementation plan through an interactive process.
You are conducting comprehensive codebase research by composing specialized skills.
You are sharing personal documents to the team's shared namespace.
Upgrade the workflows plugin from one version to another, handling both automated migrations and edge cases that require reasoning.
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)
Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
codebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the location of files, it will also give you code details!
Deep dive into complex error messages and stack traces. Call error-analyzer when you encounter cryptic errors that require investigation across multiple files.
Analyzes GCP logs and resources to diagnose issues. Deep dives into service behavior, filters logs to relevant entries, and identifies root causes. Use when investigating a specific service or issue.
ALWAYS check this skill before using grep, glob, Task tool, or doing any codebase exploration. Guides you to use specialized agents that are more efficient than basic tools.
Use BEFORE reading multiple files to understand code. Reminds you to use codebase-analyzer agent instead of manual file reading.
Use BEFORE running grep or glob commands. Reminds you to use codebase-locator agent instead of basic file search tools.
Use BEFORE using the Task tool. Ensures you select the correct specialized subagent_type instead of generic agents.
Use when encountering errors or bugs to follow a systematic debugging process instead of jumping to conclusions.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Research, planning, and implementation workflows for Claude Code.
This plugin provides workflow commands for codebase research, implementation planning, and execution. It includes 29 skills that guide Claude to use specialized agents instead of basic tools, and 17 agents with isolated contexts for focused tasks like codebase exploration and platform debugging.
The plugin automatically discovers project-specific commands and test patterns, generates structured documents, and provides tools for debugging GCP, Kubernetes, and Linear issues.
/plugin marketplace add eveld/claude
/plugin install workflows@eveld-claude
Manual installation:
git clone https://github.com/eveld/claude.git
ln -s $(pwd) ~/.claude/plugins/workflows
/workflows:research <question> - Research codebase using parallel agents, save to personal namespace/workflows:plan <research-file> - Create implementation plan, auto-discover project commands/tests/workflows:implement <plan-file> - Execute plan phase by phase with verification/workflows:share <path> - Share personal documents to team namespace/workflows:upgrade - Upgrade plugin from older versionsStarting with v1.3.0, documents use personal/shared namespaces for collaboration:
thoughts/
├── erik/ # Personal workspace (WIP)
│ ├── 0001-auth-system/
│ │ ├── research.md
│ │ ├── plan.md
│ │ └── changelog.md
│ └── 0002-api-redesign/
│ └── research.md
├── alice/ # Another developer's workspace
│ └── 0001-cache-layer/
│ └── research.md
├── shared/ # Published team documents
│ ├── 0042-auth-system/ # Shared from erik/0001
│ │ ├── research.md
│ │ ├── plan.md
│ │ └── changelog.md
│ ├── 0043-cache-layer/ # Shared from alice/0001
│ │ └── research.md
│ ├── research/ # Legacy: Old research documents
│ └── plans/ # Legacy: Old implementation plans
└── notes/ # Project-wide references
├── commands.md
└── testing.md
Collaboration Model:
thoughts/{username}/): Work-in-progress, each developer has own numberingthoughts/shared/): Published docs with canonical team numbering/share-docs to promote personal docs to shared spaceBackward Compatibility: Old thoughts/shared/ structure continues to work.
When ready to share personal documents with the team:
/workflows:share thoughts/erik/0001-auth-system
# Workflow:
# 1. Pulls latest from git
# 2. Finds next shared number (e.g., 0042)
# 3. Copies erik/0001-auth-system → shared/0042-auth-system
# 4. Updates frontmatter in both copies
# 5. Commits and pushes immediately
# 6. Reports: ✅ Shared erik/0001-auth-system → shared/0042-auth-system
Benefits:
During implementation, a changelog tracks actual progress:
changelog.md for auto-correctionThis auto-correction loop ensures later phases adapt to earlier changes.
Example:
/workflows:implement thoughts/shared/0005-authentication/plan.md
# Agent reads plan.md + changelog.md before each phase
# Agent adapts based on what actually happened in previous phases
# Agent updates changelog.md after each phase
Implementation uses agents to conserve context:
This keeps the main agent under 40k tokens per phase while enabling larger, more complex phases.
Token savings: 60% reduction per phase (92k → 40k in main agent)
See skills/spawn-implementation-agents/SKILL.md for full pattern.
Skills guide Claude's behavior automatically:
Agent Awareness:
Platform Debugging:
gcp-logs - Query GCP Cloud Loggingk8s-query - Query Kubernetes resourcesk8s-debug - Launch debug containers in podslinear-issues - Fetch Linear ticketslinear-update - Update Linear ticketsnpx claudepluginhub eveld/claude --plugin workflowsHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review