To SEO Issues

Convert an approved strategy into bounded work packages, obtain approval, then publish them to the project issue tracker. A work package is complete on controllable delivery evidence; delayed organic outcomes belong to a separate review.

The issue tracker and label vocabulary should be configured. If they are missing, show /setup-matt-pocock-skills and stop before tracker mutations.

1. Establish the source and scope

Read SEO-STRATEGY.md and the linked research. Use the strategy schema in the SEO strategy templates. Require Status: Active and an approval date; never convert a Proposed strategy or a proposal/research file by itself.

When initiative IDs are supplied, select only those. Otherwise select eligible Now initiatives. List Next and Later initiatives with their activation conditions, but do not create issues for them.

Inspect tracker context, existing strategy and child issues, repository capabilities, and known access or approval constraints. Infer before asking; ask only when an unresolved choice would change the package graph.

Complete when: the authoritative strategy, selected initiatives, existing tracker state, and material execution constraints are known or explicitly unknown.

2. Reconcile the active strategy

Find the thesis issue through the strategy's Tracker issue metadata or a unique match on strategy identity. Reuse it; never duplicate it. If none exists, propose a thesis parent using the issue templates.