Codex Prompt Deck for the 24 Working Hour WordPress Runbook

Learn / Website development

35 copy-ready prompts

Codex Prompt Deck for the 24 Working Hour WordPress Runbook

By Henok Ahmed · Version 1.0.0 · 28 October 2026

Download runbook + prompt deck (ZIP) Read the full runbook →

For the GitHub change workflow and reusable records, see the Practical Guide to Source Control Using GitHub and its Template Pack.

Prepare first: Read Building a Professional WordPress Website with Codex, Version 1.0.0 for foundations, client preparation, scope and delivery responsibilities. Then follow the full runbook alongside this deck.

By Henok Ahmed · HA-WEB-002 companion · Version 1.0.0 · Published 28 October 2026

Published with author approval. Twenty-four working hours is a planning allowance, not a tested guarantee. Read the full runbook first. Use one step at a time. Prompts do not replace human actions, completion checks, permissions or actual approvals. Use recovery prompts only when checks fail.

Step 1 Open the computer and prepare the workspace

Codex prompt

Help me establish a workspace for a four-page WordPress website.

Inspect only the selected project directory and available capabilities.
Confirm the absolute project root and existing files before writing.
If this is an unrelated or nonempty project, stop and explain the conflict.
Create only these project folders when safe:
docs, content, assets, wordpress, evidence.

Create docs/progress.md with a Step 1 entry and docs/environment.md.
Record what you can actually read/write/run and whether authenticated
WordPress interaction is available. Do not record credentials.
Do not install software, purchase services, change DNS, or modify WordPress.
Explain any manual setup I must complete and how to verify it.
Done when the workspace and capability report exist and I can open them.

Recovery prompt

Step 1 did not pass. Inspect the actual folder/capability error I provide.
Preserve existing work. Identify the smallest authorized setup correction.
Do not work around a denied permission or claim access you have not verified.
Update docs/environment.md with the result and remaining gap.

Step 2 Set the project working agreement

Codex prompt

Act as my website co-developer and explain unfamiliar steps as we work.
I have a computing background but little practical delivery experience.
Read docs/environment.md and docs/progress.md before continuing.

This project delivers Home, About, Services and Contact in WordPress.
Work in small verifiable steps. Preserve unrelated content and URLs.
Use approved facts only. Record assumptions instead of inventing claims.
Use drafts/test environment until explicit owner acceptance and deployment
authorization are recorded in Step 14.
Do not expose fictional business information as a real public service.
Do not add payments, accounts, booking, tracking, or paid dependencies.

When a tool/action is unavailable, say so. Prepare the local work and give
me the exact manual action, expected result and a way to report it back.
After each task report changed files/pages, actual checks, failures,
remaining decisions and the next step. Never mark unperformed checks passed.
Write these project conventions in docs/working-agreement.md.
Do not modify WordPress yet.

Recovery prompt

Return to Step 2's scope. Do not publish or make further website changes.
Explain any actions already performed and their verified state.
Correct the working agreement and progress record to reflect actual access.
Continue only with establishing the project conventions.

Step 3 Complete the brief once

Codex prompt

Create docs/project-brief.md from my supplied information.
Use these fields and ask only for missing essentials:
mode: practice or client
business name and owner
audience and main visitor action
verified facts and approved services
language
test WordPress URL
production URL and operator, if client mode
approved public/test email and phone, with disclosure permission
four page titles and proposed slugs
content/image rights and approval owner
editing approach and maintainer capability
included revisions and acceptance criteria
backup/recovery owner
deployment authority and exclusions.

For practice, use the fictional LumenBridge facts supplied in the runbook.
Do not invent contacts, a deployment domain, credentials, metrics or clients.
Clearly distinguish fictional material from real client material.
Keep missing operational values marked unresolved and do not use them live.
Create docs/decisions.md. Record my choices when I explicitly make them.
Do not modify WordPress yet.

Recovery prompt

Review the brief for unresolved values, unsupported claims and scope growth.
Separate launch blockers from optional improvements.
Use the smallest four-page scope and list the exact decisions I must make.
Do not silently substitute example contact values or domains.

Step 4 Verify WordPress and a recovery route

Codex prompt

Read the brief and environment report. Inspect the authorized test site
read-only, or guide my manual inspection if direct control is unavailable.
Record site URL, environment, theme, editor/builder, relevant plugins,
existing pages/slugs, publication states and homepage assignment.
Create docs/wordpress-inventory.md and docs/recovery.md.

Identify the backup reference, responsible operator, restoration method,
and a safe recovery verification suitable to the change.
Do not assume admin access proves backups exist.
Do not delete starter/existing content or alter plugins/DNS at this step.
If access or recovery is inadequate, state the blocker and prepare local
content work only; do not claim WordPress setup is complete.

Recovery prompt

Diagnose the Step 4 blocker using the supplied observation.
Separate WordPress access, hosting access, backup creation and restoration.
Give the operator a precise request without credentials in the document.
Preserve the baseline and do not advance to WordPress writes until the
necessary destination and recovery arrangements are verified.

Step 5 Prepare truthful page content

Codex prompt

Read the project brief and approved source notes.
Create docs/fact-register.md and content/home.md, content/about.md,
content/services.md and content/contact.md.
For each claim record its source, certainty and approval state.
Write clear visitor-focused content with a single main contact action.
Describe each approved service's audience, approach, deliverables and limits.
Do not invent results, clients, awards, legal status or testimonials.
Use no unapproved contact or images. Mark practice content clearly.
Do not publish. Flag owner decisions and record actual output in progress.

Recovery prompt

Edit the four drafts against the fact register.
Remove unsupported claims and preserve uncertainty and dates.
List unresolved approvals separately; do not fill gaps with invented facts.
Show the corrected wording and update the register.

Step 6 Fix the page map and editing approach

Codex prompt

Read the approved content and WordPress inventory.
Create docs/page-map.md with four pages, purpose, proposed slug,
navigation label, primary action and exact intended destination.
Preserve useful existing URLs or flag redirect decisions.
Select one maintainable editing approach appropriate to this installation.
Explain how the owner will edit routine text afterward.
If using custom HTML/CSS, scope it and identify how saving and template
behavior will be tested. Avoid adding a framework or paid builder.
Record the chosen approach for my review; do not create duplicates.

Recovery prompt

Reconcile the page map with the actual existing pages and editor.
Identify duplicates and URL risks without deleting anything.
Propose one consistent editing route and the minimum decisions needed.
Update the map only after recording the chosen resolution.

Step 7 Define a restrained visual direction

Codex prompt

Create docs/design-spec.md for this four-page site.
Specify readable typography, color roles, spacing, content width,
header/navigation, buttons, image policy, focus states and mobile behavior.
Use the approved business character and content, not invented credentials.
Propose one restrained direction with a simple page sketch or supported
local preview. Do not claim a screenshot establishes accessibility.
Prefer lightweight assets and minimal dependencies.
Record what I need to inspect and wait for my design choice before
applying the style across WordPress.

Recovery prompt

Revise only the design issues I identify.
Preserve the approved content and page map.
Reduce visual complexity, explain each change and show the affected
wide/narrow states. Do not introduce unapproved assets or dependencies.

Step 8 Build and save Home

Codex prompt

Implement Home from the recorded design and content on the authorized
test draft. Verify the exact site and page identity before writing.
Use the agreed editor. Keep source in wordpress/home and explain how it
maps to WordPress. Do not change a live homepage assignment.

Where direct WordPress editing is available, save as Draft, reopen and
compare the saved result. Where unavailable, prepare the exact block
content or native-block instructions and give me one manual action at a
time, with expected output and confirmation checks.
Respect the template's heading and main-landmark structure.
Scope CSS; do not hide unrelated site elements globally without a
documented layout decision. Verify the result in the actual template.
Report the saved page ID/URL, source, screenshot/evidence and limitations.

Recovery prompt

Home failed its saved/rendered check. Preserve source and inspect the
exact page identity, error, editor role, template and relevant styles.
Compare intended versus saved content. Reproduce safely on test.
Change one likely cause at a time and verify the result.
Record temporary plugin changes and restore them after diagnosis.
Do not disable unrelated security controls or claim success from syntax
checks alone. Stop and state the gap if safe correction needs an operator.

Step 9 Complete About Services and Contact

Codex prompt

Create/update only the three mapped test drafts: About, Services, Contact.
Reuse the approved design and content without fabricating additional proof.
Verify each target identity, save, reopen and preview it.
Keep the authored source under wordpress/about, wordpress/services,
and wordpress/contact.
Connect navigation and contact actions to verified destinations in the
test environment. Identify planned public URLs separately from previews.
Confirm which header/footer is owned by the theme versus page content.
Do not publish pages or change production menus/homepage assignment.
Report all four page identities and any incomplete destination.

