@akira-tl/forgerelay 0.1.0

package/skills/subagent-delegation/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: subagent-delegation
+description: Delegate coding tasks to user-configured ForgeRelay subagents.
+---
+
+# Subagent Delegation
+
+Use this skill when the user explicitly asks to delegate work to another coding
+agent, use a named subagent, get a second opinion, compare approaches, or run
+a subagent-like workflow.
+
+Do not use subagents silently. Tell the user when another subagent is
+being used.
+
+## Core commands
+
+Use only these commands for normal delegation:
+
+```bash
+forgerelay agents ls
+forgerelay agents run <profile-or-provider-or-id> "<prompt>"
+forgerelay agents show <id>
+```
+
+`ls` shows existing subagent sessions for the current workspace. ForgeRelay scopes
+it automatically from the shell environment injected by the workspace tool.
+
+`run <profile> "<prompt>"` starts a new configured profile and prints a
+ForgeRelay agent id.
+
+`run <provider> "<prompt>"` starts a raw built-in provider when no configured
+profile is needed. Built-in providers are listed by `open_workspace`.
+
+`run <id> "<prompt>"` sends a follow-up to an existing agent.
+
+`show <id>` prints status and the latest response. If the agent is still
+running, `show` waits briefly. If there is still no final response, call `show`
+again later.
+
+Do not run provider CLIs such as `codex`, `claude`, `opencode`, `pi`,
+`cursor-agent`, or `copilot` directly unless you are explicitly debugging
+ForgeRelay agent integration.
+
+## Choosing a profile
+
+Choose profiles from the compact subagent profile catalog returned by
+`open_workspace`. Use the profile name with `forgerelay agents run`. If no
+profile fits and delegation is still appropriate, use a built-in provider name
+from `open_workspace`.
+
+Profiles may declare a model and optional thinking level. To override the
+configured/default provider model or thinking level for a run, pass `--model`
+or `--thinking`:
+
+```bash
+forgerelay agents run <profile-or-provider> --model <model> "<prompt>"
+forgerelay agents run <profile-or-provider> --thinking <level> "<prompt>"
+```
+
+Use `--thinking` only when the user asks for a specific reasoning depth or when
+the task clearly needs a different effort than the configured profile default.
+Thinking values are provider-specific passthrough values. Use names supported by
+the selected local agent harness; ForgeRelay does not translate values between
+providers.
+
+Good delegation targets:
+
+- `reviewer`: second opinion, bug risk, security risk, test gaps.
+- `explorer`: read-only codebase investigation.
+- `implementer`: focused implementation when the user asked for delegation.
+
+Do not delegate ordinary coding work just because a profile exists. Use normal
+ForgeRelay tools unless the user asked for delegation, another agent's opinion,
+parallel work, or a named subagent.
+
+## Worker prompts
+
+Agents start with only the prompt you send plus their configured profile
+instructions. Make prompts self-contained.
+
+Implementation prompt shape:
+
+```text
+Goal:
+<clear goal>
+
+Context:
+<repo/module/user constraints>
+
+Relevant files:
+<paths and why they matter>
+
+Acceptance criteria:
+- <criterion>
+
+Rules:
+- Keep changes focused.
+- Do not perform unrelated refactors.
+- Report blockers clearly.
+```
+
+Read-only investigation prompt shape:
+
+```text
+Question:
+<specific question>
+
+Scope:
+<files/directories/modules to inspect>
+
+Rules:
+- Do not modify files.
+- Cite relevant file paths and symbols.
+- Separate facts from guesses.
+```
+
+## After the worker responds
+
+Always review the result before presenting it as verified.
+
+For write-capable tasks, inspect changed files and run or explain relevant
+tests. For read-only tasks, verify that important claims are supported by repo
+evidence.
+
+Be transparent in the final response:
+
+```text
+I used <profile>. It reported <summary>. I verified <checks>. Remaining risk:
+<risk or none>.
+```
+
+Never hide that a subagent was used.