{
  "format": "mybot.farm/team-pack",
  "version": "0.1",
  "runtime": [
    "hermes"
  ],
  "slug": "mobile-forge",
  "category": "coding",
  "tags": [
    "coding",
    "pipeline",
    "team",
    "hermes"
  ],
  "profile": {
    "name": "Mobile App Forge",
    "title": "Ship mobile apps through store review: build, release, test automation, review.",
    "description": "A 4-agent Hermes team (pipeline): Mobile App Builder Mobile Release Engineer Test Automation Engineer Code Reviewer. Ship mobile apps through store review: build, release, test automation, review.",
    "avatar": {
      "kind": "geometric",
      "shape": "hexagon",
      "color": "teal"
    }
  },
  "members": [
    {
      "role": "build",
      "summary": "Mobile App Builder \u2014 build.",
      "pack": "agents/mobile-app-builder.hermes.tar.gz"
    },
    {
      "role": "store-release",
      "summary": "Mobile Release Engineer \u2014 store-release.",
      "pack": "agents/mobile-release-engineer.hermes.tar.gz"
    },
    {
      "role": "tests",
      "summary": "Test Automation Engineer \u2014 tests.",
      "pack": "agents/test-automation-engineer.hermes.tar.gz"
    },
    {
      "role": "review",
      "summary": "Code Reviewer \u2014 review.",
      "pack": "agents/code-reviewer.hermes.tar.gz"
    }
  ],
  "topology": {
    "kind": "pipeline",
    "handoffs": [
      "User request \u2192 build (Mobile App Builder) \u2192 store-release (Mobile Release Engineer) \u2192 tests (Test Automation Engineer) \u2192 review (Code Reviewer) \u2192 human reviews and ships. Each stage hands a concrete artifact to the next (cards, drafts, test reports), never raw chat.",
      "Re-work loop: if the review output is rejected (by the human or a downstream gate) \u2192 the failing stage gets a re-work note with the specific gap \u2192 re-runs only the failed stage \u2192 artifact flows down again. No stage silently rewrites an earlier stage's work.",
      "Scope drift: if the request lands outside build's lane \u2192 build says so in the first turn and re-scopes with the human before any member starts work."
    ]
  },
  "skills": [
    {
      "name": "mobile-forge-team-rules",
      "description": "Standing rules for the Mobile App Forge crew.",
      "content": "Mobile App Forge standing rules:\n- The human owns the final decision. Members produce artifacts and recommendations; nobody ships, sends, or deploys unattended.\n- Lane discipline: Mobile App Builder Mobile Release Engineer Test Automation Engineer Code Reviewer 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: Take our iOS app to the App Store: release notes, screenshots pipeline, store-ready build.\n"
    }
  ],
  "shared": {
    "memory": [
      {
        "kind": "profile",
        "content": "Mobile App Forge: Mobile App Builder Mobile Release Engineer Test Automation Engineer Code Reviewer 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/mobile-app-builder.hermes.tar.gz --name mobile-app-builder, hermes profile import agents/mobile-release-engineer.hermes.tar.gz --name mobile-release-engineer, hermes profile import agents/test-automation-engineer.hermes.tar.gz --name test-automation-engineer, hermes profile import agents/code-reviewer.hermes.tar.gz --name code-reviewer. 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: Mobile App Builder, Mobile Release Engineer, Test Automation Engineer, Code Reviewer).\n3. Seed it with a request in this shape: \u201cTake our iOS app to the App Store: release notes, screenshots pipeline, store-ready build.\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 (Code Reviewer) 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/mobile-forge",
    "tags": [
      "coding",
      "team"
    ],
    "scrubbed": true
  }
}