Merge branch 'main' into skill-pdftk-server

Author: jhauga

.github/copilot-instructions.md

@@ -55,18 +55,17 @@ The following instructions are only to be applied when performing a code review.
 - [ ] Any bundled assets (scripts, templates, data files) are referenced in the SKILL.md instructions.
 - [ ] Bundled assets are reasonably sized (under 5MB per file).
 
-## Collection file guide
+## Plugin guide
 
-**Only apply to files that end in `.collection.yml`**
+**Only apply to directories in the `plugins/` directory**
 
-- [ ] The collection has a `name` field.
-- [ ] The collection has a `description` field.
+- [ ] The plugin directory contains a `.github/plugin/plugin.json` file.
+- [ ] The plugin directory contains a `README.md` file.
+- [ ] The plugin.json has a `name` field matching the directory name.
+- [ ] The plugin.json has a `description` field.
 - [ ] The `description` field is not empty.
-- [ ] The collection has a `tags` field.
-- [ ] The file name is lower case, with words separated by hyphens.
-- [ ] Each item in the collection has a `path` field.
-- [ ] Each item in the collection has a `kind` field.
-- [ ] The `kind` field value is one of: `prompt`, `instruction`, `agent`, or `skill`.
-- [ ] The collection does not include duplicate items.
-- [ ] The collection does not reference non-existent files.
-- [ ] Each item can have an optional `usage` field describing when to use the item.
+- [ ] The directory name is lower case, with words separated by hyphens.
+- [ ] If `tags` is present, it is an array of lowercase hyphenated strings.
+- [ ] If `items` is present, each item has `path` and `kind` fields.
+- [ ] The `kind` field value is one of: `prompt`, `agent`, `instruction`, `skill`, or `hook`.
+- [ ] The plugin does not reference non-existent files.

.github/plugin/marketplace.json

@@ -13,7 +13,7 @@
     {
       "name": "awesome-copilot",
       "source": "./plugins/awesome-copilot",
-      "description": "Meta prompts that help you discover and generate curated GitHub Copilot agents, collections, instructions, prompts, and skills.",
+      "description": "Meta prompts that help you discover and generate curated GitHub Copilot agents, instructions, prompts, and skills.",
       "version": "1.0.0"
     },
     {
@@ -214,6 +214,12 @@
       "description": "Complete toolkit for building Model Context Protocol servers in Ruby using the official MCP Ruby SDK gem with Rails integration support.",
       "version": "1.0.0"
     },
