From 4911884af0365b8ae78a89e3315b62f7ac73fd2f Mon Sep 17 00:00:00 2001 From: Anthony Espirat Date: Thu, 28 May 2026 16:19:01 +0200 Subject: [PATCH 1/3] Add Codex CLI tool glossary --- skills/using-forge/SKILL.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/skills/using-forge/SKILL.md b/skills/using-forge/SKILL.md index b7f2080..63113c3 100644 --- a/skills/using-forge/SKILL.md +++ b/skills/using-forge/SKILL.md @@ -36,19 +36,19 @@ writing-plans ─┬─▶ executing-plans (user picks [1] in-session) Forge skills use canonical Claude-style tool names. Translate those names to the current agent platform at runtime. -| Forge canonical term | Claude Code | OpenCode | -|---|---|---| -| `Agent` | `Agent` | `Task` | -| `Skill` | `Skill` | `skill` | -| `TodoWrite` | `TodoWrite` | `todowrite` | -| `Read` | `Read` | `read` | -| `Write` | `Write` | `write` | -| `Edit` | `Edit` | `edit` or `apply_patch` | -| `Bash` | `Bash` | `bash` | -| `Glob` | `Glob` | `glob` | -| `Grep` | `Grep` | `grep` | -| `WebFetch` | `WebFetch` | `webfetch` | -| `AskUserQuestion` | `AskUserQuestion` | `question` | +| Forge canonical term | Claude Code | OpenCode | Codex CLI | +|---|---|---|---| +| `Agent` | `Agent` | `Task` | `spawn_agent` | +| `Skill` | `Skill` | `skill` | `$skill` | +| `TodoWrite` | `TodoWrite` | `todowrite` | plan tracking | +| `Read` | `Read` | `read` | shell/read filesystem | +| `Write` | `Write` | `write` | shell/write filesystem | +| `Edit` | `Edit` | `edit` or `apply_patch` | `apply_patch` | +| `Bash` | `Bash` | `bash` | `shell` | +| `Glob` | `Glob` | `glob` | shell/glob search | +| `Grep` | `Grep` | `grep` | shell/search | +| `WebFetch` | `WebFetch` | `webfetch` | web search / MCP | +| `AskUserQuestion` | `AskUserQuestion` | `question` | ask user in chat | Downstream Forge skills should use the Forge canonical term. Do not repeat per-platform tool mappings unless a platform has materially different behavior that changes the instruction. From ad2bc08699c0f7bfa2d67479228e6bd25d405b63 Mon Sep 17 00:00:00 2001 From: Anthony Espirat Date: Thu, 28 May 2026 16:48:54 +0200 Subject: [PATCH 2/3] Allow multi-file plan artifacts --- skills/writing-plans/SKILL.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/skills/writing-plans/SKILL.md b/skills/writing-plans/SKILL.md index 84969c5..e5e29d4 100644 --- a/skills/writing-plans/SKILL.md +++ b/skills/writing-plans/SKILL.md @@ -11,11 +11,12 @@ Turn a free-form dev task into a concrete plan on disk. Do NOT write code here. ## Output artifact -A single markdown file at `.forge/plan/{slug}.md` in the project's working directory. +Default to a single markdown file at `.forge/plan/{slug}.md` in the project's working directory. - `{slug}` = lowercased Linear ticket id (e.g. `eng-123`) if present, else a short kebab-case slug from the task goal (≤ 40 chars, no dates). - Write with the `Write` tool — it creates parent directories. - On re-invocation with change requests, **overwrite** the same file. No stale versions. +- If a multi-step plan needs multiple tightly related files, use a folder: `.forge/plan/{slug}/*.md`. Put the entry point at `.forge/plan/{slug}/plan-root.md`; it must include a short plan description plus an index of every related file with a one-line purpose. ## Process @@ -60,7 +61,7 @@ Fix issues inline. No need to re-review — just fix and move on. Print exactly this block and stop. Do NOT start executing. ``` -PLAN: .forge/plan/{slug}.md +PLAN: <.forge/plan/{slug}.md or .forge/plan/{slug}/plan-root.md> <3-5 line summary — goal + step count + key risks> From 468e72834d075c5060fc24a75f4fc1ec4299c97f Mon Sep 17 00:00:00 2001 From: Anthony Espirat Date: Thu, 28 May 2026 16:59:05 +0200 Subject: [PATCH 3/3] Revert "Allow multi-file plan artifacts" This reverts commit ad2bc08699c0f7bfa2d67479228e6bd25d405b63. --- skills/writing-plans/SKILL.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/skills/writing-plans/SKILL.md b/skills/writing-plans/SKILL.md index e5e29d4..84969c5 100644 --- a/skills/writing-plans/SKILL.md +++ b/skills/writing-plans/SKILL.md @@ -11,12 +11,11 @@ Turn a free-form dev task into a concrete plan on disk. Do NOT write code here. ## Output artifact -Default to a single markdown file at `.forge/plan/{slug}.md` in the project's working directory. +A single markdown file at `.forge/plan/{slug}.md` in the project's working directory. - `{slug}` = lowercased Linear ticket id (e.g. `eng-123`) if present, else a short kebab-case slug from the task goal (≤ 40 chars, no dates). - Write with the `Write` tool — it creates parent directories. - On re-invocation with change requests, **overwrite** the same file. No stale versions. -- If a multi-step plan needs multiple tightly related files, use a folder: `.forge/plan/{slug}/*.md`. Put the entry point at `.forge/plan/{slug}/plan-root.md`; it must include a short plan description plus an index of every related file with a one-line purpose. ## Process @@ -61,7 +60,7 @@ Fix issues inline. No need to re-review — just fix and move on. Print exactly this block and stop. Do NOT start executing. ``` -PLAN: <.forge/plan/{slug}.md or .forge/plan/{slug}/plan-root.md> +PLAN: .forge/plan/{slug}.md <3-5 line summary — goal + step count + key risks>