Give the next task a documented starting point.
Have AI inspect the site within its authorized access and save what it finds. The result should distinguish observed facts, working rules and unanswered questions.
Use the seven areas below as a checklist. A missing answer stays a gap to investigate.
Record the environment.
Identify the hosting, WordPress/PHP versions, caching and scheduled jobs relevant to the project. Name the environment being inspected.
Useful output: a short environment map showing the website, its relevant dependencies and any limits on the preview or release route.
Describe plugins and integrations.
Record what the relevant plugins do, which content or builder tools are in use and how outside systems connect.
Useful output: an explanation of the systems affected by the proposed work, including what must be checked after a change.
Find the theme and template owners.
Identify the files rendering the relevant page types and the location of custom code. Record the fields each template reads.
Useful output: a map from the page or behavior to its active template and editable data, with unused or unknown paths clearly marked.
Map pages and editable content.
Record page structure, menus, content types and shared content. Identify what the team manages in WordPress and what comes from code.
Useful output: an editing map that guides the next task to the right content record or field.
Preserve known issues and constraints.
Record existing bugs, inconsistent approaches and fragile areas. Describe how the problem was observed and what remains uncertain.
Useful output: a list of constraints the task must account for, without treating an old issue as proof that a new change caused it.
Save the visual rules.
Document colors, typography, spacing, layouts and patterns to preserve or avoid. Use actual website evidence rather than a generic brand style.
Useful output: concrete instructions such as which section to reuse and which visual relationships should stay consistent.
Explain reusable sections and components.
Record how the pieces fit together and how shared components behave across screens. Explain where a page can reuse an existing section.
Useful output: a practical guide to extending the site without making every task start from a blank layout.
Keep the instructions current.
Save the knowledge beside the project. After a consequential change, refresh the affected facts and rules.
When reviewing a result, turn a reusable correction into an instruction for future tasks. Ask the next task to read the current instructions before working.