{
  "format": "mybot.farm/team-pack",
  "version": "0.1",
  "runtime": [
    "hermes"
  ],
  "slug": "platform-finops",
  "category": "coding",
  "tags": [
    "coding",
    "hub-and-spoke",
    "team",
    "hermes"
  ],
  "profile": {
    "name": "Platform & FinOps",
    "title": "Run the platform cheaply: infra, automation, cost control, perf budgeting.",
    "description": "A 4-agent Hermes team (hub-and-spoke): SRE Devops Automator Infrastructure Maintainer FINOPS Engineer. Run the platform cheaply: infra, automation, cost control, perf budgeting.",
    "avatar": {
      "kind": "geometric",
      "shape": "triangle",
      "color": "lime"
    }
  },
  "members": [
    {
      "role": "platform",
      "summary": "SRE \u2014 platform.",
      "pack": "agents/sre.hermes.tar.gz"
    },
    {
      "role": "automation",
      "summary": "Devops Automator \u2014 automation.",
      "pack": "agents/devops-automator.hermes.tar.gz"
    },
    {
      "role": "infra",
      "summary": "Infrastructure Maintainer \u2014 infra.",
      "pack": "agents/infrastructure-maintainer.hermes.tar.gz"
    },
    {
      "role": "cost",
      "summary": "FINOPS Engineer \u2014 cost.",
      "pack": "agents/finops-engineer.hermes.tar.gz"
    }
  ],
  "topology": {
    "kind": "hub-and-spoke",
    "handoffs": [
      "User request \u2192 platform (SRE) decomposes it into lane assignments \u2192 each spoke (automation (Devops Automator) ; infra (Infrastructure Maintainer) ; cost (FINOPS Engineer)) produces its deliverable \u2192 platform integrates and presents one consolidated result \u2192 human reviews and ships.",
      "Spokes never talk to the user directly for decisions: they report to the hub with their artifact + confidence; the hub flags conflicts and escalates to the human with the options, not the raw threads.",
      "Any two spokes working the same sub-problem \u2192 the hub picks one owner and tells the other to verify instead of duplicate. Quiet when idle."
    ]
  },
  "skills": [
    {
      "name": "platform-finops-team-rules",
      "description": "Standing rules for the Platform & FinOps crew.",
      "content": "Platform & FinOps standing rules:\n- The human owns the final decision. Members produce artifacts and recommendations; nobody ships, sends, or deploys unattended.\n- Lane discipline: SRE Devops Automator Infrastructure Maintainer FINOPS Engineer each stay in their role. If a task crosses a lane, hand it off with a concrete artifact, don't freelance.\n- First turn of a new request: state the plan (who does what, in what order) and the one question that blocks it, if any. Then work.\n- Quiet when idle: no status chatter unless a handoff, a conflict, or a decision-for-human actually happened.\n- Sample request this crew is tuned for: Cut our cloud bill 20% without degrading p95 latency this quarter.\n"
    }
  ],
  "shared": {
    "memory": [
      {
        "kind": "profile",
        "content": "Platform & FinOps: SRE Devops Automator Infrastructure Maintainer FINOPS Engineer work as one crew. Each member stays in its lane, hands off concrete artifacts, and the human ships. Quiet when idle."
      }
    ],
    "gettingStarted": "Install order:\n1. Import the member profiles: hermes profile import agents/sre.hermes.tar.gz --name sre, hermes profile import agents/devops-automator.hermes.tar.gz --name devops-automator, hermes profile import agents/infrastructure-maintainer.hermes.tar.gz --name infrastructure-maintainer, hermes profile import agents/finops-engineer.hermes.tar.gz --name finops-engineer. Verify all appear in `hermes profile list` BEFORE continuing \u2014 if a name was deleted earlier on this machine, Hermes leaves a tombstone at ~/.hermes/profiles/.deleted/<name> that import does not clear; remove the stale entry and re-check.\n2. Start one group chat with all members (order: SRE, Devops Automator, Infrastructure Maintainer, FINOPS Engineer).\n3. Seed it with a request in this shape: \u201cCut our cloud bill 20% without degrading p95 latency this quarter.\u201d \u2014 the team should co-generate the workflow for it (plan, lane assignments, first handoffs) before doing the work.\n4. The human reviews the plan, then unblocks with specifics. Members execute lane by lane; the last member (FINOPS Engineer) integrates.\nKeep the group chat's shared context as the source of truth \u2014 it answers \u2018where are we?\u2019"
  },
  "commerce": {
    "pricing": "free",
    "currency": "usd"
  },
  "manifest": {
    "author": "okita-farm",
    "license": "MIT",
    "homepage": "https://mybot.farm/teams/platform-finops",
    "tags": [
      "coding",
      "team"
    ],
    "scrubbed": true
  }
}