dev-team
Team planning, leadership, coding and review roles, feature coordination, and program status skills.
Setup
If this plugin is uninitialized or a command fails, follow the plugin setup guide for its required CLIs, configuration, and local diagnosis.
Community help
If the setup checks leave a reproducible Agent IX dev-team bug that blocks progress, join the Agent IX Discord. Community help is a last resort for Agent IX product bugs, not a help desk for local credentials, machine setup, third party tools, or unrelated projects. See setup.md for what to include.
Skills
| Skill | Action |
|---|---|
team-planner | Turn an idea into a structured Linear plan with dependencies and ready tickets. |
code-lead | Run a team's coding lane through specs, coding, review, and merge. |
team-minder | Watch a team's agents on an interval and unstick idle or blocked ones by message. |
team-retro | Measure on a schedule whether a team's work is landing on its gate tickets, score each role, and name the repeating loops. |
coder | Implement an assigned ticket in its worktree and open the PR. |
reviewer | Run applicable review methods and record findings against a PR and ticket. |
feature-request | Record a new capability request as a buildable Linear ticket. |
repo-auditor | Answer a bounded, read-only repository measurement question with cited evidence. |
spec-steward | Own the spec-gap queue, resolve implementation blockers, and cancel ceremony. |
feature-feedback | Report observed strengths, friction, and gaps after using a feature. |
feature-check | Check delivered behavior against each ticket acceptance criterion. |
status-report | Report program progress, blockers, and next actions from Linear evidence. |
program-reviewer | Run a seven-step program review and publish an evidence-backed HTML report. |
team-planner and status-report use Linear and ix-board for structured project status and blockers. reviewer can invoke review methods from dev-tools and specification methods from Quoin when installed. coder can use dev-tools:rust-style for Rust work. Get companion plugins from the Agent IX marketplace and install them as ix-board@agent-ix, dev-tools@agent-ix, or quoin@agent-ix when the corresponding methods are needed. The role skills report unavailable methods rather than inventing results.
team-retro runs the ix-board retro commands (snapshot, delta, backfill) on a schedule, so it needs an ix-board build that includes them (ix-board retro --help lists them). It stores its data under ~/.local/state/team-retro (or $TEAM_RETRO_HOME), outside every repository. code-lead includes scripts/team-gate, a wrapper that logs each gate run and re-pin for the retro; see skills/code-lead/references/gate-log.md.
The planner accepts a new idea as well as an existing focus. For a large system it establishes domain boundaries, architecture layers, specifications, tests, and blocker relations before dispatching executable tickets. Its current source workflow came from Agent IX; check your own tracker and governance before applying it elsewhere.
Install
The repository is one plugin. The same skills/ tree is used by all four hosts.
| Host | Install |
|---|---|
| Claude Code | claude plugin marketplace add agent-ix/agent-plugins then claude plugin install dev-team@agent-ix |
| Codex | codex plugin marketplace add agent-ix/agent-plugins then codex plugin add dev-team@agent-ix |
| GitHub Copilot CLI | copilot plugin install agent-ix/dev-team |
| OpenCode | Add "https://raw.githubusercontent.com/agent-ix/dev-team/main/skills/" to the skills array in your opencode.jsonc; the URL serves this repository's skills/index.json catalog. |
Claude uses .claude-plugin/plugin.json, Codex and Copilot use the root portable plugin.json, and OpenCode uses the remote skill catalog. The Agent IX public marketplace pins reviewed versions for Claude and Codex. The .codex-plugin/plugin.json file supports older Codex plugin loaders. No host-specific copy of a skill is maintained.
License
MIT. See LICENSE. See CONTENT_RIGHTS.md for source-content rules.