Skip to content

Epic: Onboard the bmad-bgreat-suite ops personas (sre-lead, devops-lead, security-lead) #1304

Closed

Description

@don-petry

Tracked stories (DELIVERED)

Follow-up (separate): bmad-bgreat-suite#395 (upstream content fix + re-vendor).


Onboard the three bmad-bgreat-suite agents as compliant, @-addressable personas, following the proven qa-lead pattern and the four just onboarded (#1281–#1283). This is the "enable the remaining bmad personas" initiative.

The suite (petry-projects/bmad-bgreat-suite, a Claude Code plugin) defines:

Upstream agent Role (§1.6 — our namespace names the role) Expertise
Morgan (SRE Lead) sre-lead Observability, incident response, SLO/SLI, chaos, postmortems
Riley (DevOps Lead) devops-lead IaC, CI/CD, K8s, GitOps, blue-green/canary
Sam (Security Lead) security-lead Threat modeling, SOC2/HIPAA/PCI/GDPR, supply-chain

Each becomes an advisory-everywhere, wrap-a-vendored-agent persona — exactly the path qa-lead demonstrated. The persona runner is convention-driven, so no new runtime is needed: dropping prompts/<role>/advisory.md and a manifest is enough for the shared runner to serve it. That is the framework's payoff.


The DAG

P1 ── vendor bmad-bgreat-suite into frameworks/  (blocks all persona stories)
       │
       ├── S1 ── sre-lead persona      (manifest + advisory + README + seed evals)
       ├── S2 ── devops-lead persona   (   ""   )
       └── S3 ── security-lead persona (   ""   )
                     │
T  ── create 3 org teams (petry-projects/{sre-lead,devops-lead,security-lead})   [parallel; org mutation]
                     │
V  ── verify: 3 manifests validate; teams resolve closed+notif-off; one advisory
       smoke-test per role in the next ring   (after S1,S2,S3,T)
  • P1 blocks S1–S3 (the manifests reference frameworks/bmad-bgreat-suite/..., which must exist).
  • S1–S3 are parallel after P1 (independent personas).
  • T (teams) is an org-level mutation — parallel, but it's a session/human step (dev-lead can't reliably create org teams via its PR flow), so it's a checklist item on this epic, not a dev-lead story.
  • V gates promotion consideration; it is not itself a code change.

The stories

P1 — Vendor bmad-bgreat-suite into frameworks/ (foundation)

  • Vendor petry-projects/bmad-bgreat-suite under frameworks/bmad-bgreat-suite/ (git subtree, matching bmad-method / bmad-test-architecture).
  • Add frameworks/bmad-bgreat-suite/VENDOR.md pinning commit ae8914e84b87 — the suite has no tags, so pin a SHA (not a version).
  • Confirm the vendored agents' dependency on bmad-method skills resolves (bmad-method is already vendored).
  • AgentShield passes on the vendored tree.
  • Blocks: S1, S2, S3.