Recovery prompt

Reconcile the four-page inventory with the page map.
List each actual ID, state, URL and navigation target.
Fix wrong links or inconsistent shared styles on the authorized drafts.
Do not delete duplicates or overwrite unknown content without a specific
resolution. Repeat the complete visitor journey and record results.

Step 10 Verify contact and media

Codex prompt

Verify the contact route defined in the brief.
For email/phone links check exact destinations and explain that a link
opening an app does not prove message delivery or a completed call.
Do not add a form merely to make the page look complete.
If a form is explicitly included, inspect required/error/success states
and verify synthetic message receipt with the authorized operator.
Use no private customer data in tests or evidence.

Verify each image/file is approved, loads correctly, and has suitable
presentation and alternatives. Do not publish a supplied private CV.
Record contact and media results in docs/contact-media-checks.md.
Mark failures or unavailable tests honestly.

Recovery prompt

Diagnose the specific contact/media failure using authorized evidence.
Separate presentation, destination configuration and actual delivery.
Do not send real personal data or invent a successful receipt.
Correct and retest, or record the missing operator/service dependency.
Do not quietly replace a required form with a link without owner agreement.

Step 11 Correct mobile and keyboard behavior

Codex prompt

Check all four saved test pages at representative wide and narrow widths.
Record the actual viewport/device/browser, not only the requested size.
Inspect wrapping, unwanted document overflow, menu behavior, controls,
images, long text, headings, labels, reading order and visible focus.
Check that theme/page landmarks are not duplicated.
Use the keyboard for the main journey.
Correct observed issues with scoped changes and repeat affected checks.
Save evidence and docs/responsive-access-checks.md.
Do not claim comprehensive accessibility or all-browser conformance.
If browser tools are unavailable, give me an exact manual test list and
record my observed results separately from checks you performed.

Recovery prompt

Reproduce the reported layout/keyboard issue at the actual measured size.
Identify the responsible element or rule and make a bounded correction.
Preserve working pages. Retest saved WordPress output and the affected
visitor journey. State precisely which checks remain unavailable.

Step 12 Run acceptance checks and correct defects

Codex prompt

Create docs/acceptance-results.md for the exact current candidate.
Check owner-approved facts, all page/menu/action links, saved content,
contact/media evidence, responsive/keyboard results, and recovery readiness.
For each criterion record PASS, FAIL or UNTESTED, environment, date,
evidence and verifier. Distinguish my observations from yours.
Fix in-scope defects on test, then repeat affected checks.
List new requests separately; do not expand scope.
Do not mark the candidate ready while material criteria fail or required
checks are unperformed. Prepare a clear owner-review summary.

Recovery prompt

Audit the acceptance report against actual evidence.
Remove unsupported passes, identify stale results and prioritize blockers.
Fix only agreed defects and retest the exact changed candidate.
Explain any owner decision needed; do not use confidence as test evidence.

Step 13 Record source and identify the candidate

Codex prompt

Capture the accepted authored content, styles, safe configuration examples,
page map and instructions without secrets, enquiries or database dumps.
Record what is outside source control: database, media, plugins and host state.
If an authorized repository is available, use its declared branch/PR
workflow and do not overwrite unrelated history or change visibility.
Otherwise prepare a local source snapshot and precise repository setup
instructions; do not pretend GitHub is configured.

Create docs/release-candidate.md with exact source identity, page IDs,
evidence references, limits and candidate version, for example v0.1.0-rc.1.
Do not move published tags or deploy.
Explain how this source becomes saved WordPress content.

Recovery prompt

Inspect the source-control failure and preserve local candidate files.
Verify repository/branch identity and actual permissions/capabilities.
Do not force push, expose private material, or invent a repository state.
Give the smallest supported setup/reconciliation action and record its result.

Step 14 Obtain owner acceptance

Codex prompt

Prepare docs/approval-request.md for the candidate.
Separate content acceptance, release readiness, deployment authorization,
and public launch where applicable.
Include exact candidate/source, target URL/environment, contact mechanism,
known limits, backup/recovery reference and rollback triggers.
For practice mode request only the agreed test-site availability.
For client mode identify the real owner decision required for production.
Do not record approval until the authorized person explicitly provides it.
Do not deploy from this request.

