Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@
},
{
"name": "automated-ai-engineer",
"description": "The autonomous engineer role for a whole portfolio of repositories β€” a run-loop engineer agent and a read-only surveyor agent plus skills for portfolio maintenance, product engineering, and guard-railed self-improvement; generic, configured by the consuming repo's AGENTS.md contract sections",
"description": "The autonomous engineer role for a whole portfolio of repositories β€” a run-loop engineer agent, a read-only surveyor agent, and a meta-engineer that improves the engineer itself from measured evidence, plus skills for portfolio maintenance, product engineering, guard-railed self-improvement, and outside-in agent improvement; generic, configured by the consuming repo's AGENTS.md contract sections",
"version": "1.0.0",
"source": "./plugins/automated-ai-engineer"
}
Expand Down
2 changes: 1 addition & 1 deletion .github/plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@
},
{
"name": "automated-ai-engineer",
"description": "The autonomous engineer role for a whole portfolio of repositories β€” a run-loop engineer agent and a read-only surveyor agent plus skills for portfolio maintenance, product engineering, and guard-railed self-improvement; generic, configured by the consuming repo's AGENTS.md contract sections",
"description": "The autonomous engineer role for a whole portfolio of repositories β€” a run-loop engineer agent, a read-only surveyor agent, and a meta-engineer that improves the engineer itself from measured evidence, plus skills for portfolio maintenance, product engineering, guard-railed self-improvement, and outside-in agent improvement; generic, configured by the consuming repo's AGENTS.md contract sections",
"version": "1.0.0",
"source": "./plugins/automated-ai-engineer"
}
Expand Down
19 changes: 12 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ This is a **tool-neutral plugin marketplace**, not a skills-only bundler. Every
| [`engineering-practices`](plugins/engineering-practices/) | `conventional-release`, `git-commit`, `refactor`, `test-driven-development`, `ways-of-working` | Git commits, conventional releases, refactoring, TDD, and engineering ways of working |
| [`frontend-design`](plugins/frontend-design/) | `astro`, `frontend-design`, `web-design-guidelines` | Astro, frontend design, and web design guidelines |
| [`vibe-coding`](plugins/vibe-coding/) | `needs-stack-mapping`, `allowed-stack-guardrail`, `jargon-free-voice` (skills) Β· `vibe-coding-companion` (agent) | Build a product by conversation alone β€” plain-language companion agent + guardrailed needs-to-stack skills for people with no technical background |
| [`automated-ai-engineer`](plugins/automated-ai-engineer/) | `portfolio-maintenance`, `product-engineering`, `self-improvement` (skills) Β· `automated-ai-engineer`, `portfolio-surveyor` (agents) | The autonomous engineer role for a whole repository portfolio β€” run-loop engineer + read-only surveyor agents with maintenance, product-engineering, and self-improvement skills; configured by the consuming repo's AGENTS.md contract sections |
| [`automated-ai-engineer`](plugins/automated-ai-engineer/) | `portfolio-maintenance`, `product-engineering`, `self-improvement`, `agent-improvement` (skills) Β· `automated-ai-engineer`, `portfolio-surveyor`, `agent-improver` (agents) | The autonomous engineer role for a whole repository portfolio β€” run-loop engineer + read-only surveyor agents, plus a meta-engineer that improves the engineer itself from measured evidence; configured by the consuming repo's AGENTS.md contract sections |
Comment thread
devantler marked this conversation as resolved.

## Installation

