# create-command

Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration.

* Purpose - Guide through creating well-structured commands
* Output - Complete command file with frontmatter, sections, and patterns

```bash
/customaize-agent:create-command ["command name or description"]
```

## Arguments

Optional command name or description of the command's purpose (e.g., "validate API documentation", "deploy to staging").

## Usage Examples

```bash
# Create an API validation command
> /customaize-agent:create-command validate API documentation

# Create a deployment command
> /customaize-agent:create-command deploy feature to staging

# Start without a specific idea
> /customaize-agent:create-command
```

## How It Works

1. **Pattern Research**: Examines existing commands in the target category
   * Lists commands in project (`.claude/commands/`) or user (`~/.claude/commands/`) directories
   * Reads similar commands to identify patterns
   * Notes MCP tool usage, documentation references, and structure
2. **Interactive Interview**: Understands requirements through targeted questions
   * What problem does this command solve?
   * Who will use it and when?
   * Is it interactive or batch?
   * What's the expected output?
3. **Category Classification**: Determines the command type
   * Planning (feature ideation, proposals, PRDs)
   * Implementation (technical execution with modes)
   * Analysis (review, audit, reports)
   * Workflow (orchestrate multiple steps)
   * Utility (simple tools and helpers)
4. **Location Decision**: Chooses where the command should live
   * Project command (specific to codebase)
   * User command (available across all projects)
5. **Generation**: Creates the command following established patterns
   * Proper YAML frontmatter (description, argument-hint)
   * Task and context sections
   * MCP tool usage patterns
   * Human review sections
   * Documentation references

## Best Practices

* Research first - Let the assistant examine existing commands before creating new ones
* Be specific about purpose - Clearly describe what problem the command solves
* Choose location carefully - Project commands for codebase-specific workflows, user commands for general utilities
* Include MCP tools - Use MCP tool patterns instead of CLI commands where applicable
* Add human review sections - Flag decisions that need verification


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cek.neolab.finance/plugins/customaize-agent/create-command.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.