+    {
+      "name": "rug-agentic-workflow",
+      "source": "./plugins/rug-agentic-workflow",
+      "description": "Three-agent workflow for orchestrated software delivery with an orchestrator plus implementation and QA subagents.",
+      "version": "1.0.0"
+    },
     {
       "name": "rust-mcp-development",
       "source": "./plugins/rust-mcp-development",

.github/pull_request_template.md

@@ -20,9 +20,9 @@
 - [ ] New instruction file.
 - [ ] New prompt file.
 - [ ] New agent file.
-- [ ] New collection file.
+- [ ] New plugin.
 - [ ] New skill file.
-- [ ] Update to existing instruction, prompt, agent, collection or skill.
+- [ ] Update to existing instruction, prompt, agent, plugin, or skill.
 - [ ] Other (please specify):
 
 ---

.github/workflows/deploy-website.yml

@@ -13,7 +13,7 @@ on:
       - "prompts/**"
       - "instructions/**"
       - "skills/**"
-      - "collections/**"
+      - "plugins/**"
       - "cookbook/**"
       - "eng/generate-website-data.mjs"
       - ".github/workflows/deploy-website.yml"

.github/workflows/validate-readme.yml

@@ -7,7 +7,6 @@ on:
       - "instructions/**"
       - "prompts/**"
       - "agents/**"
-      - "collections/**"
       - "plugins/**"
       - "*.js"
       - "README.md"
@@ -34,8 +33,8 @@ jobs:
       - name: Install dependencies
         run: npm install
 
-      - name: Validate collections
-        run: npm run collection:validate
+      - name: Validate plugins
+        run: npm run plugin:validate
 
       - name: Update README.md
         run: npm start

AGENTS.md

@@ -9,7 +9,7 @@ The Awesome GitHub Copilot repository is a community-driven collection of custom
 - **Instructions** - Coding standards and best practices applied to specific file patterns
 - **Skills** - Self-contained folders with instructions and bundled resources for specialized tasks
 - **Hooks** - Automated workflows triggered by specific events during development
-- **Collections** - Curated collections organized around specific themes and workflows
+- **Plugins** - Installable packages that group related agents, prompts, and skills around specific themes
 
 ## Repository Structure
 
@@ -20,7 +20,7 @@ The Awesome GitHub Copilot repository is a community-driven collection of custom
 ├── instructions/     # Coding standards and guidelines (.instructions.md files)
 ├── skills/           # Agent Skills folders (each with SKILL.md and optional bundled assets)
 ├── hooks/            # Automated workflow hooks (folders with README.md + hooks.json)
-├── collections/      # Curated collections of resources (.md files)
+├── plugins/          # Installable plugin packages (folders with plugin.json)
 ├── docs/             # Documentation for different resource types
 ├── eng/              # Build and automation scripts
 └── scripts/          # Utility scripts
@@ -35,14 +35,14 @@ npm ci
 # Build the project (generates README.md and marketplace.json)
 npm run build
 
+# Validate plugin manifests
+npm run plugin:validate
+
 # Generate marketplace.json only
 npm run plugin:generate-marketplace
 
-# Validate collection manifests
-npm run collection:validate
-
-# Create a new collection
-npm run collection:create -- --id <collection-id> --tags <tags>
+# Create a new plugin
+npm run plugin:create -- --name <plugin-name>
 
 # Validate agent skills
 npm run skill:validate
@@ -134,18 +134,18 @@ When adding a new agent, prompt, instruction, skill, hook, or plugin:
 6. Verify the skill appears in the generated README
 
 **For Plugins:**
-1. Create a new folder in `plugins/` with a descriptive name (lowercase with hyphens)
-2. Create `.github/plugin/plugin.json` with metadata (name, description, version)
-3. Add agents, prompts, instructions, skills, or hooks to the plugin folder
-4. Run `npm run build` to update README.md and marketplace.json
-5. Verify the plugin appears in `.github/plugin/marketplace.json`
-6. Test plugin installation: `copilot plugin install <plugin-name>@awesome-copilot`
+1. Run `npm run plugin:create -- --name <plugin-name>` to scaffold a new plugin
+2. Add agents, prompts, skills, or hooks to the plugin folder
+3. Edit the generated `plugin.json` with your metadata
+4. Run `npm run plugin:validate` to validate the plugin structure
+5. Run `npm run build` to update README.md and marketplace.json
+6. Verify the plugin appears in `.github/plugin/marketplace.json`
 
 ### Testing Instructions
 
 ```bash
 # Run all validation checks
-npm run collection:validate
+npm run plugin:validate
 npm run skill:validate
 
 # Build and verify README generation
@@ -185,7 +185,7 @@ When creating a pull request:
 4. **Build check**: Run `npm run build` before committing to verify README generation
 5. **Line endings**: **Always run `bash scripts/fix-line-endings.sh`** to normalize line endings to LF (Unix-style)
 6. **Description**: Provide a clear description of what your agent/prompt/instruction does
-7. **Testing**: If adding a collection, run `npm run collection:validate` to ensure validity
+7. **Testing**: If adding a plugin, run `npm run plugin:validate` to ensure validity
 
 ### Pre-commit Checklist
 
@@ -239,13 +239,17 @@ For hook folders (hooks/*/):
 - [ ] Follows [GitHub Copilot hooks specification](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/use-hooks)
 - [ ] Optionally includes `tags` array field for categorization
 
-For plugin folders (plugins/*/):
-- [ ] Folder contains a `.github/plugin/plugin.json` file with metadata
-- [ ] plugin.json has `name` field matching folder name (lowercase with hyphens)
-- [ ] plugin.json has non-empty `description` field
-- [ ] plugin.json has `version` field (semantic version, e.g., "1.0.0")
-- [ ] Folder name is lower case with hyphens
-- [ ] Plugin resources (agents, prompts, etc.) follow their respective guidelines
+For plugins (plugins/*/):
+- [ ] Directory contains a `.github/plugin/plugin.json` file
+- [ ] Directory contains a `README.md` file
+- [ ] `plugin.json` has `name` field matching the directory name (lowercase with hyphens)
+- [ ] `plugin.json` has non-empty `description` field
+- [ ] `plugin.json` has `version` field (semantic version, e.g., "1.0.0")
+- [ ] Directory name is lower case with hyphens
+- [ ] If `tags` is present, it is an array of lowercase hyphenated strings
+- [ ] If `items` is present, each item has `path` and `kind` fields
+- [ ] The `kind` field value is one of: `prompt`, `agent`, `instruction`, `skill`, or `hook`
+- [ ] The plugin does not reference non-existent files
 - [ ] Run `npm run build` to verify marketplace.json is updated correctly
 
 ## Contributing

CONTRIBUTING.md

@@ -136,112 +136,49 @@ Skills are self-contained folders in the `skills/` directory that include a `SKI
 3. **Add optional assets**: Keep bundled assets reasonably sized (under 5MB each) and reference them from `SKILL.md`
 4. **Validate and update docs**: Run `npm run skill:validate` and then `npm run build` to update the generated README tables
 
-### Adding Collections
+### Adding Plugins
 
-Collections group related prompts, instructions, agents, and skills around specific themes or workflows, making it easier for users to discover and adopt comprehensive toolkits.
+Plugins group related prompts, agents, and skills around specific themes or workflows, making it easy for users to install comprehensive toolkits via GitHub Copilot CLI.
 
-1. **Create your collection manifest**: Add a new `.collection.yml` file in the `collections/` directory
-2. **Follow the naming convention**: Use descriptive, lowercase filenames with hyphens (e.g., `python-web-development.collection.yml`)
-3. **Reference existing items**: Collections should only reference files that already exist in the repository
-4. **Test your collection**: Verify all referenced files exist and work well together
+1. **Create your plugin**: Run `npm run plugin:create` to scaffold a new plugin
+2. **Follow the naming convention**: Use descriptive, lowercase folder names with hyphens (e.g., `python-web-development`)
+3. **Add your content**: Add agents, commands (prompts), and skills to the plugin folder using symlinks to existing repo files
+4. **Test your plugin**: Run `npm run plugin:validate` to verify your plugin structure
 
-#### Creating a collection
+#### Creating a plugin
 
 ```bash
-# Using the creation script
-node create-collection.js my-collection-id
-
-# Or using VS Code Task: Ctrl+Shift+P > "Tasks: Run Task" > "create-collection"
-```
-
-#### Example collection format
-
-```yaml
-id: my-collection-id
-name: My Collection Name
-description: A brief description of what this collection provides and who should use it.
-tags: [tag1, tag2, tag3] # Optional discovery tags
-items:
-  - path: prompts/my-prompt.prompt.md
-    kind: prompt
-  - path: instructions/my-instructions.instructions.md
-    kind: instruction
-  - path: agents/my-custom.agent.md
-    kind: agent
-    usage: |
-     recommended # or "optional" if not essential to the workflow
-
-     This agent requires the following instructions/prompts/MCPs:
-      - Instruction 1
-      - Prompt 1
-      - MCP 1
-
-     This agent is ideal for...
-      - Use case 1
-      - Use case 2
-    
-      Here is an example of how to use it:
-      ```markdown, task-plan.prompt.md
-      ---
-      mode: task-planner
-      title: Plan microsoft fabric realtime intelligence terraform support
-      ---
-      #file: <file including in chat context>
-      Do an action to achieve goal.
-      ```
-
-      To get the best results, consider...
-      - Tip 1
-      - Tip 2
-    
-display:
-  ordering: alpha # or "manual" to preserve order above
-  show_badge: false # set to true to show collection badge
+npm run plugin:create -- --name my-plugin-id
 ```
 
-For full example of usage checkout edge-ai tasks collection:
-- [edge-ai-tasks.collection.yml](./collections/edge-ai-tasks.collection.yml)
-- [edge-ai-tasks.md](./collections/edge-ai-tasks.md)
-
-#### Collection Guidelines
-
-- **Focus on workflows**: Group items that work together for specific use cases
-- **Reasonable size**: Typically 3-10 items work well
-- **Test combinations**: Ensure the items complement each other effectively
-- **Clear purpose**: The collection should solve a specific problem or workflow
-- **Validate before submitting**: Run `node validate-collections.js` to ensure your manifest is valid
-
-### Working with Plugins
-
-Plugins are installable packages automatically generated from collections. They contain symlinked agents, commands (prompts), and skills from the source collection.
+#### Plugin structure
 
-#### Creating a Plugin from a Collection
-
-When you create a new collection, you can generate a corresponding plugin:
-
-```bash
-# Migrate a collection to a new plugin (first time only)
-npm run plugin:migrate -- --collection <collection-id>
+```
+plugins/my-plugin-id/
+├── .github/plugin/plugin.json  # Plugin metadata
+├── README.md                   # Plugin documentation
+├── commands/                   # Symlinked prompt files
+├── agents/                     # Symlinked agent files
+└── skills/                     # Symlinked skill folders
 ```
 
-#### Updating Plugins After Collection Changes
+#### Plugin Guidelines
 
-If you modify a collection (add/remove items, update metadata), refresh the corresponding plugin:
+- **Use symlinks**: Plugin content should be symlinks to source files in agents/, prompts/, skills/ directories
+- **Valid references**: All items referenced in plugin.json must exist in the repository
+- **Clear purpose**: The plugin should solve a specific problem or workflow
+- **Validate before submitting**: Run `npm run plugin:validate` to ensure your plugin is valid
 
-```bash
-# Refresh a single plugin
-npm run plugin:refresh -- --collection <collection-id>
+### Working with Plugins
 
-# Refresh all existing plugins
-npm run plugin:refresh -- --all
-```
+Plugins are installable packages that contain symlinked agents, commands (prompts), and skills organized around a specific theme or workflow.
 
 #### Plugin Structure
 
 ```plaintext
-plugins/<collection-id>/
-├── .github/plugin/plugin.json  # Plugin metadata (auto-generated)
-├── README.md                   # Plugin documentation (auto-generated)
+plugins/<plugin-name>/
+├── .github/plugin/plugin.json  # Plugin metadata
+├── README.md                   # Plugin documentation
 ├── agents/                     # Symlinks to agent files (.md)
 ├── commands/                   # Symlinks to prompt files (.md)
 └── skills/                     # Symlinks to skill folders
@@ -251,14 +188,13 @@ plugins/<collection-id>/
 
 - **Symlinks, not copies**: Plugin files are symlinks to the source files, avoiding duplication
 - **Instructions excluded**: Instructions are not currently supported in plugins
-- **Auto-generated content**: The `plugin.json` and `README.md` are generated from the collection metadata
-- **Keep plugins in sync**: After modifying a collection, run `plugin:refresh` to update the plugin
+- **Validate before submitting**: Run `npm run plugin:validate` to ensure your plugin is valid
 
 ## Submitting Your Contribution
 
 1. **Fork this repository**
 2. **Create a new branch** for your contribution
-3. **Add your instruction, prompt file, chatmode, or collection** following the guidelines above
+3. **Add your instruction, prompt file, chatmode, or plugin** following the guidelines above
 4. **Run the update script**: `npm start` to update the README with your new file (make sure you run `npm install` first if you haven't already)
    - A GitHub Actions workflow will verify that this step was performed correctly
    - If the README.md would be modified by running the script, the PR check will fail with a comment showing the required changes
@@ -324,7 +260,7 @@ We welcome many kinds of contributions, including the custom categories below:
 | **Prompts** | Reusable or one-off prompts for GitHub Copilot | ⌨️ |
 | **Agents** | Defined GitHub Copilot roles or personalities | 🎭 |
 | **Skills** | Specialized knowledge of a task for GitHub Copilot | 🧰 |
-| **Collections** | Curated bundles of related prompts, agents, or instructions | 🎁 |
+| **Plugins** | Installable packages of related prompts, agents, or skills | 🎁 |
 
 In addition, all standard contribution types supported by [All Contributors](https://allcontributors.org/emoji-key/) are recognized.