Project Overview
Case study: WP OneShot is an Agentic Development Environment for integrating AI and Coding Agents into WordPress development and the main public example of my work on Agentic Work Systems.
It prepares isolated local stacks, instructions, briefs, tools and quality gates so that a Coding Agent can work within an understandable and verifiable scope. Its file-based foundation allows different Coding Agents to use the same environment; in my daily work I mainly use Codex and Claude Code.
Related services: advanced WordPress sites and technical WordPress consulting.
The project is currently in active development with a public waitlist at wponeshot.com.
Key Features
Project Scaffolding and Local Stack Management
- Isolated WordPress Environments: Each plugin project gets its own Docker-based WordPress stack with dedicated ports, source folders, and runtime configuration — completely separate from other projects.
- Create or Import Plugins: Start from a clean plugin skeleton or wrap an existing plugin in a WP OneShot project structure without disrupting the existing codebase.
- VS Code-Ready Projects: The generated project folder opens directly in VS Code with local stack and project instructions already in place, eliminating setup friction.
Structured AI Agent Context
- AGENTS.md and MCP Configuration: Every project includes model-neutral AGENTS.md instructions and
.mcp.jsonfiles that define tool boundaries, capabilities, and WordPress-specific surfaces for AI coding agents. - One-Shot Brief Builder: A dedicated dashboard module helps formulate structured implementation briefs, turning vague plugin ideas into scoped, context-rich prompts for AI agents.
- Capability-Aware Intake Files: Toolkit definitions and intake bundles travel with the project into VS Code, so agents like Claude Code or Codex have the full implementation contract before writing a single line of code.
Quality Gates and Release Preparation
- Multi-Stage Validation: Doctor, validation, repair, commit, preflight, and CI-oriented gate scopes ensure that checks happen close to the work, not as a last-minute afterthought.
- Pre-Release Readiness Checks: A preflight workflow confirms that a plugin meets defined quality criteria before packaging, reducing the risk of shipping broken or incomplete releases.
- Repeatable Process: The entire gate system is designed to be run locally and consistently across projects, making quality a structural property of the workflow rather than a manual checklist.
Dashboard Interface
- Unified Control Panel: The WP OneShot dashboard centralizes project creation, stack management, brief building, context inspection, and gate execution in one interface.
- Multi-Project Organization: Freelancers, agencies, and plugin makers can manage multiple plugin projects simultaneously without mixing project state or environment configuration.
Purpose
WP OneShot was born from direct experience with the gap between AI coding capability and WordPress plugin reality. AI agents can write code efficiently — but without a structured project contract, a local WordPress environment to validate against, and quality gates to enforce standards, the output is hard to trust and harder to ship.
The tool targets three audiences: freelancers who want to stop rebuilding the same scaffolding for every new plugin engagement; agencies that need a shared vocabulary for plugin capabilities, review roles, and handoffs; and plugin makers who want to keep experiments and release candidates organized without blending project state and tool configuration.
Building WP OneShot brought together several disciplines from my background — WordPress architecture, developer tooling, local environment management, and AI workflow design — into a single cohesive product. It reflects my conviction that good tooling is what turns AI assistance from a novelty into a reliable part of a professional development workflow.
