메뉴
Use when building or improving a Claude Code slash command in a project's own `.claude/commands/`: $ARGUMENTS handling, file/bash injection, agent invocation, multi-agent orchestration, or command naming.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | create-claude-command |
| description | Use when building or improving a Claude Code slash command in a project's own `.claude/commands/`: $ARGUMENTS handling, file/bash injection, agent invocation, multi-agent orchestration, or command naming. |
Within atman-marketplace itself, author a skill with
disable-model-invocation: trueinstead of a new plugin command — see.claude/rules/skill-authoring.md. This skill is for authoring.claude/commands/in any other project.
| Component | Purpose | Example |
|---|---|---|
| Filename | Command name | review.md → /review |
$ARGUMENTS | Full user input | /review auth.js → $ARGUMENTS = "auth.js" |
$1, $2 | Positional args | /compare a.js b.js → $1 = "a.js", $2 = "b.js" |
@file | Include file contents | @CLAUDE.md |
!command | Include bash output | !git status |
| Location | Scope |
|---|---|
.claude/commands/ | Project (version-controlled, team-shared) |
~/.claude/commands/ | Personal (cross-project, not shared) |
Every command is a scaffold — a markdown prompt template the user fills at invocation time:
---
description: Brief description for SlashCommand tool integration
---
# Command Title
[Instructions for what this command does]
User request: $ARGUMENTS
## Steps
1. [First action]
2. [Second action]
## Output Format
[Expected output structure]
The description: frontmatter is required for the SlashCommand tool to reference the command. Always include ## Output Format — without it the agent decides its own output shape, which varies run to run.
| Pattern | Example | Use For |
|---|---|---|
{action} | /review | Simple actions |
{action}-{target} | /security-scan | Specific targets |
{domain}-{action} | /pm-strategy | Domain-prefixed |
{tool}-{action} | /git-commit | Tool-specific |
| Command | Agent | Skill | |
|---|---|---|---|
| Trigger | User types /command | Claude decides | Claude loads |
| Purpose | Quick shortcuts | Complex work | Knowledge |
| Statefulness | Stateless | Maintains context | Reference only |
Flow: User → Command → Agent → Skill
For full $ARGUMENTS examples, command patterns (agent invocation, multi-agent orchestration, validation checklist), and advanced patterns (conditional logic, flag parsing), see REFERENCE.md.
Cross-check an Epic's user stories, PBIs, and acceptance criteria against the actual implementation in its repo, and propose fixes for mismatches, missing/unfinished descriptions, and unclear wording. Use when the user wants a consistency check between backlog and code, 整合性チェック, or asks whether the backlog still reflects what is really implemented.
Investigate a spike task from an Epic's backlog using the Epic's dedicated repo clone, and save a findings report the team can decide from. Use when the user mentions a spike, スパイク調査, or wants a technical question from the backlog researched against the actual codebase.
Load a PBL Epic's working context — backlog snapshot, repo sync data, and the Epic summary — refreshing stale data first, so the conversation can start from the Epic's current state. Use when the user wants to load/open an Epic, asks "where are we on <Epic>", Epicをロード, or starts a session about a specific Epic's status.
Generate an HTML report of an Epic's currently-implemented spec and its upcoming planned features, reconciled from the backlog snapshot and the repo's actual state. Use when the user wants a "what exists now vs what's coming" summary, 仕様まとめ, or a feature-status overview for stakeholders.
Read or update the product backlog on monday.com. Use when the user asks about backlog items, monday.com boards, tickets, or tasks tracked in monday.com.
Generate a sprint-review HTML document for a PBL Epic — done items with demo pointers, sprint metrics, and an agenda — from the monday.com board and its Drive snapshot. Use when the user wants sprint review material, a demo agenda, or to prepare for a sprint review / スプリントレビュー.