S1/S2/S3 — one per role (identical shape; the pattern from #1303)

For <role> in {sre-lead, devops-lead, security-lead}, wrapping bgr-agent-{morgan-sre,riley-devops,sam-security}:

  • personas/<role>/persona.yml — draft; framework-agent layer → the vendored agent path; address.handle: petry-projects/<role>; advisory on mention/issues/discussion; evals.path: evals/<role>/; canary.agent: <role>.
  • prompts/<role>/advisory.md — the read-only/sentinel/marker advisory contract (copy qa-lead's), specialized to the role's domain.
  • personas/<role>/README.md + seed held-out evals (evals/<role>/{dev,holdout}, ≥ a couple synthetic cases; draft is exempt from the count gate).
  • validate-personas.py + validate-cases.py pass.
  • Blocked by: P1.

T — Create the three org teams (session/human step, not dev-lead)

  • petry-projects/{sre-lead,devops-lead,security-lead}, each privacy: closed, notification_setting: notifications_disabled, 0 members. Remove the auto-added creator.
  • Why not a dev-lead story: creating org teams is an org mutation outside dev-lead's PR flow; do it via gh api in-session, like qa-lead's team.

V — Verify (gate, not a code change)

  • All three manifests validate; validate-personas.py green in CI.
  • Each team resolves as a mentionable team (gh api /markdown → team-mention), closed, notifications off.
  • One advisory smoke-test per role in the next ring (mention @petry-projects/<role> on a throwaway .github-private issue; confirm advisory posts with marker and the recursion guard skips it).

Rubber-duck findings (pressure-tested before hand-off)

  1. Vendoring is a hard prerequisite. The agents are NOT in frameworks/ today (only bmad-method, bmad-test-architecture are). Nothing references them until P1. Hence P1 blocks all.
  2. No tags → pin a SHA. bmad-bgreat-suite has no releases; VENDOR.md pins commit ae8914e84b87. (bmad-test-architecture pinned v1.19.0; this can't.)
  3. Handle collisions confirmed the team-handle requirement. @sre-lead is a real Organization, @devops-lead a real User — bare handles would tag strangers. @petry-projects/<role> team handles avoid it (the §4.1 reason), which is what the manifests use.
  4. Roles, not persons (§1.6). sre-lead/devops-lead/security-lead, never Morgan/Riley/Sam. Upstream names stay upstream, referenced only by framework.skill.
  5. No new runtime, no paths needed. Each wraps ONE agent → single evals.path (so these do NOT depend on .github#779). The shared persona runner serves prompts/<role>/advisory.md by convention — the whole reason onboarding is now cheap.
  6. Advisory-only. No write surfaces initially (§3 advisory-by-default). Ops advice, not ops actions.
  7. Overlap with existing roles. security-lead (Sam) overlaps the existing agents/compliance-auditor.md and dependency-audit; devops-lead overlaps auto-rebase/CI tooling. These are ADVISORY personas, not replacements — note the relationship in each README, don't merge.
  8. Promotion is out of scope. All three ship draft with seed evals. Real held-out evals + next→ring0→ring1→stable soak + canary registration are a separate, later epic — not blocked here.

Acceptance criteria (epic)

  • P1 merged: frameworks/bmad-bgreat-suite/ vendored + VENDOR.md pinning ae8914e84b87.
  • S1/S2/S3 merged: three draft persona manifests + advisory prompts + READMEs + seed evals; validate-personas.py green.
  • T done: three closed, notifications-disabled, 0-member teams.
  • V done: three manifests validate; teams resolve; one advisory smoke-test per role passes in the next ring.
  • Each README notes the overlap relationship (finding 7) and links this epic.

Implementation note

Per the plan being solid: S1–S3 and P1 are dev-lead-implementable (well-scoped, real files, single-repo). They are held unlabeled until the go-ahead so the epic can be reviewed first; on approval, add the dev-lead label to P1 (root), then S1–S3 once P1 merges (they're blocked_by P1). T and V are session steps.

Activity

  1. github-actions commented on Jul 18, 2026

    @github-actions
    Contributor

    Thanks for the thorough write-up and DAG breakdown — this is a well-scoped epic with a clear sequencing rationale. Before we kick off implementation, could you confirm the exact SHA you want pinned in VENDOR.md for bmad-bgreat-suite? The issue references ae8914e84b87, but since there are no tags we want to make sure that commit is the intended stable point before P1 is labeled for dev-lead.

  2. don-petry commented on Jul 18, 2026

    @don-petry
    CollaboratorAuthor

    Stories created — DAG live

    Sequencing note: S1–S3 reference frameworks/bmad-bgreat-suite/... which does not exist until P1 merges, so their dev-lead labels are held to avoid the phantom-file churn trap. They get labeled the moment #1306 merges.

  3. don-petry commented on Jul 18, 2026

    @don-petry
    CollaboratorAuthor

    P1 delivered ✅ — #1310 merged; frameworks/bmad-bgreat-suite/ vendored @ ae8914e84b87, VENDOR.md pins the SHA, all 3 agents present. (Upstream content bugs Gemini flagged → bmad-bgreat-suite#395, fix-upstream-then-re-vendor; not in scope here per §2.)

    S1–S3 now unblocked and started — #1307 (sre-lead), #1308 (devops-lead), #1309 (security-lead) re-labeled dev-lead. dev-lead is building the three persona PRs. Next: validate each, then T (teams) + V (verify).

  4. don-petry commented on Jul 18, 2026

    @don-petry
    CollaboratorAuthor

    Epic DELIVERED ✅

    All 8 org personas are now onboarded: qa-lead, dev-lead, pr-review, business-analyst, scrum-master, sre-lead, devops-lead, security-lead — all draft, all @petry-projects/ addressable.

    Follow-ups (not blocking): real (non-seed) evals before any promotion; bmad-bgreat-suite#395 (upstream content fix + re-vendor); product-manager persona; #710 (pr-review canary registration); the fleet-promotion track (reach incubator + new repos) tracked separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions