diff --git a/.config/dictionary.txt b/.config/dictionary.txt
index a00770bd..7c1b4e71 100644
--- a/.config/dictionary.txt
+++ b/.config/dictionary.txt
@@ -16,6 +16,8 @@ dbservers
 deps
 devel
 dlitz
+doas
+dzdo
 ededed
 eoan
 fbba
@@ -34,16 +36,20 @@ keypair
 kubernetes
 kubevirt
 languageservice
+machinectl
 markdownlint
 netconf
 nocows
 nosetests
 nthash
 parseable
+pbrun
+pfexec
 phpass
 prereleased
 pytest
 rulesdir
+runas
 scrapy
 setuptools
 ssbarnea
diff --git a/README.md b/README.md
index 088b5226..5d55c17c 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,9 @@ any file that passed these schemas should be accepted by Ansible.
 - Inline actions are not allowed, as schema cannot validate them
 - Non builtin modules must be called using `action:` blocks
 - Module arguments are not yet verified but we plan to implement it
+- Out schemas are strict about use of jinja2 templating and require `{{` on
+  arguments declared as **explicit**, which forbid use of `{{` on those marked
+  as **implicit**. See section below for details.
 
 As these schemas are still experimental, creating pull-requests to improve the
 schema is of much greater help. Though you are still welcome to report bugs but
@@ -46,6 +49,47 @@ extension.
 - [playbook subschema url](https://raw.githubusercontent.com/ansible/schemas/main/f/ansible.json#/definitions/playbook)
 - [tasks subschema uri](https://raw.githubusercontent.com/ansible/schemas/main/f/ansible.json#/definitions/tasks)
 
+## Jinja2 implicit vs explicit templating
+
+While Ansible might allow you to combine implicit and explicit templating, our
+schema will not. Our schemas will only allow you to use the recommended form,
+either by forbidding you to use the curly braces on implicit ones or forcing you
+to add them on explicit ones.
+
+Examples:
+
+```yaml
+- name: some task
+  command: echo 123
+  register: result
+  vars:
+    become_method_var: sudo
+  become_method: become_method_var # <-- schema will not allow this
+  # become_method: "{{ become_method_var }}" # <-- that is allowed
+```
+
+### How to find if a field is implicit or explicit?
+
+Run assuming that your keyword is `no_log`, you can run
+`ansible-doc -t keyword no_log`, which will give you the following output:
+
+```yaml
+failed_when:
+  applies_to:
+    - Task
+  description:
+    Conditional expression that overrides the task's normal 'failed' status.
+  priority: 0
+  template: implicit
+  type: list
+```
+
+As you can see the `template` field tells you if is implicit or explicit.
+
+Being more restrictive, schema protects you from common accidents, like writing
+a simple string in an explicit field. That will always evaluate as true instead
+of being evaluated as a jinja template.
+
 ## Activating the schemas
 
 At this moment installing
diff --git a/f/ansible.json b/f/ansible.json
index b91b731c..59e74aa1 100644
--- a/f/ansible.json
+++ b/f/ansible.json
@@ -23,6 +23,29 @@
       "required": ["ansible.builtin.import_playbook"],
       "type": "object"
     },
+    "become_method": {
+      "markdownDescription": "See [become](https://docs.ansible.com/ansible/latest/user_guide/become.html)",
+      "oneOf": [
+        {
+          "enum": [
+            "sudo",
+            "su",
+            "pbrun",
+            "pfexec",
+            "runas",
+            "dzdo",
+            "ksu",
+            "doas",
+            "machinectl"
+          ],
+          "type": "string"
+        },
+        {
+          "$ref": "#/definitions/full-jinja"
+        }
+      ],
+      "title": "Become Method"
+    },
     "block": {
       "properties": {
         "always": {
@@ -56,8 +79,7 @@
           "type": "string"
         },
         "become_method": {
-          "title": "Become Method",
-          "type": "string"
+          "$ref": "#/definitions/become_method"
         },
         "become_user": {
           "title": "Become User",
@@ -240,8 +262,7 @@
           "type": "string"
         },
         "become_method": {
-          "title": "Become Method",
-          "type": "string"
+          "$ref": "#/definitions/become_method"
         },
         "become_user": {
           "title": "Become User",
@@ -493,8 +514,7 @@
           "type": "string"
         },
         "become_method": {
-          "title": "Become Method",
-          "type": "string"
+          "$ref": "#/definitions/become_method"
         },
         "become_user": {
           "title": "Become User",
@@ -655,8 +675,7 @@
           "type": "string"
         },
         "become_method": {
-          "title": "Become Method",
-          "type": "string"
+          "$ref": "#/definitions/become_method"
         },
         "become_user": {
           "title": "Become User",
diff --git a/negative_test/playbooks/tasks/become_method_untemplated.yml b/negative_test/playbooks/tasks/become_method_untemplated.yml
new file mode 100644
index 00000000..bc7217f0
--- /dev/null
+++ b/negative_test/playbooks/tasks/become_method_untemplated.yml
@@ -0,0 +1,4 @@
+- command: echo 123
+  vars:
+    sudo_var: doo
+  become_method: sudo_var # templating requires {{ }}
diff --git a/test/playbooks/tasks/become_method.yml b/test/playbooks/tasks/become_method.yml
new file mode 100644
index 00000000..9d63a768
--- /dev/null
+++ b/test/playbooks/tasks/become_method.yml
@@ -0,0 +1,7 @@
+- command: echo 123
+  become_method: sudo
+
+- command: echo 123
+  vars:
+    sudo_var: doo
+  become_method: "{{ sudo_var }}" # templating is ok