44 tagged workflow, measured the same way as everything else here.
Browse within: claude-code-plugin 40claude-code-hooks 31spec-driven-development 31plugin 25agentic-workflow 22execution 22agent-orchestration 21marketplace 21Multi-Agent 20framework 14vibecoding 14agent 12ai-coding 11cursor 9
Agent Claude Code
An AI agent profile for Vue 3 internationalisation and interface translation. Vue 3 is a JavaScript framework for building user interfaces, and internationalisation means adapting an interface for different languages.
Agent Claude Code
Product-technical alignment reviewer. Spawned in a tmux pane via OpenAI Codex CLI with zero inherited context. Cross-provider isolation (GPT-5.5 vs Lead's Claude) layered on top of zero context inheritance. Reads product-spec and tech-spec independently to verify the technical approach actually implements what the…
yaukwan/my-claude-code-workflow
Agent Claude Code
Universal implementation and progress tracking expert using artisan agent pattern. Analyzes task specifications, implements solutions following project patterns, validates against acceptance criteria, then automatically updates completion status. Use PROACTIVELY for systematic task implementation with integrated…
Agent Claude Code
Convert PRDs into development task lists.
Agent Claude Code
Use this agent proactively when making significant architectural decisions and reactively to document architectural choices after they're made. Invoke when evaluating technology options, making foundational decisions, or discovering undocumented architectural choices.
Agent Claude Code
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.
Agent Claude Code
Reviews every implementation against this repo's rules and non-negotiables before it ships.
Agent Claude Code
Read-only auditor of the NAMES a repo's doc layer cites. The layer is whatever AGENTS.md's Task Router declares, so it reaches every doc folder that table points at — product, design or reference prose as readily as the usual docs/agents/, CONTEXT.md and docs/decisions/ — read for its paths and symbols but never its…
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: