/create

Workflow Creation Assistant

--help Handler

If 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.

Initial Context

User's initial request: $ARGUMENTS

Process

Step 1: Load the workflow-creation skill

Before proceeding, load the workflow-creation skill to access decision criteria and best practices.

Step 2: Requirements Discovery

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):

1. "What task should this workflow automate?"
2. "When would you typically run this workflow?"
3. "What inputs does it need (files, arguments, context)?"
4. "What should the output look like?"
5. "Are there any tools it needs to use (git, npm, bash commands)?"

Follow-up based on answers:

• If mentions multiple related tasks → probe if single workflow or multiple needed
• If mentions external services → probe integration needs
• If mentions state/memory → probe persistence needs
• If mentions team usage → probe standardization needs

Step 3: Scope Decision

Based on gathered requirements, determine if this is a:

WORKFLOW (slash command) - Choose when:

• Single, focused purpose
• No persistent state needed
• One-shot execution
• Project-specific
• No complex validation logic

PLUGIN - Choose when:

• Multiple related commands needed
• Needs hooks, agents, or skills
• External service integration (MCP)
• Reusable across multiple projects
• Needs complex validation/automation

If unclear, ask the user: "Based on what you've described, this could be either:

• A simple workflow (single slash command) - good for [specific reason]
• A full plugin (multiple components) - better if [specific reason]

Which approach fits your needs better?"

Step 4: Route Appropriately

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.

Step 5: Design the Workflow

Create workflow specification:

1. Name: kebab-case, verb-noun pattern (e.g., review-pr, run-tests)
2. Description: Clear, under 60 characters
3. Arguments: What arguments does it accept? ($1, $2, $ARGUMENTS)
4. Allowed Tools: Minimum needed (principle of least privilege)
5. Instructions: What should Claude do when this runs?

Present the design to user for confirmation before creating.

Step 6: Create the Workflow File

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.

Step 7: Validate and Explain

After creating the file, use the workflow-validator agent to validate the workflow.

Then explain to the user:

1. Where the file was created
2. How to invoke it: /[workflow-name] [arguments]
3. What it will do when run
4. Any tips for effective use

Quality Standards

Ensure created workflows follow these standards:

• ✅ Clear, actionable description
• ✅ Appropriate tool restrictions
• ✅ Instructions written FOR Claude (imperative form)
• ✅ Arguments documented with argument-hint
• ✅ File in correct location (.claude/commands/)
• ✅ Naming follows conventions (kebab-case)

Conversation Style

• Be conversational and collaborative
• Ask clarifying questions when needed
• Summarize understanding before creating
• Explain decisions and tradeoffs
• Offer to iterate if workflow doesn't meet needs