Expand Down Expand Up @@ -70,7 +70,7 @@ npx skills add devantler-tech/agent-plugins --skill gitops-knowledge --agent cur
```

> [!IMPORTANT]
> This is a **partial** install path. It resolves all **27 bundled skills**, but **not** the [MCP servers](#mcp-servers) or [custom agents](#custom-agents). For those, use **Claude Code** or **Copilot CLI** above β€” they are the only tools that load a plugin's bundled `.mcp.json` and `agents/` automatically. In **VS Code**, a plugin install delivers the skills only, and MCP servers and agents are added manually (see [MCP servers](#mcp-servers) and [custom agents](#custom-agents) for the exact steps).
> This is a **partial** install path. It resolves all **28 bundled skills**, but **not** the [MCP servers](#mcp-servers) or [custom agents](#custom-agents). For those, use **Claude Code** or **Copilot CLI** above β€” they are the only tools that load a plugin's bundled `.mcp.json` and `agents/` automatically. In **VS Code**, a plugin install delivers the skills only, and MCP servers and agents are added manually (see [MCP servers](#mcp-servers) and [custom agents](#custom-agents) for the exact steps).

## MCP servers

Expand Down Expand Up @@ -131,14 +131,19 @@ build companion for a non-technical audience (design:
deployment to author a `## Stack map` section in its `AGENTS.md` (see the
[plugin README](plugins/vibe-coding/README.md)).

The [`automated-ai-engineer`](plugins/automated-ai-engineer/) plugin bundles two agents β€”
The [`automated-ai-engineer`](plugins/automated-ai-engineer/) plugin bundles three agents β€”
[`automated-ai-engineer`](plugins/automated-ai-engineer/agents/automated-ai-engineer.md) (the
autonomous portfolio-engineer actor) and
autonomous portfolio-engineer actor),
[`portfolio-surveyor`](plugins/automated-ai-engineer/agents/portfolio-surveyor.md) (its read-only
survey subagent) β€” alongside its three engineering skills (design:
[ADR 0002](docs/adr/0002-automated-ai-engineer-plugin-boundary.md)). Same delivery rules; the
survey subagent), and
[`agent-improver`](plugins/automated-ai-engineer/agents/agent-improver.md) (a meta-engineer that
improves the engineer itself from measured evidence) β€” alongside its engineering skills (design:
[ADR 0002](docs/adr/0002-automated-ai-engineer-plugin-boundary.md)). Same delivery rules; VS Code
Comment thread
devantler marked this conversation as resolved.
users copy them to `.github/agents/automated-ai-engineer.agent.md`,
`.github/agents/portfolio-surveyor.agent.md`, and `.github/agents/agent-improver.agent.md`. The
consuming deployment must define the five contract sections (Portfolio map, Trust gate, Cadence,
Memory, Maintainer channels) in its `AGENTS.md` (see the
Memory, Maintainer channels) in its `AGENTS.md` β€” plus **Agent definition locations** and
**Authority model** if it enables `agent-improver` (see the
[plugin README](plugins/automated-ai-engineer/README.md)).

## How it works
Expand Down
4 changes: 2 additions & 2 deletions docs/adr/0002-automated-ai-engineer-plugin-boundary.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ children 2 and 3 a contract to implement.

