{
  "format": "mybot.farm/team-pack",
  "version": "0.1",
  "runtime": [
    "hermes"
  ],
  "slug": "shopify-crew",
  "category": "coding",
  "tags": [
    "coding",
    "hub-and-spoke",
    "team",
    "hermes"
  ],
  "profile": {
    "name": "E-Commerce Build Crew",
    "title": "Run web stores profitably: Shopify/Drupal builds, performance, payments, checkout.",
    "description": "A 4-agent Hermes team (hub-and-spoke): Drupal Shopping Cart Wordpress Shopping Cart Payments Billing Engineer Wordpress Performance. Run web stores profitably: Shopify/Drupal builds, performance, payments, checkout.",
    "avatar": {
      "kind": "geometric",
      "shape": "octagon",
      "color": "orange"
    }
  },
  "members": [
    {
      "role": "storefront",
      "summary": "Drupal Shopping Cart \u2014 storefront.",
      "pack": "agents/drupal-shopping-cart.hermes.tar.gz"
    },
    {
      "role": "ecom",
      "summary": "Wordpress Shopping Cart \u2014 ecom.",
      "pack": "agents/wordpress-shopping-cart.hermes.tar.gz"
    },
    {
      "role": "payments",
      "summary": "Payments Billing Engineer \u2014 payments.",
      "pack": "agents/payments-billing-engineer.hermes.tar.gz"
    },
    {
      "role": "performance",
      "summary": "Wordpress Performance \u2014 performance.",
      "pack": "agents/wordpress-performance.hermes.tar.gz"
    }
  ],
  "topology": {
    "kind": "hub-and-spoke",
    "handoffs": [
      "User request \u2192 storefront (Drupal Shopping Cart) decomposes it into lane assignments \u2192 each spoke (ecom (Wordpress Shopping Cart) ; payments (Payments Billing Engineer) ; performance (Wordpress Performance)) produces its deliverable \u2192 storefront 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": "shopify-crew-team-rules",
      "description": "Standing rules for the E-Commerce Build Crew crew.",
      "content": "E-Commerce Build Crew standing rules:\n- The human owns the final decision. Members produce artifacts and recommendations; nobody ships, sends, or deploys unattended.\n- Lane discipline: Drupal Shopping Cart Wordpress Shopping Cart Payments Billing Engineer Wordpress Performance 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: Launch our second storefront on a different platform with shared billing and performance budget.\n"
    }
  ],
  "shared": {
    "memory": [
      {
        "kind": "profile",
        "content": "E-Commerce Build Crew: Drupal Shopping Cart Wordpress Shopping Cart Payments Billing Engineer Wordpress Performance 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/drupal-shopping-cart.hermes.tar.gz --name drupal-shopping-cart, hermes profile import agents/wordpress-shopping-cart.hermes.tar.gz --name wordpress-shopping-cart, hermes profile import agents/payments-billing-engineer.hermes.tar.gz --name payments-billing-engineer, hermes profile import agents/wordpress-performance.hermes.tar.gz --name wordpress-performance. 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: Drupal Shopping Cart, Wordpress Shopping Cart, Payments Billing Engineer, Wordpress Performance).\n3. Seed it with a request in this shape: \u201cLaunch our second storefront on a different platform with shared billing and performance budget.\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 (Wordpress Performance) 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/shopify-crew",
    "tags": [
      "coding",
      "team"
    ],
    "scrubbed": true
  }
}