Add add-phpengine-plugin skill and update .gitignore to track it

skills/.gitignore

@@ -5,6 +5,7 @@
 !/.gitignore
 
 # Eccezioni: traccia solo le 15 skill selezionate
+!/add-phpengine-plugin/
 !/ascii-preview-generator/
 !/code-simplifier/
 !/codebase-analysis/

skills/add-phpengine-plugin/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: add-phpengine-plugin
+description: Create or modify a discoverable PHP plugin for the phpengine backend. Use when the user asks to create a plugin, add a menu entry, or add a permission in the phpengine project. Fetches the official recipe and follows it step by step.
+---
+
+# Add a phpengine Plugin
+
+## Step 1 — Fetch the official recipe (mandatory, every time)
+
+Fetch this URL before doing anything else, it is the single source of truth:
+
+```
+https://gogs.gvoci.com/softword/phpengine/raw/main/specs/rules/add-plugin.md
+```
+
+Use whatever fetch tool is available (web fetch, curl, ...). Never rely on
+memory or prior knowledge of its content: it may have changed.
+
+If the fetch fails, stop and ask the user to paste the file. Do not proceed
+without it.
+
+## Step 2 — Follow the recipe exactly
+
+Execute the steps in the fetched recipe in order, without skipping or
+reinterpreting them.
+
+## Basecode root (path override)
+
+All repository-relative paths in the recipe resolve from this basecode root:
+
+```
+phengine/
+```
+
+Example: the recipe's `src/Modules/` means `phengine/src/Modules/`, so a plugin
+named `Example` is created at:
+
+```
+phengine/src/Modules/Example/Example.php
+```
+
+## Docs referenced by the recipe
+
+When the recipe links other specs (e.g. `add-api-endpoint.md`,
+`module-index.md`), resolve them against the same base:
+`https://gogs.gvoci.com/softword/phpengine/raw/main/specs/` and fetch them
+before acting on the related step.

skills/gv-brainstorming/SKILL.md

@@ -183,6 +183,11 @@ Identify only the spec files created for the approved microdevelopment IDs in th
 
 Record the deleted paths in the final result. Do not report `COMPLETED` while any current-work spec remains.
 
+# Test execution
+
+* Tests run only on a direct user instruction, whether from the orchestrator or any delegated role.
+* Every test run is subject to a hard timeout of two minutes; on expiry, abort the run and report the check as FAIL with the timeout noted.
+
 # Scope changes
 
 When new files, behaviors, or decisions become necessary: