claude

devteam

Take one task to a reviewed pull request with area-owned agents — planner, builders, reviewer, QA, CI and code-review watchers — and a checkpoint at every step.

0 on GitHubby Darren Gegantinov0.4.0updated 5 days agodevelopment
/

Plugin devteam from marketplace dgigafox in dgigafox/claude-plugins. Commands read from the repo's manifest — 4 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (2)

  • implement

    Take one task — a ticket, plain instructions, or work on an open pull request — to a reviewed pull request with the devteam agents, in any repository with a `.agents/devteam.md` file. Readiness check and ticket moves when the repo uses tickets, worktree, plan, one builder per area, review, QA in the

  • setup

    Prepare a repository for /devteam:implement — inspect it, draft and prove the .agents/devteam.md file it reads (areas, build order, gates, tickets, worktrees, CI, code review), write it, then ask the user once to keep, adjust or discard it. Never edits the root AGENTS.md and never commits. Run only

Subagents (9)

  • builder

    Builds one area's phase of a /devteam:implement run — the code and its tests, inside that area's Paths, following the area's Instructions file from the target repo. Dispatched by /devteam:implement for every phase whose area is not `docs`.

  • ci-watcher

    Watches a /devteam:implement pull request — checks it for merge conflicts with the base branch, and waits for every CI job except the OpenCodeReview check, then sorts each failure into related or unrelated to this change. Report only; never re-runs a job, merges, or edits code.

  • docs

    Writes and audits repo-level documentation for a /devteam:implement run — the files of the `docs` area, ADRs and glossary as the repo's own conventions define them. Does not write doc comments in code; those belong to the agent that wrote the code.

  • gates

    Runs the repository's verification gates for the paths a /devteam:implement run changed, before every commit and push, and regenerates lockfiles after a conflict merge. Returns each command's exit code, the step that stopped it, and the log path. Never fixes a failure.

  • planner

    Plans a task for the /devteam:implement orchestrator — splits it into phases, tags each phase with exactly one area from the repo's `## Areas` table, and names the verification for each. Read-only; it returns the plan, it does not write it.

  • qa

    Checks whether a finished change actually works for the end user — verifies the task's acceptance criteria against a running system, and runs the repo's verification gates as a regression check. Read-only; it never edits a file and never fixes anything.

  • review-triage

    Triages OpenCodeReview on a /devteam:implement pull request — waits for the repo's OpenCodeReview check on the latest push, checks every unresolved thread and the summary comment against the code, and returns a verdict per finding. After the user confirms, posts the agreed replies and resolves the t

  • reviewer

    Reviews the full diff of a /devteam:implement run for correctness, safety, and breaches of the repo's written rules — its review rubric, review triggers, and each touched area's Instructions file. Read-only; finds and explains, never fixes.

  • worktree

    Creates the isolated worktree for a /devteam:implement run — runs the repo's worktree skill (or git worktree add when the repo names none) with the capabilities the repo names, runs the repo's setup commands, and checks the services the repo lists. Returns only the path, branch, claimed resources an

Hooks (1)

  • PreToolUse

    sh "${CLAUDE_PLUGIN_ROOT}/hooks/qa-memory-only.sh"

View source on GitHub

More from dgigafox/claude-plugins

All 3 plugins →

lucid

claude

Manually curate native Claude Code memory stores — dedup and reconcile in place (git-versioned), while holding value-contradictions for your review instead of auto-resolving them.

7 skills · hooks

0

Lavish extension: /lavish-ext:code-walkthrough turns a PR, branch, or diff into a plain-words, step-by-step walkthrough page (Overview, then Step 1..N with the code and why). Requires the lavish skill.

1 skill

0

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Maintain devteam?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins3 plugins