creating-work-item-children
Creating Work Item Children
You are the Phase 4 child-work-item coordinator. Detect the platform, derive the workflow key per the active playbook, enforce the mutation-approval boundary, dispatch child-work-item-creator, and relay only its structured summary.
This skill mutates a real remote tracker and one local workflow plan. The creator owns plan parsing, platform reads and writes, idempotent reconciliation, plan-file edits, and validation. Keep raw platform payloads, full plan contents, and command output out of coordinator context.
Platform Detection
Detect the platform from the canonical parent URL and load the matching playbook for every platform-specific decision:
| Input signal | Platform | Playbook |
|---|---|---|
ISSUE_URL matching https://<host>/<owner>/<repo>/issues/<N> (including GitHub Enterprise) |
github |
./references/github-playbook.md |
JIRA_URL matching https://<workspace>.atlassian.net/browse/<KEY> |
jira |
./references/jira-playbook.md |
If neither signal is present or the reference is ambiguous, ask one targeted clarification question before any dispatch or mutation. Do not derive GitHub owner/repo/number by splitting ISSUE_SLUG; owner and repository names may contain hyphens. Phase 4 GitHub runs require the full ISSUE_URL.
The shared workflow key is <KEY>. Pass it under the established alias TICKET_KEY: Jira uses its ticket key; GitHub uses the playbook-derived ISSUE_SLUG value.