plugin-slash-command

# Navigator Slash Command Generator

Generate new slash commands for the Navigator plugin following established conventions and patterns.

## When to Invoke

Auto-invoke when user says:
- "Add a slash command for..."
- "Create a new /nav:[name] command"
- "Generate slash command..."
- "Add /nav:[feature] command"
- "New Navigator command for..."

## What This Does

1. Asks for command details (name, purpose, complexity)
2. Analyzes existing commands for pattern matching
3. Generates command markdown file with proper structure
4. Validates YAML frontmatter and formatting
5. Shows usage example

## Execution Steps

### Step 1: Gather Command Requirements

Ask user:
- **Command name** (kebab-case, without /nav: prefix)
  - Example: "marker", "compact", "update-doc"
- **Command purpose** (one sentence description)
  - Example: "Create context markers to save conversation state"
- **Command complexity**:
  - Simple: Single action, minimal steps (e.g., marker)
  - Medium: Multiple steps, some logic (e.g., compact)
  - Complex: Multi-phase execution, integrations (e.g., init, start)
- **User-facing or internal**?
  - User-facing: Part of standard Navigator workflow
  - Internal: For plugin development/maintenance

### Step 2: Analyze Similar Commands

Use Task agent to find similar commands:
```
"Find existing Navigator commands similar to [purpose]:
 - Commands in commands/*.md
 - Similar complexity level
 - Common structure patterns
 - Return 2-3 best examples"
```

**What to extract from examples**:
- Section structure (What This Does, When to Use, etc.)
- Tone and style (conversational, 2nd person)
- Emoji usage patterns
- Example format
- Troubleshooting patterns

### Step 3: Design Command Structure

Based on complexity level:

**Simple commands**:
```
- YAML frontmatter (description)
- Title
- What This Does (2-3 sentences)
- Usage (basic syntax + examples)
- When to Use (2-3 scenarios)
- Expected Output
- Troubleshooting (2-3 common issues)
- Closing statement
```