Prompt examples

Tell the assistant what to do, what not to do, and when to stop.

Each example names the goal, the information the assistant needs, the actions that are off limits, and the result you expect. Clear instructions help people review the work, but they never replace real WordPress permissions.

Read Only

Bounded content inventory

Inspect a named WordPress scope and return findings without requesting a mutation.

Reusable structure

Required inputs

  • Target post IDs or URLs
  • Fields to inspect
  • Required output format

Prohibited actions

  • Create, edit, publish, delete, install, update, or change settings
  • Expand beyond the named scope
  • Treat an inaccessible field as evidence that it does not exist

Expected output

A source-linked inventory with observed facts, unknowns, and follow-up questions.

Prompt templateReplace every value inside double braces.
You are reviewing a bounded WordPress content scope through a dedicated Agent Control identity.

Scope: {{post IDs or canonical URLs}}
Inspect: {{fields and questions}}
Return as: {{table, JSON, or structured notes}}

Do not create, edit, publish, delete, install, update, or change settings. Do not expand beyond the named scope. Separate observed facts from unknowns and recommendations.

Draft

Draft from an approved brief

Prepare a new draft that a human editor can inspect before publication.

Reusable structure

Required inputs

  • Approved brief
  • Source documents
  • Audience and locale
  • Required metadata

Prohibited actions

  • Publish or schedule the draft
  • Overwrite an existing live page
  • Invent facts, citations, product capabilities, or URLs

Expected output

A draft plus a concise list of unresolved facts and editorial decisions.

Prompt templateReplace every value inside double braces.
Prepare a WordPress draft from the approved material below.

Brief: {{approved brief}}
Sources: {{canonical sources}}
Audience and locale: {{audience and locale}}
Required metadata: {{title, excerpt, taxonomy, or other fields}}

Keep the result in draft state. Do not publish, schedule, or overwrite live content. Do not invent missing facts. Return the draft and a separate list of unresolved questions.

Content Editor

Bounded content update

Change only approved fields on explicitly identified WordPress content.

Reusable structure

Required inputs

  • Target IDs
  • Allowed fields
  • Approved replacement values
  • Validation checklist

Prohibited actions

  • Publish, delete, install, or change settings
  • Modify content outside the target list
  • Rewrite unrelated fields for stylistic consistency

Expected output

A field-by-field change log, skipped items, and validation results.

Prompt templateReplace every value inside double braces.
Apply only the approved content changes below.

Target IDs: {{IDs}}
Allowed fields: {{field allowlist}}
Approved values or transformation: {{changes}}
Validation: {{checks}}

Do not publish, delete, change settings, or modify any field outside the allowlist. If a target or field is ambiguous, skip it and report the ambiguity. Return a field-by-field change log.

Publisher

Publish only after checklist

Make a publication decision for one approved item after every required check passes.

Reusable structure

Required inputs

  • Target draft ID
  • Approval reference
  • Required checks
  • Publication timing

Prohibited actions

  • Publish a different item or expand the scope
  • Ignore a failed or unavailable check
  • Change plugins, users, themes, or site settings

Expected output

The publication result or a stopped state naming every failed or unknown check.

Prompt templateReplace every value inside double braces.
Evaluate the named WordPress draft for publication.

Target draft ID: {{ID}}
Human approval reference: {{reference}}
Required checks: {{checklist}}
Publication timing: {{now or approved schedule}}

Publish only if every required check passes. If any check fails or cannot be observed, stop without publishing and report the exact blocker. Do not touch any other content or site configuration.

Administrator-level Full Power work

Full Power decision preflight

Require an explicit administrative plan and confirmation before exceptional work.

Reusable structure

Required inputs

  • Exact administrative target
  • Reason protected modes do not fit
  • Backup or staging state
  • Rollback plan

Prohibited actions

  • Begin work before explicit human confirmation
  • Hide irreversible effects, credential needs, or blast radius
  • Treat Full Power as a protected mode or default upgrade

Expected output

A preflight only: scope, risks, prerequisites, rollback, and a clear confirmation request.

Prompt templateReplace every value inside double braces.
Prepare a Full Power administrative preflight. Do not execute the requested work yet.

Target: {{exact administrative target}}
Why protected modes do not fit: {{reason}}
Backup or staging state: {{state}}
Rollback plan: {{plan}}

Return the exact scope, expected effects, irreversible effects, prerequisites, rollback path, and remaining unknowns. End by requesting explicit human confirmation before any administrative action.