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 config/SOUL.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Identity

I am a **Lead Engineer** — the bridge between an operator's intent and the team
I am a **Project Manager** — the bridge between an operator's intent and the team
that ships it. I own one repository end to end: its board, its quality bar, and
the coding agents that do the building. I read code deeply, triage and spec the
work, dispatch it to my board, adjudicate reviews, and own the outcome — merged,
Expand Down
28 changes: 14 additions & 14 deletions protoagent.bundle.yaml
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# A protoAgent plugin BUNDLE (ADR 0040) — the Lead Engineer tier of the
# portfolio→team hierarchy. This repo is the BUNDLE and its REFERENCE HOST: the
# manifest pins the plugin set and config/SOUL.md carries the frozen Lead Engineer
# persona (dogfooded on the protoAgent repo itself, 2026-07, then frozen as the
# shipped archetype — see protoAgent's archetype-catalog.json `lead-engineer` row).
# The Project Manager archetype — DEV/REFERENCE HOST manifest. The CANONICAL
# bundle users install lives at github.com/protoLabsAI/project-manager-stack
# (that's what protoAgent's archetype-catalog `project-manager` row points at);
# keep this copy content-synced with it. Persona: dogfooded on the protoAgent
# repo itself (2026-07), frozen as the shipped archetype + soul preset.
#
# Install (onto any host): python -m server plugin install <this-repo-url>
#
# A Lead Engineer focuses on ONE repo and a set of coding agents. The Portfolio
# Manager tier (portfolio plugin, ADR 0055) treats each Lead Engineer as a board it
# A Project Manager focuses on ONE repo and a set of coding agents. The Portfolio
# Manager tier (portfolio plugin, ADR 0055) treats each Project Manager as a board it
# can dispatch to over A2A and read back — so this bundle is deliberately the team
# subset of the old pm-stack: project_board (runs the board + spawn loop) WITHOUT
# portfolio (that's the manager-of-teams, a separate bundle).
Expand All @@ -29,10 +29,10 @@
# manifest into a scratch agent and probe every declared console view). Keep member
# entries on ONE line — scripts/check_bundle_updates.py rewrites the `ref:` in place.

id: lead-engineer
name: Lead Engineer
id: project-manager
name: Project Manager
description: >-
A single-repo technical lead — the bridge between an operator's intent and the
A single-repo project manager — the bridge between an operator's intent and the
team that ships it. It reads code deeply but never holds the keyboard: its file
tools are read-only, and every change ships through the board — decomposed into
features, dispatched to a coding agent in a disposable per-feature git worktree,
Expand Down Expand Up @@ -80,9 +80,9 @@ config: # recommended defaults (you
agent_browser:
panel_mode: full

# Agent archetype (ADR 0042) — presents this bundle as a "Lead Engineer" agent type
# Agent archetype (ADR 0042) — presents this bundle as a "Project Manager" agent type
# in the new-agent picker. Additive metadata; it doesn't change the bundle shape.
archetype:
label: Lead Engineer
icon: Wrench
blurb: Single-repo technical lead — reads deeply, never holds the keyboard; ships every change through a board of coding agents and reports back as it merges.
label: Project Manager
icon: ClipboardList
blurb: Single-repo project manager — reads deeply, never holds the keyboard; ships every change through a board of coding agents and reports back as it merges.
Loading