Update ai ops index files, agents, files

Author: ashleyshaw

.github/agents/agent.md

@@ -33,6 +33,20 @@ This file documents the primary automation agent(s) for this repository, their p
 - **Usage:** Say "Generate a new multi-block plugin" or "Create CPT plugin from scaffold"
 - **Related Prompt:** [generate-plugin.prompt.md](../prompts/generate-plugin.prompt.md)
 
+### WP Block Build Agent
+
+- **Agent Spec:** `.github/agents/wp-block-build.agent.md`
+- **Purpose:** Details the build process for the multi-block plugin agent, covering compilation, asset handling, and packaging.
+- **Usage:** Reference for understanding and troubleshooting the plugin build process.
+
+### Development Assistant Agent
+
+- **Agent Spec:** `.github/agents/development-assistant.agent.md`
+- **Purpose:** Provides context-specific assistance for development tasks, with different modes for various needs.
+- **Usage:** Invoke for help with coding, debugging, and adhering to project standards.
+
+---
+
 ### General Automation Agent
 
 - **Agent Script:** `.github/agents/agent-script.js`

.github/agents/generate-plugin.agent.md

@@ -520,7 +520,7 @@ Requires Plugins: secure-custom-fields
 
 ## Implementation
 
-This agent is implemented in [`scaffold-generator.agent.js`](./scaffold-generator.agent.js).
+This agent is implemented in [`generate-plugin.agent.js`](../../scripts/generate-plugin.agent.js).
 
 **Direct Usage:**
 ```bash

.github/custom-instructions.md

@@ -81,6 +81,56 @@ When creating project tracking files, task lists, or multi-week project plans:
 
 ---
 
+## Instruction File Index
+
+Reference the following instruction files based on your task. For a complete map, see the Master Instructions Index.
+
+### WordPress Coding Standards (WPCS)
+
+| File | Purpose |
+|------|---------|
+| wpcs-php.instructions.md | PHP coding standards, formatting, naming, security, i18n |
+| wpcs-javascript.instructions.md | JavaScript coding standards and patterns |
+| wpcs-php-docs.instructions.md | PHP inline documentation (DocBlocks) |
+| wpcs-js-docs.instructions.md | JavaScript inline documentation (JSDoc) |
+| wpcs-css.instructions.md | CSS/SCSS coding standards |
+| wpcs-html.instructions.md | HTML markup standards and semantics |
+| wpcs-accessibility.instructions.md | Accessibility standards (WCAG 2.2 AA) |
+
+### Block Development
+
+| File | Purpose |
+|------|---------|
+| blocks-development.instructions.md | Comprehensive block development guide |
+| block-json.instructions.md | Block.json schema reference |
+| patterns-and-templates.instructions.md | Pattern development, registration, and template usage |
+| javascript-react-development.instructions.md | React/JS development patterns for blocks |
+
+### Testing & Quality Assurance
+
+| File | Purpose |
+|------|---------|
+| testing-e2e.instructions.md | End-to-end testing with Playwright/TypeScript |
+| security.instructions.md | Block plugin security best practices |
+
+### Plugin Scaffolding & Organization
+
+| File | Purpose |
+|------|---------|
+| generate-plugin.instructions.md | Mustache template scaffolding standards |
+| scaffold-extensions.instructions.md | Extending the scaffold with new features |
+| folder-structure.instructions.md | Project organization and file structure standards |
+
+### Special Topics
+
+| File | Purpose |
+|------|---------|
+| a11y.instructions.md | Advanced accessibility standards for block plugins |
+| i18n.instructions.md | Internationalization guidelines |
+| scf-fields.instructions.md | Custom field development with SCF |
+
+---
+
 # {{name}} Multi-Block Plugin Instructions
 
 You are an expert WordPress multi-block plugin developer working on {{name}}, a modern WordPress multi-block plugin scaffold with custom post types, taxonomies, and SCF field integration.

.github/instructions/_index.instructions.md

@@ -42,7 +42,7 @@ This index maps every instruction file in the repository and when to use it. Use
 - Check links resolve to existing files after renames.
 
 **Last Updated:** 2025-12-10
-**Total Files:** 19 instruction files
+**Total Files:** 22 instruction files
 
 ---
 
@@ -147,7 +147,7 @@ All `wpcs-*` files in the [WordPress Coding Standards](#wordpress-coding-standar
 | [a11y.instructions.md](./a11y.instructions.md) | 27.8KB | Accessibility standards for block plugins (WCAG 2.2 AA) | When developing block controls, editor UX, or block output |
 | [i18n.instructions.md](./i18n.instructions.md) | 550 bytes | Internationalization guidelines | When adding translatable strings |
 | [scf-fields.instructions.md](./scf-fields.instructions.md) | 19.8KB | Custom field development | When creating custom fields functionality |
-| [reporting.instructions.md](./reporting.instructions.md) | 19.0KB | Reporting and documentation standards | When creating reports or documentation |
+| [reporting.instructions.md](./reporting.instructions.md) | 19.0KB | Reporting and analysis documentation standards | When creating reports or documentation |
 
 **Total Special Topics:** 4 files (~67KB)
 
@@ -348,28 +348,28 @@ Found an issue with an instruction file?
 <summary>Click to expand full alphabetical listing</summary>
 
 1. [_index.instructions.md](./_index.instructions.md) — This file
-2. [a11y.instructions.md](./a11y.instructions.md) — Accessibility standards
-3. [block-json.instructions.md](./block-json.instructions.md) — Block.json reference
-4. [blocks-development.instructions.md](./blocks-development.instructions.md) — **NEW** Block development guide
-5. [folder-structure.instructions.md](./folder-structure.instructions.md) — Project organization
-6. [generate-plugin.instructions.md](./generate-plugin.instructions.md) — Plugin generator
-7. [i18n.instructions.md](./i18n.instructions.md) — Internationalization
-8. [javascript-react-development.instructions.md](./javascript-react-development.instructions.md) — **CONSOLIDATED** React/JS patterns
-9. [patterns-and-templates.instructions.md](./patterns-and-templates.instructions.md) — **NEW** Pattern development
-10. [reporting.instructions.md](./reporting.instructions.md) — Reporting standards
-11. [scaffold-extensions.instructions.md](./scaffold-extensions.instructions.md) — **RENAMED** Scaffold extensions
-12. [scf-fields.instructions.md](./scf-fields.instructions.md) — Custom fields
-13. [schema-files.instructions.md](./schema-files.instructions.md) — Schema organization
-14. [security.instructions.md](./security.instructions.md) — Security best practices
-15. [temp-files.instructions.md](./temp-files.instructions.md) — Temporary files
-16. [testing-e2e.instructions.md](./testing-e2e.instructions.md) — **RENAMED** E2E testing
-17. [wpcs-accessibility.instructions.md](./wpcs-accessibility.instructions.md) — WPCS Accessibility
-18. [wpcs-css.instructions.md](./wpcs-css.instructions.md) — WPCS CSS
-19. [wpcs-html.instructions.md](./wpcs-html.instructions.md) — WPCS HTML
-20. [wpcs-javascript.instructions.md](./wpcs-javascript.instructions.md) — WPCS JavaScript
-21. [wpcs-js-docs.instructions.md](./wpcs-js-docs.instructions.md) — WPCS JS Docs
-22. [wpcs-php.instructions.md](./wpcs-php.instructions.md) — WPCS PHP
-23. [wpcs-php-docs.instructions.md](./wpcs-php-docs.instructions.md) — WPCS PHP Docs
+2. [a11y.instructions.md](./a11y.instructions.md)
+3. [block-json.instructions.md](./block-json.instructions.md)
+4. [blocks-development.instructions.md](./blocks-development.instructions.md)
+5. [folder-structure.instructions.md](./folder-structure.instructions.md)
+6. [generate-plugin.instructions.md](./generate-plugin.instructions.md)
+7. [i18n.instructions.md](./i18n.instructions.md)
+8. [javascript-react-development.instructions.md](./javascript-react-development.instructions.md)
+9. [patterns-and-templates.instructions.md](./patterns-and-templates.instructions.md)
+10. [reporting.instructions.md](./reporting.instructions.md)
+11. [scaffold-extensions.instructions.md](./scaffold-extensions.instructions.md)
+12. [scf-fields.instructions.md](./scf-fields.instructions.md)
+13. [schema-files.instructions.md](./schema-files.instructions.md)
+14. [security.instructions.md](./security.instructions.md)
+15. [temp-files.instructions.md](./temp-files.instructions.md)
+16. [testing-e2e.instructions.md](./testing-e2e.instructions.md)
+17. [wpcs-accessibility.instructions.md](./wpcs-accessibility.instructions.md)
+18. [wpcs-css.instructions.md](./wpcs-css.instructions.md)
+19. [wpcs-html.instructions.md](./wpcs-html.instructions.md)
+20. [wpcs-javascript.instructions.md](./wpcs-javascript.instructions.md)
+21. [wpcs-js-docs.instructions.md](./wpcs-js-docs.instructions.md)
+22. [wpcs-php.instructions.md](./wpcs-php.instructions.md)
+23. [wpcs-php-docs.instructions.md](./wpcs-php-docs.instructions.md)
 
 </details>
 

.github/prompts/generate-plugin.prompt.md

@@ -6,35 +6,59 @@ description: Interactive WordPress multi-block plugin generator with CPT, taxono
 
 I'll help you generate a new WordPress multi-block plugin with custom post types, taxonomies, and Secure Custom Fields integration. This is a comprehensive scaffold for complex WordPress applications.
 
-## 🔍 Repository Context Detection
+## 🔍 Step 1: Repository Context Detection
 
 **First, I need to understand your setup:**
 
 Are you running this generator:
 
 1. **In the `lightspeedwp/multi-block-plugin-scaffold` repository?**
-   - If YES → The plugin will be generated in an `output-plugin/` folder (excluded from git)
+   - If YES → The plugin will be generated in `generated-plugins/<slug>/` folder (excluded from git)
    - This folder is for testing and development only
    - You'll manually move the generated plugin to where you need it
+   - Use **Generator Mode** (default)
 
 2. **In a NEW repository (created from the scaffold template)?**
    - If YES → The generator will replace all mustache variables IN-PLACE in your current repository
    - This will transform the scaffold INTO your actual plugin
-   - This action modifies your repository permanently (use `--in-place` mode)
+   - This action modifies your repository permanently
+   - Use **Template Mode** (`--in-place` flag)
 
 **Please indicate which scenario applies to you before we proceed.**
 
-## Quick Start Options
+---
+
+## 📋 Step 2: Configuration File Check
+
+**Do you have a plugin configuration file?**
+
+### ✅ YES - I Have a Config File
+
+If you have a `plugin-config.json` file (or similar), I'll help you validate and use it:
 
-### Option 1: Use Configuration File (Fastest)
+1. **Provide the file path** to your configuration file
+2. **I will validate it** against the schema (`.github/schemas/plugin-config.schema.json`)
+3. **Review validation results:**
+   - ✅ If valid → Ask if you want to override any values → Generate plugin
+   - ❌ If invalid → Show errors → Offer to fix or use wizard
 
-If you already have a configuration file that follows the schema (`.github/schemas/plugin-config.schema.json`), you can bypass the wizard entirely:
+**Would you like to override any configuration values?**
+- If YES → I'll ask which values you want to change
+- If NO → I'll generate using your config file as-is
 
+**Example validation workflow:**
 ```bash
-node scripts/generate-plugin.js --config path/to/your-config.json
+# Step 1: Validate your config
+node scripts/generate-plugin.js --validate plugin-config.json
+
+# Step 2: Generate (if validation passed)
+node scripts/generate-plugin.js --config plugin-config.json
+
+# Step 3: (Template mode only) Add --in-place flag
+node scripts/generate-plugin.js --config plugin-config.json --in-place
 ```
 
-**Example configuration file:**
+**Example configuration file structure:**
 ```json
 {
   "slug": "tour-operator",
@@ -45,6 +69,7 @@ node scripts/generate-plugin.js --config path/to/your-config.json
   "version": "1.0.0",
   "name_singular": "Tour",
   "name_plural": "Tours",
+  "cpt_slug": "tour",
   "cpt_icon": "dashicons-palmtree",
   "cpt_supports": ["title", "editor", "thumbnail", "custom-fields"],
   "cpt_has_archive": true,
@@ -66,17 +91,43 @@ node scripts/generate-plugin.js --config path/to/your-config.json
 }
 ```
 
-See `.github/schemas/plugin-config.example.json` for a complete example.
+**See complete example:** `.github/schemas/examples/plugin-config.example.json`
+
+**See schema reference:** `.github/schemas/plugin-config.schema.json`
+
+---
+
+### ❌ NO - I Don't Have a Config File
+
+No problem! I'll guide you through creating your plugin configuration using one of these wizards:
+
+#### Option A: Simple Wizard (Recommended for Most Users)
+- Asks **only required** questions
+- Uses **smart defaults** for optional values
+- **Faster** and easier to complete
+- Best for standard use cases
 
-### Option 2: Interactive Wizard (Guided)
+#### Option B: Advanced Wizard (Complete Configuration)
+- Asks about **all 100+ mustache variables**
+- Full control over every aspect
+- Takes longer but offers maximum customization
+- Best for complex or highly customized plugins
 
-If you prefer step-by-step guidance, continue with the information gathering process below.
+**Which wizard would you prefer?**
+- Type **"simple"** for Simple Wizard
+- Type **"advanced"** for Advanced Wizard
 
 ---
 
-## Information Gathering Process
+## 🧙 Interactive Wizard: Information Gathering
+
+*(This section applies when using the Simple or Advanced Wizard)*
+
+This scaffold requires detailed planning due to its complexity. I'll gather information in multiple stages to ensure your plugin is properly configured.
 
-This scaffold requires more detailed planning due to its complexity. I'll gather information in multiple stages to ensure your plugin is properly configured.
+**Wizard Types:**
+- **Simple Wizard**: Covers Stages 1-5 with smart defaults
+- **Advanced Wizard**: Covers all stages + additional variables (100+ total)
 
 ---
 
@@ -243,9 +294,21 @@ Which blocks should be created?
 
 ---
 
-## Let's Begin!
+## 🚀 Let's Begin!
+
+**First, answer these two questions:**
+
+1. **Repository Context**: Are you in the scaffold repo or a new repo?
+   - Type **"scaffold"** for Generator Mode (creates `generated-plugins/<slug>/`)
+   - Type **"new"** for Template Mode (modifies current directory with `--in-place`)
+
+2. **Configuration File**: Do you have a plugin-config.json file?
+   - Type **"yes"** and provide the file path
+   - Type **"no"** to use the wizard
+
+---
 
-**Please provide your answers for Stage 1:**
+**If using the wizard, provide your answers for Stage 1:**
 
 1. Plugin Name:
 2. Plugin Slug:
@@ -370,7 +433,6 @@ The plugin will automatically declare SCF as a dependency using the WordPress 6.
 
 ## Related Resources
 
-- [Multi-Block Plugin Scaffold Reference](multi-block-plugin-scaffold.prompt.md)
 - [Plugin Generator Agent](../agents/generate-plugin.agent.md)
-- [Development Assistant](../agents/development-assistant.agent.md)
+- [Plugin Generator Instructions](../instructions/generate-plugin.instructions.md)
 - [SCF Fields Reference](../instructions/scf-fields.instructions.md)