Wp Requirements To Goals

Convert a full WordPress plugin requirements.md (multiple user stories, edge cases, settings, cross-cutting features) into a complete Codex /goal-ready project — goals-plan.md, root scaffold (.wp-env.json, package.json, AGENTS.md, plugin bootstrap, run-goals.sh, protocols), and a layered goals/ tree (foundation, per-US, non-US, integration). The full-workflow counterpart to wp-spec-to-goal — that handles single-goal vague specs; this handles multi-goal full requirements. Probes the repo first to skip clarifications the filesystem already answers (slug, namespace, WP/PHP versions). Asks remaining clarifications in ≤3 rounds. Supports phased (checkpoint after plan) or one-shot mode. Detects an existing goals-plan.md and offers to resume from Phase 2. Supports extend mode — on a completed project, appends new goals and writes only new goal folders without disturbing what shipped. Codex-only outputs — never references Claude Code or .claude/.

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                 │
…

mkdir -p ~/.claude/skills/wp-requirements-to-goals
curl -L https://claudskills.com/skills/wp-requirements-to-goals/SKILL.md \
  -o ~/.claude/skills/wp-requirements-to-goals/SKILL.md

@misc{wp-requirements-to-goals-2026,
  author    = {nathanonn},
  title     = {Wp Requirements To Goals [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/wp-requirements-to-goals/}
}