Interactive slash command generator that creates project-specific commands through guided conversation. Use when (1) User wants to create a new slash command, (2) User says 'create command', 'new command', 'make a slash command', or similar, (3) User needs help building automation workflows via commands. This skill ensures full understanding of user intent before generating production-ready command files.
Generate project-specific slash commands through interactive discovery. Ensure complete understanding of user intent before creating the command file.
Before creating ANY command, gather this information through conversation:
1. Command Purpose Ask: "What should this command do? Describe the specific task or workflow."
2. Command Name
Ask: "What name would you like for this command?" (kebab-case, e.g., review-pr, deploy-staging)
3. Tool Requirements Determine what Claude needs access to:
Read, Glob, GrepBash(git:*), ReadRead, Edit, WriteBash, Read, Write, EditAsk: "Should this command be able to modify files, or just read/analyze?"
4. Arguments Ask: "What inputs does this command need from the user?"
$ARGUMENTS$1, $2, $3 with [arg1] [arg2]5. Output Expectations Ask: "What should the output look like? (Report format, file creation, console output, etc.)"
Before generating, summarize back to user:
Command Summary:
- Name: /command-name
- Purpose: [clear description]
- Tools: [list of allowed tools]
- Arguments: [what user provides]
- Output: [expected result]
Does this match your intent? [Yes/Adjust]
Generate the command file at .claude/commands/{command-name}.md
---