work-on-plugin

Work on Plugin

Orchestrate creating or resuming work on a plugin in this skill-authoring workspace.

When to Activate

• User says "I want to create skills for "
• User says "work on "
• User says "create a new plugin"
• User says "add skills to "

Workflow

Step 1: Identify the Target Plugin

1. Parse the plugin name from the user's request (the $ARGUMENTS or conversation context).
2. List existing plugins:

   ls ./plugins/
   

3. Fuzzy-match the requested name against existing plugin directories.

If a match is found:

• Tell the user: "Looks like there's already <matched-name> in ./plugins/<matched-name>/. Want to add skills there?"
• If YES → proceed to Step 3 with that plugin.
• If NO → proceed to Step 2 to create a new plugin.

If no match:

• Proceed to Step 2.

Step 2: Scaffold a New Plugin

1. Determine the plugin directory name (kebab-case the user's requested name).
2. Create the plugin directory structure:

   plugins/<plugin-name>/
   ├── .claude-plugin/
   │   └── plugin.json
   ├── commands/
   ├── agents/
   ├── skills/
   ├── hooks/
   └── scripts/
   

3. Write plugins/<plugin-name>/.claude-plugin/plugin.json:

   {
     "name": "<plugin-name>",
     "version": "0.1.0",
     "description": "<ask user or use a sensible default from context>",
     "author": {
       "name": "Jeremy Giberson",
       "email": "[email protected]"
     },
     "license": "MIT",
     "keywords": []
   }
   

4. Write a minimal plugins/<plugin-name>/README.md with the plugin name and description.
5. Update .claude-plugin/marketplace.json — add an entry to the plugins array:

   {
     "name": "<plugin-name>",
     "source": "./plugins/<plugin-name>",
     "description": "<description>",
     "version": "0.1.0"
   }
   

6. Tell the user: "Scaffolded <plugin-name> in ./plugins/<plugin-name>/ and added it to the marketplace."

Step 3: Offer Next Steps

Ask the user:

"Do you want to jump right into writing skills for <plugin-name>?"

• If YES → Invoke the superpowers:writing-skills skill, providing context that the target plugin is at ./plugins/<plugin-name>/ and skills go in ./plugins/<plugin-name>/skills/.
• If NO → Say "Okay, what would you like to do next?" and wait.

Important Constraints

• Plugin isolation is mandatory. Every plugin in ./plugins/ must be fully self-contained. Skills, scripts, agents, hooks, and commands MUST NOT reference or depend on assets from other plugins.
• Always update the marketplace when creating a new plugin.
• Use relative paths in marketplace.json source fields (e.g., "./plugins/my-plugin").
• kebab-case all plugin directory names.