Interactive workflow creation - conversationally create Claude Code slash commands
Guides you through creating Claude Code slash commands via conversational discovery and validation.
/plugin marketplace add FrancisVarga/coconut-claude-code-plugins/plugin install coconut-workflow@coconut-claude-code-pluginsoptional initial descriptionIf the user passes --help as an argument, display this help and stop:
/coconut-workflow:create - Interactive Workflow Creation
DESCRIPTION
Conversationally create Claude Code slash commands through guided
requirements discovery. Determines if you need a simple workflow
or a full plugin, then generates the appropriate files.
USAGE
/coconut-workflow:create [initial description]
/coconut-workflow:create --help
ARGUMENTS
[initial description] Optional starting description of what you want
to automate. If omitted, starts with discovery.
EXAMPLES
# Start with discovery questions
/coconut-workflow:create
# Start with an idea
/coconut-workflow:create "automate my PR review process"
# Create a specific workflow
/coconut-workflow:create "run tests and lint before committing"
PROCESS
1. Discovery - Answer questions about what you want to automate
2. Scope Decision - Workflow (single command) vs Plugin (multiple components)
3. Design - Review the proposed command structure
4. Create - Generate the workflow file in .claude/commands/
5. Validate - Verify the workflow works correctly
OUTPUT
Creates: .claude/commands/[name].md
Format: YAML frontmatter + markdown instructions
Guide the user through creating a Claude Code workflow (slash command) through conversational requirements gathering.
User's initial request: $ARGUMENTS
Before proceeding, load the workflow-creation skill to access decision criteria and best practices.
If the user provided an initial description ($ARGUMENTS is not empty), acknowledge it and ask clarifying questions.
If no initial description, start with discovery questions:
Core Questions (ask 2-3 at a time, not all at once):
Follow-up based on answers:
Based on gathered requirements, determine if this is a:
WORKFLOW (slash command) - Choose when:
PLUGIN - Choose when:
If unclear, ask the user: "Based on what you've described, this could be either:
Which approach fits your needs better?"
If WORKFLOW: Continue to Step 5 below.
If PLUGIN:
Inform the user: "This needs a full plugin with [components]. Let me hand off to the plugin creation workflow."
Then invoke: /plugin-dev:create-plugin [brief description based on requirements]
Stop here - the plugin-dev workflow will take over.
Create workflow specification:
review-pr, run-tests)Present the design to user for confirmation before creating.
Create the workflow file at .claude/commands/[name].md:
---
description: [Clear description]
argument-hint: [argument format]
allowed-tools: [tool list]
---
[Instructions FOR Claude - imperative form, not "you should"]
Critical: Write instructions FOR Claude, not TO the user. Use imperative form.
After creating the file, use the workflow-validator agent to validate the workflow.
Then explain to the user:
/[workflow-name] [arguments]Ensure created workflows follow these standards: