Renumber merged steps to sequential order

- create-backend-plugin: 'Steps 2-3' -> Step 2, renumber 4-6 to 3-5
- enable-plugin workflow: 'Steps 1-3' -> Step 1, renumber 4-8 to 2-6
- create-frontend-plugin: clean up 'Steps 2 + 4' reference in notes

Author: schultzp2020

skills/create-backend-plugin/SKILL.md

@@ -37,19 +37,18 @@ Before starting, ensure the following are available:
 ## Workflow Overview
 
 1. **Determine RHDH Version** - Identify target RHDH version for compatibility
-2. **Create Backstage App** - Scaffold Backstage app with matching version
-3. **Create Backend Plugin** - Generate new backend plugin using Backstage CLI
-4. **Implement Plugin Logic** - Write the plugin code using new backend system
-5. **Export and Package** - Build, export, and package using RHDH CLI (see export-and-package skill)
-6. **Configure for RHDH** - Create dynamic-plugins.yaml configuration
+2. **Scaffold App and Plugin** - Create Backstage app and generate backend plugin
+3. **Implement Plugin Logic** - Write the plugin code using new backend system
+4. **Export and Package** - Build, export, and package using RHDH CLI (see export-and-package skill)
+5. **Configure for RHDH** - Create dynamic-plugins.yaml configuration
 
 ## Step 1: Determine RHDH Version
 
 Check the target RHDH version and find the compatible Backstage version. Consult  `../rhdh/references/versions.md` file for the version compatibility matrix and available RHDH versions.
 
 Ask the user which RHDH version they are targeting if not specified.
 
-## Steps 2-3: Create Backstage Application & Backend Plugin
+## Step 2: Scaffold App and Plugin
 
 Use the scaffold script to automate app creation, dependency installation, and plugin generation in one command:
 
@@ -97,7 +96,7 @@ plugins/<plugin-id>-backend/
 └── README.md
 ```
 
-## Step 4: Implement Plugin Logic
+## Step 3: Implement Plugin Logic
 
 Backend plugins must use the **new backend system** for dynamic plugin compatibility. The plugin entry point should export a default using `createBackendPlugin()` or `createBackendModule()`.
 
@@ -151,7 +150,7 @@ cd plugins/<plugin-id>-backend
 yarn build
 ```
 
-## Step 5: Export and Package
+## Step 4: Export and Package
 
 Export the plugin as a dynamic plugin and package it for deployment. For detailed export and packaging options, see the **export-and-package** skill.
 
@@ -175,7 +174,7 @@ podman push quay.io/<namespace>/<plugin-name>:v0.1.0
 
 For advanced options (dependency handling, multi-plugin bundles, tgz/npm packaging), consult the **export-and-package** skill.
 
-## Step 6: Configure for RHDH
+## Step 5: Configure for RHDH
 
 Create the dynamic plugin configuration for RHDH. Add to `dynamic-plugins.yaml`:
 

skills/create-frontend-plugin/SKILL.md

@@ -56,7 +56,7 @@ Ask the user which RHDH version they are targeting if not specified.
 
 ## Step 2: Create Backstage Application
 
-> **Automated:** Steps 2 + 4 (and optionally 3) are automated by the scaffold script.
+> **Automated:** This step plus Step 4 (and optionally Step 3) are automated by the scaffold script.
 > Run it from the directory where the app should be created:
 >
 > ```bash
@@ -110,7 +110,7 @@ const app = createApp({
 
 ## Step 4: Create Frontend Dynamic Plugin
 
-> **Automated:** If you used `scripts/scaffold.py` in Step 2, this step was already completed. Skip to Step 5.
+> **Automated:** If you used the scaffold script in Step 2, this step was already completed. Skip to Step 5.
 
 ### Manual method
 

skills/rhdh-local/workflows/enable-plugin.md

@@ -12,7 +12,7 @@ Read before starting:
 
 > **Note:** This sequence involves multiple API calls to GitHub. If any step fails, check GitHub API rate limits and authentication.
 
-## Steps 1–3: Identify Plugin & Fetch Metadata
+## Step 1: Identify Plugin & Fetch Metadata
 
 Ask the user which plugin to enable. Use the `fetch-plugin-metadata.py` script to list plugins and retrieve all metadata in one step:
 
@@ -81,7 +81,7 @@ Extract: `spec.dynamicArtifact`, `spec.backstage.role`, `spec.appConfigExamples`
 
 ---
 
-## Step 4: Add to `dynamic-plugins.override.yaml`
+## Step 2: Add to `dynamic-plugins.override.yaml`
 
 Edit `rhdh-customizations/configs/dynamic-plugins/dynamic-plugins.override.yaml`.
 
@@ -130,7 +130,7 @@ Backend plugins should be listed before their corresponding frontend plugins.
 
 ---
 
-## Step 5: Add Backend Configuration (if needed)
+## Step 3: Add Backend Configuration (if needed)
 
 If `spec.appConfigExamples` includes configuration outside the `dynamicPlugins` key, add it to:
 `rhdh-customizations/configs/app-config/app-config.local.yaml`
@@ -150,7 +150,7 @@ argocd:
 
 ---
 
-## Step 6: Set Required Environment Variables
+## Step 4: Set Required Environment Variables
 
 If backend config references `${VAR_NAME}` variables, tell the user to add them to `rhdh-customizations/.env` (bare format — no `export`, no quotes):
 
@@ -163,18 +163,18 @@ This file overrides `rhdh-local/default.env`.
 
 ---
 
-## Step 7: Present Summary
+## Step 5: Present Summary
 
 Before applying, show the user:
 
 - Which packages were added to `dynamic-plugins.override.yaml`
 - What app-config was added (if any)
 - What environment variables need to be set in `.env`
-- The commands from Step 8
+- The commands from Step 6
 
 ---
 
-## Step 8: Apply and Restart
+## Step 6: Apply and Restart
 
 ```bash
 rhdh local apply