What is wp-requirements-to-goals?

A project generator that turns a complete WordPress plugin requirements file into a structured Codex goal project. It creates the project setup and a series of smaller implementation goals with browser checks.

Use it to prepare a multi-feature WordPress plugin for staged development, including setup files, implementation goals, shared project notes, and verification instructions.

It removes the manual work of breaking a large plugin specification into an order of tasks that an coding agent can follow and verify.

wp-requirements-to-goals — Skill for Claude Code and Codex by nathanon

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add nathanonn/agent-skills --skill wp-requirements-to-goals

Clone the repo

git clone --depth 1 https://github.com/nathanonn/agent-skills

Made for: Claude Code, Codex.

Or install wp-requirements-to-goals, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nathanonn/agent-skills/wp-requirements-to-goals/github.svg)](https://agentmods.dev/skills/nathanonn/agent-skills/wp-requirements-to-goals)

Your own site

<a href="https://agentmods.dev/skills/nathanonn/agent-skills/wp-requirements-to-goals"><img src="https://agentmods.dev/badge/skills/nathanonn/agent-skills/wp-requirements-to-goals/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nathanonn/agent-skills/wp-requirements-to-goals"><img src="https://agentmods.dev/badge/skills/nathanonn/agent-skills/wp-requirements-to-goals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 213 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 10,435 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00213	$0.10435
Opus 5	$0.00106	$0.05217
Sonnet 5	$0.00043	$0.02087
Haiku 4.5	$0.00021	$0.01043

Measured 12d ago against content hash 6ecea7d3d0df, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade C, and why

wp-requirements-to-goals scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (references/run-goals-template.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

2. **Sanitize, then atomic mv.** Run the sanitizer (`references/sanitizer.md`) over the whole tmp tree. On a clean pass, `mv` each top-level entry into the project root. On any sanitizer hit, `rm -rf` the tmp tree and st

plugins/wp-requirements-to-goals/skills/wp-requirements-to-goals/SKILL.md · 531 lines

How it starts

The opening of the file, as written. The whole thing — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.

wp-requirements-to-goals — Full WP Plugin Requirements → Codex /goal Project

Convert a complete WordPress plugin requirements.md (multiple user stories, edge cases, settings catalog, cross-cutting features) into the full project structure Codex /goal needs to drive autonomous implementation across many goal slices.

Prerequisite — playwright-cli. Every goal's VERIFY.md runs its browser checks through playwright-cli. Install it once on the machine that runs /goal: npm install -g @playwright/cli@latest then playwright-cli install --skills (needs Node.js 18+). Phase 2 also host-detects an installed playwright-cli skill and bundles it into .codex/skills/ so Codex can reach it during execution.

project-root/
├── requirements.md           ← input
├── goals-plan.md             ← Phase 1 output
├── _shared/                  ┐
│   ├── project-config.md     │  ← Phase 1 (identity + env + skill refs, single source of truth)
│   └── dev-patterns.md       │  ← Phase 1 (extracted from input CLAUDE.md/AGENTS.md if present)
├── README.md                 │
├── AGENTS.md                 │
├── .wp-env.json              │
├── package.json              ├─ Phase 2 (root scaffold)
├── run-goals.sh              │  bash automation — drives every goal via codex exec
├── fixtures/.gitkeep         │
├── .codex/skills/            │  ← Phase 2 (host-detected playwright-cli skill, if bundled)
│   └── playwright-cli/       │
├── <slug>/                   │  plugin bootstrap (folder name = slug)
│   ├── <slug>.php            │
│   ├── src/Plugin.php        │
│   └── composer.json         │
├── protocols/                │
│   └── run_goal_tests.md     ┘  canonical verification protocol
└── goals/
    ├── 00-foundation/        ← Phase 3 (walking skeleton)
    ├── 01-usXX-<slug>/       ┐
    ├── 02-usXX-<slug>/       ├─ Phase 4 (one folder per US)
    ├── ...                   ┘
    ├── NN-<feature-slug>/    ← Phase 5 (one per non-US feature)
    └── NN-integration/       ← Phase 6 (cross-cutting + edge-case suite)

_shared/ is the cross-goal vocabulary home: project-config.md carries APP_NAME / NAMESPACE / CSS_PREFIX / ports / credentials / skill references, and per-phase templates indirect into it instead of inlining the values. dev-patterns.md is populated only when the input project has a CLAUDE.md or AGENTS.md worth extracting from; otherwise it's omitted. See references/scaffold-templates.md for both files' templates.

Each goal folder contains:

goals/NN-slug/
  GOAL.md                  objective, scope, ACs, allowed paths, depends-on, DoD
  VERIFY.md                wp-env up + domain check + browser protocol invocation + manual smoke
  PROGRESS.md              audit trail (populated by /goal during execution)
  tests/
    test_plan.md           one TC per AC + one TC per owned edge case
    domain.eval.txt        wp eval-file script for server-side checks

Read the full file on GitHub · 531 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 531 lines · 213 tokens per session scan C 6ecea7d3d0df

Subscribe to this mod's changes

wp-requirements-to-goals is a skill published in the GitHub repository nathanonn/agent-skills (19 stars, last pushed 23d ago), licensed MIT. It adds 213 tokens to every session and 10,435 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

wp-requirements-to-goals