wordpress-scaffoldlisted

# WordPress Scaffold Scaffolds a brand-new WordPress plugin through a short interview. **Greenfield only** — if a `*.php` file with a `Plugin Name:` header already exists in the working directory, stop and use the `wordpress-feature` skill. ## Phases 1. **Identity.** Ask one question at a time, don't continue without a clear answer: - Plugin name (e.g. "Order Tracker") - One-sentence description - Vendor prefix (optional, e.g. `acme`) - Slug — derive `acme-order-tracker` or `order-tracker`; confirm - PHP namespace — PascalCase from slug, e.g. `AcmeOrderTracker`; confirm Show the full identifier set before generating: slug, text domain (= slug), namespace, constant prefix, function prefix, options key. 2. **Constitution.** Write `.claude/plans/constitution.md` from the template in @.claude/references/PLANNING.md. The file has two binding levels: - **Default sections** (loose) — `@wordpress/*` packages, Composer deps, deploy lane, quality gates. Accept the template defaults unless the user wants different. - **Allowed sections** (strict, security-relevant) — sanitize functions, escape functions, capability constants, forbidden constructs. Match @.claude/references/SECURITY.md exactly. Confirm both before writing. The distinction is the point: treat everything as strict and the agent asks permission for trivia; treat nothing as strict and the plugin is one missing escape from disclosure. 3. **Feature selection.** Ask one at a time: Settings page