Recovery prompt

Reconcile the candidate, target and recorded approval.
Identify missing, expired or invalidated decisions.
Prepare the corrected review request and stop before deployment.
Do not manufacture an approval or transfer it to a changed candidate.

Record the actual decision

Record this supplied owner decision in docs/approvals.md:
Approver and authority:
Candidate/source identity:
Target and mode:
Decision and conditions:
Date/time and evidence reference:

Check that the decision matches the current candidate and target.
Identify conditions not yet satisfied. Preserve rejection or deferral
accurately. Do not infer approval or proceed to deployment from this
recording task. Update progress with the next authorized action.

Step 15 Apply the approved deployment

Codex prompt

Read the exact Step 14 authorization and candidate record.
Before writing, verify the approved target, current state, source/artifact,
backup/restoration availability, operator and rollback triggers.
If any condition is missing or the destination has unexplained drift, stop.

Apply only the authorized deployment using the supported route.
For manual operation, give one precise action at a time and verify my
reported result before advancing. Do not invent hosting access.
Confirm homepage assignment, page states and intended menus.
Replace review-only URLs with verified final destinations where authorized.
Do not alter DNS, business email records, plugins or paid services unless
the specific change is separately authorized and necessary.

Record actions, operator, times, result and running state in
docs/deployment-record.md. On failure follow the approved recovery route,
verify restoration, and report the real state instead of declaring done.

Recovery prompt

Treat this as a deployment incident, not an opportunity to redesign.
Record what was applied, what failed and the current operating version.
Execute only the already authorized recovery or obtain the needed operator
decision. Verify service/content/contact state after recovery.
Preserve evidence and source; do not report successful deployment until
the intended destination is verified.

Step 16 Verify hand over and close

Codex prompt

Perform final verification of the actual deployed destination and mode.
Check all four pages, navigation, contact, approved media, saved content,
access state and known limits. Record who performed each check.
Guide manual checks when tools are unavailable; do not assume public
access from an authenticated preview.

Create docs/handover.md with routine editing steps, account/service owners,
renewals, backup/recovery references, support boundaries and outstanding work.
Include no credentials.
Reconcile source after any final edits and identify the running version.
Create docs/completion-report.md with actual hours and separate:
- verified completed work;
- accepted nonblocking limits;
- unresolved blockers;
- follow-up improvements.

Use DONE—PRACTICE only for a completed verified test-site exercise.
Use DONE—CLIENT only when authorized deployment, final checks and agreed
handover/source requirements are complete.
Otherwise use BLOCKED or IN PROGRESS with the exact remaining action.
Never upgrade the status merely because the planned time is exhausted.

Recovery prompt

The final completion check failed.
Identify the exact unmet criterion and return to the relevant step.
Preserve working parts and make the smallest justified correction.
Repeat affected verification, update source/records and reassess the real
completion state. Do not hide the failure in the handover document.

Appendix A Resume after an interruption

Resume this project without overwriting unknown work.
Read docs/project-brief.md, docs/working-agreement.md,
docs/environment.md and docs/progress.md.
Inspect the actual current files/site state with available authorization.
Summarize the last verified step, pending actions and any drift.
Do not infer missing approvals.
Continue only with the next uncompleted bounded task, preserving the
recorded scope and separating observed facts from assumptions.

Appendix B Return a manual result to Codex

Manual action report:
Step:
Environment and page/service:
Action I performed:
Expected result:
Actual result:
Error text or sanitized evidence:
Anything else that changed:

Evaluate this observation against the step's completion check.
Do not mark unavailable tests passed. Tell me the next single action,
or update the record if this step is genuinely complete.

Copyright © 2026 Henok Ahmed. The original educational text, prompts, tables and checklists in this publication are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You may share and adapt them, including commercially, with appropriate attribution, a link to the license, and an indication of changes. This grant excludes client websites, private materials, third-party software/assets, trademarks and personal data. Those materials retain their respective rights.

Source: https://henokahmed.com/wordpress-24-hour-prompts/

Release: Published from edition 1.0.0-draft.1 with approval on 28 October 2026. All 35 instructional prompts are unchanged.

Practical learning by Henok Ahmed · Educational text, prompts and checklists: CC BY 4.0, subject to stated exclusions.

Back to top ↑