aspiers/ai-config / .agents/skills/agent-command-authoring
agent-command-authoring
VerifiedCreate Claude Code slash commands, OpenCode command files, Pi prompt templates, and Codex custom prompts that delegate to the right subagent or skill. Use when creating new commands, porting commands across agent platforms, or refactoring existing commands to follow platform conventions.
Agent Command Authoring
Create commands for Claude Code, OpenCode, Pi, and Codex that are thin wrappers around reusable agent capabilities.
When to Use This Skill
Use this skill when:
- Creating a new custom command
- Refactoring an existing command to delegate correctly
- Porting commands between Claude Code, OpenCode, Pi, and Codex
- Ensuring consistency between command implementations across agent harnesses
Platform Model
Different harnesses support different delegation mechanisms:
| Platform | Command location | Preferred delegation |
|---|---|---|
| Claude Code | .claude/commands/<name>.md | Task(subagent-name) for context-independent tasks; Skill(skill-name) for session-context-dependent tasks |
| OpenCode | .config/opencode/command/<name>.md | agent: subagent-name for context-independent tasks; omit agent: and call the skill directly for session-context-dependent tasks |
| Pi | .pi/prompts/<name>.md project-local, or ~/.pi/agent/prompts/<name>.md global | Prompt template that invokes the skill directly |
| Codex | $CODEX_HOME/prompts/<name>.md, usually ~/.codex/prompts/<name>.md | Custom prompt that invokes the skill directly |
Pi does not have subagents by default, and Codex custom prompts do not
declare a subagent target. Their templates should not reference Task(...),
agent:, or "use the <name> subagent". Convert those to direct skill
invocation.
Codex custom prompts are deprecated upstream. Keep reusable behavior in
skills. Add a custom prompt only when the user or repository wants an explicit
/prompts:<name> command.
The Delegation Pattern
For Claude Code and OpenCode, commands should usually be thin wrappers that delegate to subagents, which in turn delegate to skills:
command → subagent → skill
For Pi and Codex, commands are prompt templates and should invoke skills directly:
prompt template → skill
Claude Code Command Structure
Claude Code command (.claude/commands/<name>.md):
---
description: Brief description of what the command does
allowed-tools: Task(subagent-name)
---
Use the `<subagent-name>` subagent to accomplish this task.
Frontmatter Fields
| Field | Required | Description |
|---|---|---|
description | Yes | 1-2 sentence description of what the command does |
allowed-tools | Yes for subagent commands | Task(subagent-name) to invoke the subagent |
argument-hint | No | Hint for command arguments (e.g., [feature_name [subtask_number]]) |
allowed-tools Format
For commands that delegate to subagents:
Task(subagent-name)- Invoke a subagent
For commands that must run in the current session context:
Skill(skill-name)- Invoke the skill directly
Example:
allowed-tools: Task(git-committer)
OpenCode Command Structure
OpenCode command (.config/opencode/command/<name>.md):
---
description: Brief description of what the command does
agent: <subagent-name>
---
Use the `<subagent-name>` subagent to accomplish this task.
Frontmatter Fields
| Field | Required | Description |
|---|---|---|
description | Yes | 1-2 sentence description of what the command does |
agent | Yes for subagent commands | Name of the subagent to invoke |
argument-hint | No | Hint for command arguments |
For session-context-dependent commands, omit agent: so the command runs in
the primary agent's context, and invoke the skill directly in the body.
Pi and Codex Prompt Template Structure
Pi prompt template (.pi/prompts/<name>.md or ~/.pi/agent/prompts/<name>.md):
Codex custom prompt ($CODEX_HOME/prompts/<name>.md, usually
~/.codex/prompts/<name>.md):
---
description: Brief description of what the command does
argument-hint: "[optional-args]"
---
Use the `<skill-name>` skill to accomplish this task.
Arguments: $ARGUMENTS
Frontmatter Fields
| Field | Required | Description |
|---|---|---|
description | No, but recommended | Description shown in / autocomplete |
argument-hint | No | Hint shown before the description in autocomplete |
Pi Rules
- Filename becomes the slash command:
.pi/prompts/review.mdcreates/review. - Use
$1,$2,$@, or$ARGUMENTSfor arguments. - Do not include Claude/OpenCode-only fields:
allowed-tools,agent,model,mode,permission, ortools. - Do not reference subagents unless a Pi extension/package explicitly provides them. Prefer direct skill invocation.
- After adding or changing templates in a running Pi session, run
/reload.
Codex Rules
- Filename becomes the slash command:
~/.codex/prompts/review.mdcreates/prompts:review. - Use
$ARGUMENTSto pass the user's trailing command text. - Do not include Claude/OpenCode-only fields such as
allowed-toolsoragent. - In a dotfiles repository, edit its source path, such as
.codex/prompts/<name>.md, then verify that the deployment exposes it under$CODEX_HOME/prompts/. Do not assume that committing the source deploys it. - When the Pi and Codex bodies are identical in a shared config repository, make the Codex source a relative symlink to the Pi template. Keep separate files only when platform syntax requires different content.
Common Subagent → Skill Mapping for Pi and Codex
When porting existing Claude/OpenCode commands to Pi or Codex, map common subagents to skills:
| Subagent | Pi/Codex skill |
|---|---|
git-committer | git-commit |
git-stager | git-staging |
code-linter | code-linting |
test-runner | test-running |
pr-describer | describing-prs |
prp-generator | prp-generation |
task-generator | task-generation |
Naming Conventions
Command names should use the imperative form of verbs (telling the agent what to do):
- ✅
commit,stage,lint,test,review,reflect - ❌
committing,git-committer,do-linting
The imperative form gives commands their characteristic feel:
- "commit" = "perform a commit"
- "stage" = "stage changes"
- "test" = "run tests"
Command Body
The command body should be 5-20 lines maximum and contain only delegation and argument-passing instructions.
Claude/OpenCode subagent command:
Use the `<subagent-name>` subagent to accomplish this task.
Pi/Codex prompt template or direct-skill command:
Use the `<skill-name>` skill to accomplish this task.
Arguments: $ARGUMENTS
Do NOT include:
- Full implementation steps
- Duplicated content between command wrappers
- More than ~20 lines of content
- Platform-specific frontmatter in the wrong platform's command file
Examples
Minimal Command (Claude Code)
---
description: Create well-formatted commits using conventional commits style
allowed-tools: Task(git-committer)
---
Use the `git-committer` subagent to create a well-formatted commit.
Minimal Command (OpenCode)
---
description: Create well-formatted commits using conventional commits style
agent: git-committer
---
Use the `git-committer` subagent to create a well-formatted commit.
Minimal Prompt Template (Pi or Codex)
---
description: Create well-formatted commits using conventional commits style
---
Use the `git-commit` skill to create a well-formatted commit.
Command with Arguments (Claude Code)
---
description: Generate a PRP
argument-hint: [feature_name]
allowed-tools: Task(prp-generator)
---
Use the `prp-generator` subagent to create a Product Requirements Prompt.
Prompt Template with Arguments (Pi or Codex)
---
description: Generate a PRP
argument-hint: "[feature_name]"
---
Use the `prp-generation` skill to create a Product Requirements Prompt.
Feature: $ARGUMENTS
Why This Pattern?
- Single source of truth: Skills contain all implementation content
- Easier maintenance: Changes to skills automatically propagate
- Platform consistency: Commands are thin wrappers with platform-specific frontmatter
- Token efficiency: Skills load progressively via progressive disclosure
- No duplication: Implementation lives in one place (the skill)
- Isolation where available: Claude/OpenCode subagents run context-independent tasks in their own context
- Pi/Codex compatibility: Prompt templates preserve slash-command ergonomics without assuming subagents
Anti-Pattern to Avoid
BAD - Command with full implementation:
---
description: Stage changes
allowed-tools: Bash(git add:*)
---
# Staging Changes
Stage relevant changes via `git add`...
1. Run `git status` to check for already staged changes
2. Verify no staged changes exist...
3. Run `git status` again...
4. Carefully review which files are relevant...
5. Stage only the relevant files...
6. Run `git status` again...
BAD for Pi/Codex - Prompt template that references a subagent:
---
description: Stage changes via git add
---
Use the `git-stager` subagent to stage relevant changes.
GOOD for Pi/Codex - Prompt template that invokes the skill directly:
---
description: Stage changes via git add
---
Use the `git-staging` skill to stage relevant changes.
BAD for Claude/OpenCode - Command that delegates directly to skill for a context-independent task when a subagent exists:
---
description: Stage changes via git add
allowed-tools: Skill(git-staging)
---
Use the `git-staging` skill to stage relevant changes.
GOOD for Claude/OpenCode - Command that delegates to subagent for a context-independent task:
---
description: Stage changes via git add
allowed-tools: Task(git-stager)
---
Use the `git-stager` subagent to stage relevant changes.
EXCEPTION - Commands that are inherently session-context-dependent (e.g. "review what I just wrote", "remove duplication I just introduced") should skip the subagent and invoke the skill directly. Subagents start with a fresh context and will not know what was recently worked on unless the parent agent tells them — which defeats the purpose of the command.
---
description: Remove code duplication you just introduced
allowed-tools: Skill(code-refactoring-dry)
---
Use the `code-refactoring-dry` skill to remove duplication in the files you
have worked on in this session.
In OpenCode, omit the agent: field entirely for the same effect. In Pi and
Codex, all prompt templates should use this direct skill-invocation style.
Workflow
- Check for existing skill: Identify the skill the command should use.
- For Claude/OpenCode context-independent commands: Check for an existing
subagent that delegates to that skill:
- Claude Code:
.claude/agents/<name>.md - OpenCode:
.config/opencode/agents/<name>.md
- Claude Code:
- If no subagent exists for Claude/OpenCode: Ask the user if they want one created.
- If yes, use the
subagent-authoringskill to create it first. - If no, create only the Pi and Codex templates or stop and explain the limitation.
- If yes, use the
- Create/refactor Claude Code command with
allowed-tools: Task(subagent-name). - Create/refactor OpenCode command with
agent: subagent-name. - Create/refactor Pi prompt template with direct skill invocation in
.pi/prompts/<name>.md. - Create/refactor the Codex custom prompt with direct skill invocation in
$CODEX_HOME/prompts/<name>.md, or in the corresponding deployment source path when working in a dotfiles repository. - Verify the chains:
- Claude/OpenCode: command → subagent → skill
- Pi/Codex: prompt template → skill
- If source files require a separate deployment step, verify the deployed command exists. Run the deployment only when the user or repository policy authorizes it.
Missing Subagent Handling
Before creating a Claude/OpenCode subagent command, always verify the target subagent exists:
# Check Claude Code subagent
ls ~/.claude/agents/<subagent-name>.md
# Check OpenCode subagent
ls ~/.config/opencode/agents/<subagent-name>.md
If either file is missing, ask the user:
"The subagent
<subagent-name>doesn't exist yet. Would you like me to create it using thesubagent-authoringskill before proceeding with the Claude/OpenCode command?"
Do NOT create Claude/OpenCode commands that reference non-existent subagents. This requirement does not apply to Pi or Codex prompt templates, which should reference skills directly.
Verification
After creating or refactoring commands:
# YAML/frontmatter sanity check for generated markdown files
python3 - <<'PY'
from pathlib import Path
import yaml
for root in [
'.claude/commands',
'.config/opencode/command',
'.pi/prompts',
'.pi/agent/prompts',
'.codex/prompts',
]:
for path in Path(root).glob('*.md'):
text = path.read_text()
if text.startswith('---\n'):
yaml.safe_load(text.split('---', 2)[1])
print('command frontmatter ok')
PY
For Pi and Codex, also check that templates do not contain Claude/OpenCode-only fields:
rg -n 'allowed-tools|^agent:|Task\(|`ask_user`|`ToolSearch`|!`' \
.pi/prompts .pi/agent/prompts .codex/prompts 2>/dev/null || true
Run /reload in active Pi sessions after changing Pi prompt templates.
Start a new Codex session if it does not discover a newly deployed prompt.
Related Skills
subagent-authoring- For creating Claude/OpenCode subagent definitions that delegate to skillsskill-authoring- For creating skills themselves
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |