mirror of
https://github.com/obra/superpowers.git
synced 2026-07-25 03:34:01 +08:00
a868631a8a
The prune in e7ddc25e removed the `## Subagent support` section from
antigravity-tools.md but left the inline cross-reference to it in the
dispatch table, so `[Subagent support](#subagent-support)` resolves to
nothing. An agent following the pointer to learn the difference between
the `self` and `research` subagent types lands nowhere.
Drop the dangling parenthetical. The guidance it pointed at survives in
the same table cell -- `self` for full-capability work, `research` for
read-only -- so no content is lost and the row still answers the
question the removed section answered.
gemini-tools.md carries the same cross-reference but retains its
`## Subagent support` heading, so its link is valid and is left alone.
24 lines
1.5 KiB
Markdown
24 lines
1.5 KiB
Markdown
# Antigravity CLI (`agy`) Tool Mapping
|
|
|
|
Skills speak in actions ("dispatch a subagent", "create a todo", "read a file"). On the Antigravity CLI (`agy`) these resolve to the tools below.
|
|
|
|
| Action skills request | Antigravity CLI equivalent |
|
|
|----------------------|----------------------|
|
|
| Dispatch a subagent (`Subagent (general-purpose):` template) | `invoke_subagent` with a built-in `TypeName` — `self` for full-capability work, `research` for read-only |
|
|
| Task tracking ("create a todo", "mark complete") | a **task artifact** — `write_to_file` with `IsArtifact: true` and `ArtifactType: "task"` (see [Task tracking](#task-tracking)). **Not** `manage_task`, which manages background processes. |
|
|
|
|
## Task tracking
|
|
|
|
Antigravity has **no todo tool** (`manage_task` manages background
|
|
processes — `list`/`kill`/`status`/`send_input` — it is *not* a checklist). When a
|
|
skill says to create a todo list or track tasks, maintain a **task artifact**: a
|
|
markdown checklist saved with `write_to_file` (`IsArtifact: true`,
|
|
`ArtifactMetadata.ArtifactType: "task"`), edited with `replace_file_content` /
|
|
`multi_replace_file_content` as you go.
|
|
|
|
At the start of any multi-step task, create the task artifact listing every step of
|
|
your plan. As you complete each step, edit the artifact to mark it done (`- [x]`).
|
|
If the plan changes, update the checklist. Keep it current — it is your source of
|
|
truth for what remains; once the conversation gets long, re-read it before starting
|
|
each step.
|