By bdfinst
Persona-driven AI development team: orchestrator, team agents, review agents, skills (agent-loaded and user-invocable slash commands), and advisory hooks for Claude Code
Scope: UI component and template files only (.svelte, .html, .jsx, .tsx, .vue, .razor, .cshtml, .jsp).
Creates and manages Architecture Decision Records (ADRs) with a decision framework for when to create one
Checks whether AI-authored test assertions and non-obvious production decisions carry human-verification evidence, flags verification debt and regeneration-risk candidates
Scope: Angular component, directive, and service files (`.component.ts`,
Architectural alignment — ADR compliance, layer boundary violations, dependency direction, pattern consistency
Decide which agents and skills to load for a given task. Use at the start of every task to select the minimum viable context load, calculate the token budget, and stay below the 40% utilization ceiling.
Create and manage Architecture Decision Records using the npryce adr-tools CLI. Use when the user asks to "add an ADR", "record this decision", "create an ADR", "supersede ADR N", "link ADRs", "generate the ADR table of contents", or any request involving the `adr` command. Pairs with the adr-author agent — this skill is the mechanics (commands, files, links); adr-author is the decision framework (when an ADR is warranted) and the prose authoring.
Audit code-review agents, skills, and hooks for structural compliance. Use this when adding or modifying any agent, skill, or hook file, or for a periodic health check of the toolkit. Trigger phrases: "audit the agents", "check compliance", "validate the skills", "are the agents correct", or any time agent/skill files change.
Run eval fixtures against review agents and grade results. Use this after adding or modifying a review agent, to validate detection accuracy, or when the user says "run the evals", "test the agents", "check for regressions", or "how accurate is the agent".
Resume work from a prior session by reading phase progress files in memory/ and active plans. Use this when starting a new session on in-progress work, or when the user says "continue", "pick up where I left off", "resume", or "what was I working on".
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power 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.
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
Has parse errors
Some configuration could not be fully parsed
Three Claude Code plugins for engineering workflows. Install one or all.
dev-team gives Claude Code a full persona-driven development team: an Orchestrator that routes tasks, specialist agents (engineer, QA, architect, reviewers…), skills that encode reusable knowledge, and the four-command feature workflow /specs → /plan → /build → /pr.security-assessment is the security companion. It adds a tool-first /security-assessment pipeline (SAST + AI judgment + false-positive filtering + executive report), a /cross-repo-analysis command for multi-repo attack chains, and an adversarial ML red-team harness (/redteam-model) for self-owned model endpoints.marketplace-dev is the plugin-author's toolkit. It scaffolds new plugins and marketplaces (/scaffold-plugin, /scaffold-marketplace, /init-plugin-eval), audits any plugin for structural compliance (/plugin-audit), advises on the markdown-vs-script agent decision (/agent-type-advisor), and ships the migrated agent/skill authoring toolkit (/agent-create, /agent-add, /agent-remove).dev-team is the foundation: it owns the shared data contract (codebase-recon, ACCEPTED-RISKS.md, unified finding format) that security-assessment builds on, so install dev-team first and add security-assessment when you need it. marketplace-dev is independent — it has no hard dependency on dev-team and can be installed on its own to build or maintain plugins.
| Plugin | What it does | Key commands | Required tools | Optional tools |
|---|---|---|---|---|
| dev-team | Persona-driven development team, reviewer swarm, TDD-gated build loop | /specs, /plan, /build, /pr, /code-review, /triage | jq, gh | semgrep, playwright, hadolint/trivy/grype; auto-detected formatters and test/type/lint runners |
| security-assessment | Tool-first security assessment + red-team pipeline | /security-assessment, /cross-repo-analysis, /redteam-model, /export-pdf | dev-team, Python ≥ 3.10, tier-1 SAST (semgrep, gitleaks, trivy, hadolint, actionlint) | grype, PDF-export deps |
| marketplace-dev | Scaffold, audit, and maintain Claude Code plugins and marketplaces | /scaffold-plugin, /scaffold-marketplace, /plugin-audit, /agent-type-advisor, /agent-create | jq | git |
Plugin names link to each plugin's README, where the full tool list and per-tool install commands live. Claude Code itself is assumed. First time here? Start with dev-team; add security-assessment only when you run full /security-assessment pipelines against target repos, and marketplace-dev when you're building or maintaining plugins.
New here? The Getting Started guide is the full walkthrough — installing each plugin, configuring a project, the day-to-day workflow, and the diagnostic commands.
Quick install of the core plugin:
claude plugin marketplace add bdfinst/agentic-dev-team
claude plugin install dev-team@bfinster
Then run /setup in your project. Optional plugins (security-assessment, marketplace-dev), self-hosted git hosts, install scopes, and the /upgrade flow are all covered in the Getting Started guide.
Four commands drive feature development from idea to pull request:
/specs → /plan → /build → /pr
npx claudepluginhub bdfinst/agentic-dev-team --plugin dev-teamScaffold, audit, and maintain Claude Code plugins and plugin marketplaces: structural review agent, markdown-vs-script decision framework, scaffolding skills (plugin, marketplace, eval), a generalized plugin-audit, and the migrated agent/skill authoring toolkit. Companion plugin to dev-team.
Deep security assessment + adversarial ML red-team: SARIF-first tool orchestration, narrowly-scoped LLM agents, FP-reduction with fallback banner, compliance mapping, service-comm diagramming, and a self-owned-target red-team harness. Companion plugin to dev-team.
Scaffold, audit, and maintain Claude Code plugin-marketplace monorepos. Enforces shipping hygiene, portability, testing, and automated release/catalog sync.
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
Universal multi-agent infrastructure: 26 specialist agents, 20 enforced workflow skills, and a lead orchestrator
Complete project development toolkit: 23 agents, 23 slash commands, 29 lifecycle hooks, and 69 reusable skills for Claude Code workflows
Cross-agent development skills, hooks, orchestration, and optional custom-agent adapters for Claude Code and Codex
AI team workflow harness for Claude Code — specialist agents, shared skills, slash commands, hooks, and staged delegation pipeline.
Interactive skill that analyzes a task, proposes an agent team composition, and creates the team after user confirmation