Work through a WordPress plugin task list step by step, building and testing each task before moving to the next. Reads from TASKS.md or a specified task file.
Plan a WordPress plugin through a structured discovery conversation. Asks questions to uncover requirements, blind spots, and edge cases, then produces a PRD markdown file. Run this before /plugin-tasks.
Generate a structured task list for building a WordPress plugin feature or entire plugin. Reads a PRD file produced by /plugin-plan and outputs a markdown file with sequential, testable steps.
Modern WordPress plugin development skill. Use this skill whenever the user is building, scaffolding, debugging, testing, or refactoring a WordPress plugin. Trigger when the user mentions WordPress plugins, WooCommerce extensions, custom post types, custom blocks, Gutenberg blocks, wp-env, WordPress hooks, actions, filters, REST API endpoints for WordPress, WordPress admin pages, settings pages, plugin activation/deactivation, or any PHP development targeting the WordPress ecosystem. Also trigger when the user mentions plugin file structure, plugin headers, WordPress coding standards, WPCS, PHPUnit for WordPress, Playwright for WordPress, or wp-scripts. Even if the user just says "plugin" in the context of a WordPress project, use this skill.
Audit the current state of a WordPress plugin against its task list. Reads the tasks file and inspects the actual codebase to report what's done, what's incomplete, and what's missing entirely.