💻 Coding
Ansible Playbook Task Notes from Host Inventory (No Invented Secrets)
Write Ansible playbook task notes from a host inventory only. No invented secrets, vault passwords, or hostnames beyond the inventory.
0Reviews
Prompt
Act as an Ansible playbook note-taker who only uses a pasted host inventory. You write task notes the inventory already supports. You do not invent secrets, vault passwords, SSH keys, or hostnames absent from Inputs. This is not a production apply runbook and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Host inventory I lock (hosts, groups, ports, packages noted): [Inventory] - Ansible / collection version I lock: [Version] - Playbook name I may quote (or UNKNOWN): [Playbook] - Become user I may quote (or UNKNOWN): [Become] - Words I must not use: [Banned] - What I must never invent (secrets, vault ids, hostnames, SSH keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Playbook, Become, Lang. Forbidden: invented secrets, vault ids, hostnames, SSH keys. Include Ansible playbook terminology. 2. Host table: one row per Inventory host or group. Missing facts write NOT IN INPUTS. 3. Task stub YAML: only modules and packages named in Inventory and Version. Secrets stay as vault references NOT IN INPUTS when absent. 4. Version lock: print Version. Refuse collections newer than Version if Version is named. 5. Refuse list: inventing ansible-vault password, inventing ~/.ssh/id_rsa contents, inventing host db-prod-99, inventing become password. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented secrets or hostnames. - Honor Version. No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Inventory: hosts web1 as pasted and web2 as pasted in group edge as pasted; package nginx as pasted. db hosts NONE. Vault id NOT IN INPUTS. Version: ansible-core 2.16 as pasted (do not invent 2.18) Playbook: harbor-edge.yml as pasted Become: root as pasted. Become password UNKNOWN. Banned: guaranteed idempotent, vault pass invent, id_rsa paste, db-prod-99 Never: invent secrets, invent vault ids, invent hostnames, invent SSH keys Format: ledger + table + yaml + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: web1; web2; group edge; package nginx. db hosts NONE. Vault id NOT IN INPUTS. Version ansible-core 2.16. Playbook harbor-edge.yml. Become root; password UNKNOWN. Lang English. Forbidden: invented secrets, vault ids, hostnames, SSH keys, guaranteed idempotent, vault pass invent, id_rsa paste, db-prod-99.
2. Host table.
1. web1 as pasted | group edge | packages nginx as pasted
2. web2 as pasted | group edge | packages nginx as pasted
db hosts: NONE so not listed. Ports NOT IN INPUTS.
3. Task stub YAML.
- name: install nginx on edge
hosts: edge
become: true
# become_user password NOT IN INPUTS (UNKNOWN)
tasks:
- name: ensure nginx
ansible.builtin.package:
name: nginx
state: present
# vault_id NOT IN INPUTS; no ansible-vault password invented
4. Version lock. ansible-core 2.16 as pasted. 2.18 features not used.
5. Refuse. Vault pass invent: refused. id_rsa paste: refused. db-prod-99 invent: refused. Guaranteed idempotent: refused. Become password invent: refused.
6. Compliance. Banned hits none. Format ledger+table+yaml+version+refuse+compliance. Gaps: ports, vault id, become password, db decision, handlers.
Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.