メニュー
Product management frameworks for WordPress plugins — persona creation, Jobs to Be Done, feature hypothesis testing, positioning, problem framing, and user stories.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Capture clean, Mac-faithful WordPress admin + front-end screenshots from a JSON brief. Headless Chromium, login-aware, hides update bubbles and admin notices, defaults to 2× DPR, and writes a standalone HTML gallery alongside the PNGs. Works against any WordPress site you have credentials for.
Security-first WordPress development for 6.9+. Covers plugin architecture, block development (apiVersion 3, Interactivity API), block themes with theme.json, REST API, Abilities API, and the Security Trinity.
Engineering workflows for WordPress development including compound planning, code review, documentation generation, and git worktree strategies.
Craft effective AI prompts and technical blog posts. Covers prompt structure, cross-platform compatibility, token optimization, anti-patterns, and WordPress publishing workflows.
UI/UX review with motion design specifications. Covers animation principles, easing tokens, duration guidelines, WordPress Design System (WPDS) patterns, and interaction audit methodology.
WCAG 2.1/2.2 Level AA compliance for WordPress themes, plugins, and blocks. Covers automated audits, keyboard navigation, screen reader testing, ARIA patterns, and color contrast.
| name | Product Management for WordPress |
| description | Product management frameworks for WordPress plugins — persona creation, Jobs to Be Done, feature hypothesis testing, positioning, problem framing, and user stories. |
| triggers | ["persona","jobs to be done","JTBD","feature hypothesis","positioning","problem framing","user story","product management","product strategy"] |
Frameworks for WordPress plugin product management — from problem discovery through positioning and feature validation.
## Persona: [Name]
**Role**: [Job title / WordPress role]
**Technical level**: [Beginner / Intermediate / Advanced]
**Goals**: [What they're trying to accomplish]
**Frustrations**: [What's blocking them today]
**WordPress context**: [Site type, plugins, hosting]
**Decision factors**: [Price, reviews, features, support]
When [situation],
I want to [motivation],
so I can [expected outcome].
**We believe** [this feature]
**for** [this persona]
**will achieve** [this outcome]
**We'll know this is true when** [measurable signal]
**For** [target user]
**who** [has this need/problem]
**[Plugin Name]** is a [category]
**that** [key benefit].
**Unlike** [alternatives],
**we** [key differentiator].
As a [WordPress role],
I want to [action],
so that [benefit].
### Acceptance Criteria
- [ ] [Specific, testable condition]