Command Creator Assistant
This meta-command helps create other commands by:
- Understanding the command's purpose
- Determining its category and pattern
- Choosing command location (project vs user)
- Generating the command file
- Creating supporting resources
- Updating documentation
<command_categories>
-
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
-
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
-
Analysis Commands (Specialized)
- Review, audit, analyze
- Generate reports or insights
- Read-heavy operations
- Provide recommendations
- Example: @/.claude/commands/review.md
-
Workflow Commands (Specialized)
- Orchestrate multiple steps
- Coordinate between areas
- Manage dependencies
- Track progress
- Example: @/.claude/commands/04_feature-planning.md
-
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
-
description (REQUIRED):
- One-line summary of the command's purpose
- Clear, concise, action-oriented
- Example: "Guided feature development with codebase understanding and architecture focus"
-
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:
echo 'Fix issue #$ARGUMENTS following our coding standards' > .claude/commands/fix-issue.md
> /fix-issue 123 high-priority
Individual Arguments with $1, $2, etc.
Access specific arguments individually using positional parameters:
echo 'Review PR #$1 with priority $2 and assign to $3' > .claude/commands/review-pr.md
> /review-pr 456 high 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 string |
Inherits from conversation |
disable-model-invocation |
Prevent Skill tool from calling this command |
false |
Example with all frontmatter options:
---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
argument-hint: [message]
description: Create a git commit
model: claude-3-5-haiku-20241022
---
Create a git commit with message: $ARGUMENTS
</command_features>
<pattern_research>
Before Creating: Study Similar Commands
-
List existing commands in target directory:
ls -la /.claude/commands/
ls -la ~/.claude/commands/
-
Read similar commands for patterns:
- Check the frontmatter (description and argument-hint)
- How do they structure sections?
- What MCP tools do they use?
- How do they handle arguments?
- What documentation do they reference?
-
Common patterns to look for:
# MCP tool usage for tasks
Use tool: mcp__scopecraft-cmd__task_create
Use tool: mcp__scopecraft-cmd__task_update
Use tool: mcp__scopecraft-cmd__task_list
# NOT CLI commands
❌ Run: scopecraft task list
✅ Use tool: mcp__scopecraft-cmd__task_list
-
Standard references to include:
- @/docs/organizational-structure-guide.md
- @/docs/command-resources/{relevant-templates}
- @/docs/claude-commands-guide.md
</pattern_research>
<interview_process>
Phase 1: Understanding Purpose
"Let's create a new command. First, let me check what similar commands exist..."
Use Glob to find existing commands in the target category
"Based on existing patterns, please describe:"
- What problem does this command solve?
- Who will use it and when?
- What's the expected output?
- Is it interactive or batch?
Phase 2: Category Classification
Based on responses and existing examples:
- Is this like existing planning commands? (Check: brainstorm-feature, feature-proposal)
- Is this like implementation commands? (Check: implement.md)
- Does it need mode variations?
- Should it follow analysis patterns? (Check: review.md)
Phase 3: Pattern Selection
Study similar commands first:
# Read a similar command
@{similar-command-path}
# Note patterns:
- Task description style
- Argument handling
- MCP tool usage
- Documentation references
- Human review sections
Phase 4: Command Location
🎯 Critical Decision: Where should this command live?
Project Command (/.claude/commands/)
- Specific to this project's workflow
- Uses project conventions
- References project documentation
- Integrates with project MCP tools
User Command (~/.claude/commands/)
- General-purpose utility
- Reusable across projects
- Personal productivity tool
- Not project-specific
Ask: "Should this be:
- A project command (specific to this codebase)
- A user command (available in all projects)?"
Phase 5: Resource Planning
Check existing resources:
ls -la /docs/command-resources/planning-templates/
ls -la /docs/command-resources/implement-modes/
ls -la /docs/
</interview_process>
<generation_patterns>
Critical: Copy Patterns from Similar Commands
Before generating, read similar commands and note:
-
Frontmatter (MUST BE FIRST):
---
description: Clear one-line description of command purpose
argument-hint: What arguments does it accept
---
- No blank lines before opening
---
- One blank line after closing
---
description is REQUIREDargument-hint is OPTIONAL
-
MCP Tool Usage:
# From existing commands
Use mcp__scopecraft-cmd__task_create
Use mcp__scopecraft-cmd__feature_get
Use mcp__scopecraft-cmd__phase_list
-
Standard References:
<context>
Key Reference: @/docs/organizational-structure-guide.md
Template: @/docs/command-resources/planning-templates/{template}.md
Guide: @/docs/claude-commands-guide.md
</context>
-
Task Update Patterns:
<task_updates>
After implementation:
1. Update task status to appropriate state
2. Add implementation log entries
3. Mark checklist items as complete
4. Document any decisions made
</task_updates>
-
Human Review Sections:
<human_review_needed>
Flag decisions needing verification:
- [ ] Assumptions about workflows
