7 tagged development-workflow, measured the same way as everything else here.
Browse within: code-quality 43claude-code-plugin 30Multi-Agent 15
ZeusYue/acceptance-driven-development-skill
Skill Claude CodeCodex
Use when creating or changing a software project, or when the user explicitly requests ADD, acceptance criteria, or verifiable done conditions.
Skill Claude Code
Requirement-aligned development workflow. TRIGGER: whenever the user asks to build a feature, make a change, optimize/improve something, or fix a bug — especially when the requirement is vague or lacks scope/acceptance criteria. Before starting, the agent MUST detect the user's role (PM/Developer/Both), persisted…
xincheng-1999/orchestrating-development-graphs
Skill Claude CodeCodex
Use when starting a code change, feature, bug fix, refactor, or build/configuration task where workflow intensity may be disproportionate, or when reviewing whether development changes are necessary.
Skill Claude CodeCodex
GitHub development workflow for planning, implementing, validating, and reviewing code changes. Plans a feature or bug as a GitHub issue, implements an issue and opens a pull request, runs a repository's validation checks before a PR, reviews a pull request, plans an epic as phased issues, researches a technical…
Skill Claude Code needs its repo
Multi-Agent Collaborative Pipeline for Claude Code — orchestrates 7 development phases with 6 specialized AI roles.
Skill Claude CodeCodex
Bootstrap a new project with multi-CLI agent config — drops AGENTS.md + CLAUDE.md from the cc-templates templates/ directory into a target project, patches its .gitignore, and prints verification commands. The "multi-agent" here means multi-CLI (Claude Code + Codex CLI + Antigravity CLI), not multiple internal…
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: