ai-to-tickets-workplan

Read one stored Workplan spec, split it into tracer-bullet tickets, and publish its prerequisite graph. The invocation authorizes publication without another approval round.

Before using wp, load the ai-workplan skill. If it is unavailable, stop and tell the user to install it. Follow its pointers to the machine-output, workplan, project, label, ticket, and dependency references. Those references define the command flags, envelopes, pagination, selectors, and typed errors.

Process

Resolve one spec. Prefer an explicit spec slug, then the canonical resource returned by an immediately preceding ai-to-spec-workplan invocation, then an exact slug named in the conversation. Otherwise list every spec workplan through wp --json workplan list --type spec, following all cursors. Use the sole result when exactly one exists. Similar titles, recency, and workplan content do not make a choice unique.

Ask for an exact spec slug only when these rules produce no unique target. Make no tracker mutation before resolution. For a selected slug, run wp --json workplan show <slug>, check schema_version, and require the returned type to be spec. Return any typed lookup failure instead of substituting another workplan. The stored content_markdown is the source spec; do not use a conversation copy in its place.

This step is complete when one exact stored spec resource has been read through wp --json.
Resolve projects and the publication label. List projects through wp --json project list, following every cursor. Resolve each explicit project to its listed canonical path. For a ticket without an explicit project, resolve the directory that owns the ticket's work and select the longest registered ancestor. Record that canonical path in the draft. Resolve project context independently for every ticket, so one graph may span several projects. An intentionally unassigned ticket uses --no-project.

List labels through wp --json label list, following cursors until ready-for-agent is found or the list ends. Stop before publication when the canonical label is absent. Setup, not this skill, owns project registration and label creation. Pass the recorded project selection explicitly on every create; never rely on the caller's current directory during publication.

This step is complete when every draft has an explicit canonical project path or an explicit unassigned selection, and ready-for-agent exists.