This also advances the marketplace's own roadmap: [#38](https://github.com/devantler-tech/agent-plugins/issues/38)
Theme 1 wants a flagship bundle that proves plugins are *not skills-only* β€” an agent+skills unit at real
scale. The Automated AI Engineer is exactly that (two agents + three skills).
scale. The Automated AI Engineer is exactly that β€” shipped as two agents + three skills, and since extended to **three agents + four skills** with the `agent-improver` meta-engineer and its `agent-improvement` skill ([#73](https://github.com/devantler-tech/agent-plugins/pull/73)), which improves the engineer itself from measured evidence.

**Name collision to avoid.** An existing `agentic-engineering` plugin bundles SDK / instruction-authoring
/ skill-discovery skills for **building** agentic applications; `engineering-practices` bundles practice
Expand Down Expand Up @@ -57,7 +57,7 @@ local.

### D1 β€” Home of every section: role β†’ plugin, configuration β†’ consumer `AGENTS.md`

**Generic β€” the role (β†’ plugin: the two agents + three skills):**
**Generic β€” the role (β†’ plugin: the agents + skills; two agents + three skills at authoring time, three + four today):**

| Constitution element | Plugin home |
|---|---|
Expand Down
56 changes: 47 additions & 9 deletions plugins/automated-ai-engineer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,23 @@ CI and dependencies healthy) and **advances** it (strategy and roadmaps, oldest-
issue resolution, coverage, performance, refactoring, docs), shipping everything as human-gated
draft PRs.

It bundles two agents β€” **`automated-ai-engineer`** (the actor: the survey β†’ select β†’ act β†’ report
run loop) and **`portfolio-surveyor`** (a read-only subagent that returns one compact survey
digest) β€” and three skills with their canonical home in
It bundles three agents β€” **`automated-ai-engineer`** (the actor: the survey β†’ select β†’ act β†’ report
run loop), **`portfolio-surveyor`** (a read-only subagent that returns one compact survey
digest), and **`agent-improver`** (a meta-engineer that improves the engineer itself from measured
Comment thread
devantler marked this conversation as resolved.
evidence) β€” and skills with their canonical home in
[devantler-tech/agent-skills](https://github.com/devantler-tech/agent-skills):
`portfolio-maintenance` (the run loop), `product-engineering` (the advance playbook), and
`self-improvement` (the guard-railed definition-improvement procedure).
`portfolio-maintenance` (the run loop), `product-engineering` (the advance playbook),
`self-improvement` (the guard-railed definition-improvement procedure), and `agent-improvement`
(the outside-in meta-improvement loop).

**Why both `self-improvement` and `agent-improvement`?** They work at different vantage points and are
complementary, not alternatives. `self-improvement` is one run reflecting on its own memory, banking a
learning per run and distilling on a slow cadence. `agent-improvement` is an **external observer** over
the whole session corpus and every deployed instance at once β€” which is where failures that no single
run can see actually live: errors recurring across hundreds of runs, waste that looks normal from inside
one run, divergence between sibling instances, and drift between a non-version-controlled bootstrap
entry and the contract it points at. Deployments running a single instance with no separate meta-run can
use `self-improvement` alone.

## Consumer setup: the contract sections

Expand All @@ -35,6 +46,25 @@ five named contract sections (ADR 0002 D2) β€” the agents and skills fail closed
**AI-disclosure line** β€” the stable prefix the agents place on everything they author and use to
tell their own prior output apart from human comments under the same login.

**Enabling `agent-improver` adds two more required sections.** The meta-engineer edits the engineer's
own definition, so a deployment that runs it must also define β€” and it fails closed on either being
missing:

- **Agent definition locations** β€” every surface the meta-engineer may change, and which are
version-controlled (ship as a pull request) versus not (bootstrap/loader entries, permission or
approval configuration β€” edited in place, backed up first). Anything not named here is out of scope,
which is what keeps a meta-engineer away from product repositories.
- **Authority model** β€” how much it may change alone, stated separately for **tightening** and
**loosening** a guardrail, and for the prose definition versus the enforcement layer. Deployments
differ: some grant tightening only and route every loosening to the maintainer; others grant
symmetric authority. The agent's own obligations (evidence, reversibility, audit trail, loosenings
shipping alone) hold either way β€” this section only sets the boundary between what it applies itself
and what it hands over.

Also state, in **Memory**, where its scorecard and open verification hypotheses live: the loop depends
on comparing today's numbers against the previous run's and re-checking a change's target metric before
starting new work.

## Runtime guard note

The surveyor's read-only discipline is **prompt-level**; its tool set still includes the shell it
Expand All @@ -44,7 +74,15 @@ subagents), so a prompt-injected survey cannot escalate to writes even in princi

## Delivery

Installing the plugin makes both bundled agents available automatically β€” Claude Code, Copilot CLI,
and VS Code all discover the plugin's `agents/` directory on install (VS Code surfaces
plugin-provided agents in chat alongside your locally defined ones). No manual copy into
`.github/agents` is required.
**Claude Code** and **Copilot CLI** load the plugin's `agents/` directory automatically on install, so
all three agents are available with no manual step. **VS Code consumes agents but does not bundle them
from a plugin** β€” copy each one into your workspace:

```text
.github/agents/automated-ai-engineer.agent.md
.github/agents/portfolio-surveyor.agent.md
.github/agents/agent-improver.agent.md
```

(See the root README's [Custom agents](../../README.md#custom-agents) section for the shared delivery
model.)
Loading
Loading