You’re about to launch a client’s WordPress site. The pressure is on. Did you remember to disable XML-RPC? Is that caching plugin configured correctly? The nagging fear of a missed step—a security hole, a broken form—keeps you up at night. Scattered notes and generic checklists fail for complex, professional projects.
This prompt is your solution. It transforms a simple project brief into a dynamic, exhaustive, and actionable professional checklist. It thinks like a senior developer, covering everything from core setup to post-launch protocols. Stop guessing. Start executing with flawless confidence.
📋 The Prompt
**Project Context:**
– Project Type: [e.g., Corporate Brochure Site, E-commerce Store, Membership Portal]
– Primary Goal: [e.g., Generate Leads, Sell Products, Share Knowledge]
– Key Plugins/Framework: [e.g., WooCommerce, LearnDash, GeneratePress]
– Technical Constraints: [e.g., Shared Hosting, Must use Divi, Multisite]
**Output Requirements:**
1. Structure the checklist in clear, sequential phases: Pre-Development, Development, Pre-Launch, Launch, Post-Launch.
2. For each phase, list critical tasks. Each task must be an actionable item, not a vague category.
3. For key technical tasks (e.g., '.htaccess' rules, database optimization), provide a brief "Why This Matters" note.
4. Flag 3-5 items as "Critical Priority – Do Not Skip" with a brief risk explanation.
5. Include a final "Client Handoff" section listing items to document and communicate.
How It Works
This prompt works because it replaces a static document with a dynamic reasoning engine. You’re not asking for a list; you’re hiring a virtual senior architect. The magic is in the structure.
First, the role and context force specificity. “Senior WordPress architect” triggers a mindset of thoroughness and risk aversion. The Project Context fields are crucial—a checklist for an e-commerce site is radically different from one for a blog. This customization is the core value.
The phased output requirement is the strategic framework. It mirrors a real project lifecycle. The ‘Pre-Development’ phase includes scope sign-off and hosting checks—things often forgotten in code-focused lists. ‘Pre-Launch’ is where most failures happen; this prompt ensures a dedicated audit stage.
Demanding “actionable items” and “Why This Matters” notes transforms the list from a rote task sheet into an educational and decision-making tool. You understand the purpose, which is vital for junior team members or when justifying steps to a client.
Identifying “Critical Priority” items performs risk assessment for you. It highlights the show-stoppers—like missing an SSL certificate or broken checkout—so resources are allocated correctly. This is the kind of insight covered in our Mastering WordPress Prompt guide.
Finally, the “Client Handoff” section enforces professionalism. It ensures knowledge transfer and sets clear post-launch expectations, closing the loop on the project. This holistic approach is what makes it the ultimate checklist, far beyond a simple to-do list.
Pro Tips & Variations
Advanced Customization: After generating the base list, paste it back into the AI and command: “For the ‘Pre-Launch’ phase, expand each security task into a sub-checklist of verification steps.” This creates nested, hyper-detailed procedures.
Common Mistake: Being too vague in the Project Context. ‘Corporate Brochure Site’ is good. ‘Website’ is useless. The better the input, the more surgical the output. For deep thinking on crafting the perfect project brief, see our Deep Philosophical Prompt guide.
Tweak for Audits: Change the first line to “…create a comprehensive health audit checklist for an EXISTING WordPress site.” Change the phases to: Discovery, Security Audit, Performance Audit, Content/SEO Audit, Action Plan. This repurposes the engine for site reviews.
Tweak for Speed: Add this instruction: “Prioritize this checklist for a 1-week launch sprint. Mark items that can be automated or delegated.” The AI will highlight levers for 10x productivity.
Pro Integration: Use the generated checklist as the agenda for your launch meeting. Assign each item an owner and a due date directly from the AI’s output, making it a living project management document.
Frequently Asked Questions
Can I use this for a site that's already live?
Absolutely. Input the project type as “Site Maintenance & Hardening” and use the ‘tweak for audits’ tip above. It will generate a superb checklist for evaluating and improving an existing site’s security, speed, and structure.
The list is huge! Do I really need to do everything?
The prompt is designed to be exhaustive so you don’t miss anything. The “Critical Priority” flags are your guide for must-dos. For other items, use your judgment. The checklist is a map; you choose the route based on project scope and risk tolerance.
How do I handle checklist items for plugins I'm not using?
The AI bases its tasks on the “Key Plugins/Framework” context you provide. If you list WooCommerce, it will include WooCommerce-specific steps. If you’re using a lightweight stack, the list will adapt. Be precise in your input for a relevant output.
Can this prompt create checklists for team members with different skills?
Yes. The actionable nature of each task makes it clear. You can further instruct the AI: “Mark tasks suitable for a junior developer with [J] and tasks requiring senior/admin access with [S].” This helps with delegation and permission planning.
Is this better than a template I download?
Infinitely. A static template is generic and grows stale. This prompt generates a living checklist tailored to your specific project’s technology, goals, and constraints. It thinks through the unique requirements each time, which a template cannot do.
