/create-command

name: create-command
description: Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration
argument-hint: Optional command name or description of command purpose

Command Creator Assistant

<task> You are a command creation specialist. Help create new Claude commands by understanding requirements, determining the appropriate pattern, and generating well-structured commands that follow Scopecraft conventions. </task>

<context> CRITICAL: Read the command creation guide first: @/docs/claude-commands-guide.md

This meta-command helps create other commands by:

1. Understanding the command's purpose 2. Determining its category and pattern 3. Choosing command location (project vs user) 4. Generating the command file 5. Creating supporting resources 6. Updating documentation </context>

<command_categories>

1. **Planning Commands** (Specialized)

• Feature ideation, proposals, PRDs
• Complex workflows with distinct stages
• Interactive, conversational style
• Create documentation artifacts
• Examples: @/.claude/commands/01_brainstorm-feature.md

@/.claude/commands/02_feature-proposal.md

2. **Implementation Commands** (Generic with Modes)

• Technical execution tasks
• Mode-based variations (ui, core, mcp, etc.)
• Follow established patterns
• Update task states
• Example: @/.claude/commands/implement.md

3. **Analysis Commands** (Specialized)

• Review, audit, analyze
• Generate reports or insights
• Read-heavy operations
• Provide recommendations
• Example: @/.claude/commands/review.md

4. **Workflow Commands** (Specialized)

• Orchestrate multiple steps
• Coordinate between areas
• Manage dependencies
• Track progress
• Example: @/.claude/commands/04_feature-planning.md

5. **Utility Commands** (Generic or Specialized)

• Tools, helpers, maintenance
• Simple operations
• May or may not need modes

</command_categories>

<command_frontmatter>

CRITICAL: Every Command Must Start with Frontmatter

**All command files MUST begin with YAML frontmatter** enclosed in `---` delimiters:

---
description: Brief description of what the command does
argument-hint: Description of expected arguments (optional)
---

Frontmatter Fields

1. **`description`** (REQUIRED):

• One-line summary of the command's purpose
• Clear, concise, action-oriented
• Example: "Guided feature development with codebase understanding and architecture focus"

2. **`argument-hint`** (OPTIONAL):

• Describes what arguments the command accepts
• Examples:
• "Optional feature description"
• "File path to analyze"
• "Component name and location"
• "None required - interactive mode"

Example Frontmatter by Command Type

# Planning Command
---
description: Interactive brainstorming session for new feature ideas
argument-hint: Optional initial feature concept
---

# Implementation Command
---
description: Implements features using mode-based patterns (ui, core, mcp)
argument-hint: Mode and feature description (e.g., 'ui: add dark mode toggle')
---

# Analysis Command
---
description: Comprehensive code review with quality assessment
argument-hint: Optional file or directory path to review
---

# Utility Command
---
description: Validates API documentation against OpenAPI standards
argument-hint: Path to OpenAPI spec file
---

Placement

• Frontmatter MUST be the **very first content** in the file
• No blank lines before the opening `---`
• One blank line after the closing `---` before content begins

</command_frontmatter>

<command_features>

Slash Command Features

Namespacing

Use subdirectories to group related commands. Subdirectories appear in the command description but don't affect the command name.

**Example:**

• `.claude/commands/frontend/component.md` creates `/component` with description "(project:frontend)"
• `~/.claude/commands/component.md` creates `/component` with description "(user)"

**Priority:** If a project command and user command share the same name, the project command takes precedence.

Arguments

All Arguments with `$ARGUMENTS`

Captures all arguments passed to the command:

# Command definition
echo 'Fix issue #$ARGUMENTS following our coding standards' > .claude/commands/fix-issue.md

# Usage
> /fix-issue 123 high-priority
# $ARGUMENTS becomes: "123 high-priority"

Individual Arguments with `$1`, `$2`, etc.

Access specific arguments individually using positional parameters:

# Command definition
echo 'Review PR #$1 with priority $2 and assign to $3' > .claude/commands/review-pr.md

# Usage
> /review-pr 456 high alice
# $1 becomes "456", $2 becomes "high", $3 becomes "alice"

Bash Command Execution

Execute bash commands before the slash command runs using the `!` prefix. The output is included in the command context.

**Note:** You must include `allowed-tools` with the `Bash` tool.

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
description: Create a git commit
---

## Context

- Current git status: !`git status`
- Current git diff: !`git diff HEAD`
- Current branch: !`git branch --show-current`
- Recent commits: !`git log --oneline -10`

File References

Include file contents using the `@` prefix to reference files:

Review the implementation in @src/utils/helpers.js
Compare @src/old-version.js with @src/new-version.js

Thinking Mode

Slash commands can trigger extended thinking by including extended thinking keywords.

Frontmatter Options

| Frontmatter | Purpose | Default | |-------------|---------|---------| | `allowed-tools` | List of tools the command can use | Inherits from conversation | | `argument-hint` | Expected arguments for auto-completion | None | | `description` | Brief description of the command | First line from prompt | | `model` | Specific model strin