diff --git a/AGENTS.md b/AGENTS.md
index 9905a4f..c28adf8 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -263,4 +263,8 @@ extensions already does the job and only the conversion of the measurements or o
 - [ ] Tests added for new behaviour using a mock controller (no real hardware in CI).
 - [ ] Docstring of each plugin class states: compatible devices, what was tested, PyMoDAQ and OS versions,
       drivers to install.
-- [ ] `README.rst` updated; target PyMoDAQ version stated.
+- [ ] `README.rst` updated; target PyMoDAQ version stated. Keep its section order: a short description, then `Authors`
+      (then `Contributors` if needed), then `Instruments` (`Actuators`, `Viewer0D`...). `pymodaq_plugin_manager` reads the
+      README from `Authors` to `Instruments` (`extract_authors_from_description` in its `validate.py`), so write nothing
+      else before these sections or between them: requirements, installation, hardware notes or differences with
+      another branch come after the `Instruments` list.
diff --git a/README.rst b/README.rst
index b369419..0ac3522 100644
--- a/README.rst
+++ b/README.rst
@@ -23,16 +23,6 @@ Use this template to create a repository on your account and start the developme
 
 This branch targets **PyMoDAQ 5.3.x** (Python 3.10 to 3.13). Use the branch matching your PyMoDAQ version.
 
-Development
-===========
-
-* Install your plugin in editable mode: ``pip install -e .``
-* Check it, without any hardware: ``check_plugin`` (and ``pytest``)
-* If you use an AI coding assistant, point it to ``AGENTS.md``: it describes the patterns to follow for instrument
-  plugins, Dashboard extensions (``CustomExt``, whenever instruments are involved) and standalone apps
-  (``CustomApp``, only if no instruments are needed).
-
-
 Authors
 =======
 
@@ -97,3 +87,13 @@ Installation instructions
 * PyMoDAQ’s version.
 * Operating system’s version.
 * What manufacturer’s drivers should be installed to make this plugin run?
+
+
+Development
+===========
+
+* Install your plugin in editable mode: ``pip install -e .``
+* Check it, without any hardware: ``check_plugin`` (and ``pytest``)
+* If you use an AI coding assistant, point it to ``AGENTS.md``: it describes the patterns to follow for instrument
+  plugins, Dashboard extensions (``CustomExt``, whenever instruments are involved) and standalone apps
+  (``CustomApp``, only if no instruments are needed).