agentleFS
YomudoglyYomudogly/oh-my-agy/skills/team/SKILL.md

team

Skill4 starsChanged todayMITView on GitHub

[oh-my-agy] N coordinated subagent workers on a shared, leader-owned task board, built on Antigravity invoke_subagent/send_message. Use only for an explicit $team request when an approved plan benefits from parallel lanes, task-state tracking, or workspace isolation.

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • ncklrsSkill

    seo-content-strategist

    Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use only for an explicit $team request (for example $team 3:executor "implement X"), or when an active $ultragoal/$autopilot plan calls for …

    line 10
  2. Distinctive:

    Do not launch nested teams.

    line 22
  3. Very specific:

    Fail-closed task-board integrity: before scheduling a new wave or declaring completion, validate .omagy/state/team/<team>/tasks.json (or …

    line 49
  4. Very specific:

    If a task fails or blocks after retries, mark it "blocked" and cascade "blocked" (result:"blocked-by:<id>") to downstream tasks whose …

    line 50
  5. Very specific:

    When amending a team plan mid-run ($team --amend.

    line 51
  6. Distinctive:

    Only the leader edits the board.

    line 54
  7. Very specific:

    Evidence archival before cleanup: before removing any isolated worker branch/worktree, copy validated .omagy/evidence/task-*.json (and …

    line 90
  8. Very specific:

    Finish: only when pending=0, in_progress=0, failed=0 (or failures are explicitly acknowledged), and all isolated worker branches are …

    line 93
  9. Very specific:

    When a leader-owned .omagy/ultragoal/goals.json exists, workers return task evidence only.

    line 97
  10. Distinctive:

    Never kill all subagents to "reset" unless the user aborts.

    line 103

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Team Skill

When to use

Use only for an explicit $team request (for example $team 3:executor "implement X"), or when an active $ultragoal/$autopilot plan calls for coordinated parallel lanes. Team is explicit and outside the default workflow. Ordinary work never silently becomes a team run.

In Antigravity, workers are subagents:

  • launch: invoke_subagent (several entries in one call run concurrently)
  • coordinate: send_message to a worker's conversation ID
  • monitor/stop: manage_subagents (list, kill)
  • isolate: prefer Workspace: "share" (shared git object store with an independent branch, like git worktree) over "branch" (isolated clone deleted when the subagent is killed) whenever workers write overlapping areas or commit recovery matters.

Inputs and preconditions

  • Launch shape: $team [N:role] "<task>" (plus $team --amend for live mid-flight DAG board mutation and $team --arena for N=2..3 competing Workspace: "share" candidate bake-offs on high-risk slices — see references/amend-and-arena.md). Default role is executor. Use test-engineer, designer, debugger, etc. for specialized lanes. Max 6 concurrent workers.
  • Ground the task first: reuse or create .omagy/context/{slug}-*.md (target, evidence, constraints, unknowns, touchpoints). Prefer an approved spec or plan (.omagy/specs/, .omagy/plans/).
  • Do not launch nested teams. Workers never spawn subagents.
  • Work-Shape Model Routing (Splittable vs Cohesive):
    • Splittable / Quick (isolated single-file edits, mechanical renames, doc/config updates, targeted lookups): fan out across parallel workers with Model: "flash".
    • Cohesive / Deep (multi-file feature slices, shared state/types, stateful debugging): keep together in a single worker with Model: "inherit" rather than splitting across workers that would fight over interfaces.
    • Ultrabrain / Review & Architecture (architect, critic, tracer, security-reviewer): use Model: "pro" (or "inherit" when the session already runs a frontier reasoning model).

Task board & DAG wave scheduling (leader-owned)

.omagy/state/team/<team>/tasks.json:

{
  "team": "<team>",
  "objective": "<task>",
  "created_at": "<ISO>",
  "updated_at": "<ISO>",
  "tasks": [
    {"id": "1", "title": "...", "role": "executor", "model": "inherit|flash|pro", "owned_paths": ["src/auth/**"], "acceptance": ["..."],
     "requires_code_change": true, "depends_on": [], "fingerprint": "<sha1-or-short-hash-of-title+owned_paths+acceptance>",
     "status": "pending|in_progress|completed|failed|blocked", "worker": null, "conversation_id": null, "result": null}
  ]
}

Also write .omagy/state/team-state.json (mode:"team", active:true, current_phase:"executing", state.team:"<team>").

  • DAG Wave Scheduling, Capacity Reservation & Fail-Closed Task Validation:
    • Tasks form an explicit DAG via depends_on. Launch ready waves (status:"pending" whose depends_on tasks are all "completed"), up to 6 concurrent workers per wave.
    • One-task-per-worker capacity reservation & rollback: reserve at most 1 active (in_progress) task per worker at a time. If invoke_subagent or send_message dispatch fails, immediately roll the task's claim back to status: "pending" (worker: null, conversation_id: null) so it is not stranded as a phantom in_progress claim.
    • Fail-closed task-board integrity: before scheduling a new wave or declaring completion, validate .omagy/state/team/<team>/tasks.json (or run sh <plugin>/hooks/run.sh validate-team-tasks <workspace> <team>). Any missing, unreadable, symlinked, or malformed task board is a hard blocker (team_task_read_failed) — never treat an unreadable board as "0 pending tasks".
    • If a task fails or blocks after retries, mark it "blocked" and cascade "blocked" (result:"blocked-by:<id>") to downstream tasks whose depends_on transitively includes <id>, while continuing independent branches.
    • When amending a team plan mid-run ($team --amend; see references/amend-and-arena.md), perform a leader-owned atomic read-modify-write on .omagy/state/team/<team>/tasks.json (and tasks/task-<id>.json), recompute fingerprint (title + owned_paths + acceptance + upstream fingerprints) so unchanged "completed" tasks stay "completed", steer in-flight workers safely via send_message without losing Workspace: "share" commits, and immediately re-validate with sh <plugin>/hooks/run.sh validate-team-tasks <cwd> <team> --json.
    • For high-ambiguity or high-risk slices ($team --arena; see references/amend-and-arena.md), run N=2..3 parallel executor candidates in Workspace: "share" against one shared test contract, gate winner selection through independent verifier + critic review (VERIFICATION_VERDICTS + verified_head), merge/cherry-pick the winner cleanly, and archive runner-up diffs under .omagy/artifacts/.

Only the leader edits the board. Workers report results in their final message, and the leader transitions status.

requires_code_change default. Set it explicitly on every task:

  • false when the task is analysis-only: its wording asks to analyze, audit, review, research, explain, compare, or summarize, or it explicitly says not to change code. A report or summary without a named output file also counts as analysis-only.
  • false for read-only roles: explore, researcher, planner, architect, critic, tracer, code-reviewer, security-reviewer, verifier, vision.
  • true otherwise, for execution roles (executor, debugger, test-engineer, designer) and any task that adds, fixes, changes, or writes a file.

Operational steps

  1. Decompose the task into independent tasks with disjoint owned_paths where possible, testable acceptance, and explicit dependencies. If two tasks must touch the same file, serialize them via depends_on or give them isolated workspaces.
  2. Write the board, then launch the ready tasks in one invoke_subagent call (one entry per task, at most 6). Each worker prompt must be self-contained:
    TEAM <team> — TASK <id>: <title>
    Objective: <objective (or path to brief generated by sh <plugin>/hooks/run.sh goal-brief)>
    Owned paths (edit only these): <paths>
    Acceptance: <criteria>
    Context: <spec/plan/context paths>
    Verification: <exact commands>
    Constraints: do not edit .omagy/state/**, do not spawn subagents, report conflicts instead of editing outside scope. A permission denial or a refusal by the user is final for what that call was meant to do: never reach that result with another tool, command, path, or host — report TASK <id>: BLOCKED upward immediately.
    Evidence (when requires_code_change is true): write .omagy/evidence/task-<id>.json with {"team":"<team>","taskId":"<id>","verdict":"unit-test-verified","verified_head":"<40-char-git-sha>","summary":"...","verification":[{"command":"...","result":"passed","output":"..."}],"unverified":[]} (and optional verbose logs to .omagy/evidence/task-<id>-report.md so your reply stays <15 lines) and include EVIDENCE_RECORDED: .omagy/evidence/task-<id>.json on its own line.
    Report format: TASK <id>: COMPLETED|COMPLETED_WITH_CONCERNS|NEEDS_CONTEXT|FAILED|BLOCKED / Changed files / Verification / EVIDENCE_RECORDED / Concerns or Blockers
    Record each conversation_id, then set status:"in_progress". Surface [oh-my-agy HUD](sidecar://oh-my-agy/hud/) once when launching the first wave so the user can watch the live DAG board in the Auxiliary Pane.
  3. Wait for worker messages. Do not poll; the system wakes you when a worker reports. Optionally set a liveness schedule timer with TimerCondition: "any".
  4. On each report: if a worker reports NEEDS_CONTEXT, answer via send_message to its existing conversation_id with the missing interface or file detail. If a worker reports COMPLETED_WITH_CONCERNS, evaluate the concern in the leader lane before marking completed. If a worker fails/stalls twice on Model: "flash" or "inherit", escalate the retry to the next model tier (flash -> inherit -> pro). For tasks with requires_code_change: true, validate .omagy/evidence/task-<id>.json with read_file (not the shell). Reject the report unless all of these hold:

    • the file is inside <workspace>/.omagy/evidence/, is not a symlink, and is valid JSON of at most 1 MiB;
    • team and taskId match this task;
    • summary is real text (not TODO/TBD/placeholder/pending/not run), verdict (when present) is one of VERIFICATION_VERDICTS (live-ui-verified | unit-test-verified | type-check-only | enforcement-verified | formally-verified | verifier-blocked | verifier-failed), and verified_head (or sha, when present on requires_code_change: true tasks) is a valid 7–40 hex commit SHA matching the worker's verified commit;
    • verification is a non-empty array whose every entry has a real non-echo command (echo, printf, true, :, and rem are rejected even when wrapped in env/time/nice), result: "passed", and a real output;
    • unverified is an array (empty, or listing checks that were not run).

    Then re-run the verification command for anything non-trivial, transition the task to completed/failed/blocked with result, and refresh updated_at. Launch newly unblocked tasks. When merely inspecting team status ($hud or status check), stay strictly read-only and never mutate tasks.json or reassign tasks. (Optional scripted check: sh <plugin>/hooks/run.sh verify-evidence <workspace> .omagy/evidence/task-<id>.json <team> <id>. Antigravity's terminal sandbox may deny reading plugin files, in which case it needs BypassSandbox: true. The read_file check above is the default.)

  5. Blocked worker: answer via send_message to the same conversation ID rather than spawning a replacement. For a stuck or looping worker, preserve its work before killing (since manage_subagents kill deletes "branch" workspaces): if it ran in "share" or "branch", ask it once via send_message to commit/report its branch or salvage reachable commits in the leader lane before calling manage_subagents kill on that worker only, then set the task pending and relaunch with a sharper prompt.
  6. Integrate & Shutdown Worktree Preservation:
    • Fail-closed Git integration: when workers used share/branch workspaces, merge their verified verified_head commits into the main workspace in the leader lane. Never auto-resolve merge conflicts with -X theirs or -X ours, and never automatically abort pre-existing manual Git operations (MERGE_HEAD, CHERRY_PICK_HEAD, REVERT_HEAD, BISECT_START, rebase-merge, rebase-apply) in the leader workspace — surface conflict details and stop or resolve both intents explicitly.
    • Evidence archival before cleanup: before removing any isolated worker branch/worktree, copy validated .omagy/evidence/task-*.json (and *-report.md) files into the leader workspace's .omagy/evidence/ directory so task verification evidence outlives worktree cleanup.
    • Porcelain status & unmerged conflict parsing: when parsing git status --porcelain output, always use .trimEnd() (never .trim(), which strips the leading status character of the first entry when the index slot is a space, e.g. " M file"). Treat all 7 git unmerged two-letter porcelain prefixes (DD, AU, UD, UA, DU, AA, UU — including modify/delete UD/DU and add/unmerged AU/UA, not just UU/AA/DD) as active merge/rebase conflicts before declaring integration clean.
    • Submodule-safe worktree detection & --exclude unmerged-commit guard: when checking whether a directory is already a linked git worktree (git rev-parse --git-dir vs --git-common-dir), also check [ -z "$(git rev-parse --show-superproject-working-tree 2>/dev/null)" ] so git submodules are never misclassified as linked worktrees. Record base_commit when creating a worker worktree; before removing any worker branch/worktree or killing a worker with Workspace: "branch", verify in the leader lane that (a) the worker's HEAD is an ancestor of the leader's HEAD (git merge-base --is-ancestor <workerHead> HEAD) and has no commits unreachable from non-worker branches/tags/remotes (worktree_unmerged guard: git rev-list --max-count=1 <workerHead> <workerBranch> --not <leaderHead> <baseCommit> --exclude=<workerBranchPattern> --branches --tags --remotes must return empty so the worker branch ref itself does not hide unmerged commits), and (b) no unpreserved untracked, ignored, or submodule changes remain (git status --porcelain --untracked-files=all --ignored --ignore-submodules=none). Never run git worktree remove --force when untracked or unmerged commits exist. If checkpointing or merging fails, retain the worker branch/workspace and team state (status:"blocked", reason "worktree_unmerged") for recovery instead of deleting it.
  7. Finish only when pending=0, in_progress=0, failed=0 (or failures are explicitly acknowledged), and all isolated worker branches are verified merged. Run integrated verification (tests/lint/typecheck/build) in the leader lane. Write team-state.json terminal (active:false, current_phase:"complete", completed_at).

Team and Ultragoal

When a leader-owned .omagy/ultragoal/goals.json exists, workers return task evidence only. The leader checkpoints the corresponding Ultragoal goal and appends the ledger entry with the integrated verification evidence.

Recovery

  • Worker reports touching files outside its scope: inspect the diff, keep or revert deliberately, and note it on the board.
  • Two workers conflict on the same file: stop the later one, serialize the remaining work, and relaunch.
  • Never kill all subagents to "reset" unless the user aborts. Kill only the exact stale worker.
  • After a server restart (Antigravity stops all subagents): read the board, then revive each in_progress worker by send_message to its recorded conversation_id with a short "resume TASK <id>" note before spawning anything. If a worker cannot be revived, continue that task in the leader lane or relaunch it once with the board context. Do not spawn a replacement only because the original stopped.

Exit and evidence

Report team name, task table (id, role, status, worker result summary), integration/merge notes, leader verification commands with exit codes, failures or blockers, and the terminal state path. Final integration and verification always stay in the leader lane.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.