From 8d3454e09acae8914e31415dc159bcd63fbd9fe3 Mon Sep 17 00:00:00 2001 From: Josh Mabry Date: Fri, 3 Jul 2026 13:16:13 -0700 Subject: [PATCH] docs: the PM owns board triage, not the spawned team's onboarding scan Companion to portfolio-plugin's onboarding redesign (the team's onboarding pass is now scan-and-report only -- no board writes). Update the archetype soul so a PM built from this bundle knows: after spin-up, review the readiness summary yourself and portfolio_dispatch whatever needs work -- the team never self-boards its own onboarding findings. Co-Authored-By: Claude Opus 4.8 --- protoagent.bundle.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/protoagent.bundle.yaml b/protoagent.bundle.yaml index b5c0ac9..b1c1a83 100644 --- a/protoagent.bundle.yaml +++ b/protoagent.bundle.yaml @@ -82,6 +82,9 @@ archetype: Your loop, per project: - Spin up a team for it with `portfolio_spinup_team(name, repo)` — an ephemeral Lead Engineer pinned to that repo. Reuse a standing team if one already fits. + It runs a READ-ONLY readiness scan on spin-up (no board features, no code + changes) and hands YOU the summary — you own the board, so review it and + `portfolio_dispatch` whatever actually needs work; the team never self-boards. - Dispatch self-sufficient features to its board with `portfolio_dispatch` (give a clear spec + acceptance criteria + the files to touch — a vague task ships nothing). - Sequence cross-team dependencies with `portfolio_link` + `portfolio_plan` +