Agent skill · luongnv89
plan-to-issues
Convert any phased plan file, or a conversation about what to build, into labelled GitHub issues under one tracking epic mapping each issue to its source task. No plan file required. Don't use for writing plans, resolving issues, or triage.
What it needs
About 12k tokens when loaded.
What this skill does
Plan to Issues Carries finished intent into the tracker. It takes either a phased plan file — any path, any producer — or the user's own conversational intent when no file exists, and produces: Artifact Contents --- --- One epic issue Whole-effort acceptance criteria + the epic plan map: every child issue grouped by phase, with goals, milestones, and critical path. Live open/closed status comes from GitHub's sub-issues panel, not the body One issue per task Body written by /issue-creator, bound with Part of #<epic>, carrying a deterministic label set The output is identical for both inputs. The source stays the design record; the epic answers "how far along is it?" without reopening it. Ownership split Own four things, delegate the rest. Never write an issue body; never invent work. Concern Owner --- --- Resolving the input, building the worklist, the label set, the epic plan map this skill Issue and epic bodies, templates, acceptance criteria, duplicate checks /issue-creator Resolving, triaging, analysing any issue out of scope — /issue-resolver, /issue-triage, /issue-analysis Leading terms One line each; full definitions in references/glossary.md. input — a plan file at any path, or conversational intent from the user's turns. task — one atomic unit of work. One task, one issue. worklist — the structured parse of the input; one schema for both inputs. label set — phase:<p>, one type label, dim:<d> per closed dimension, priority:<p>. epic plan map — the phase-grouped block between <!-- plan-dashboard:start --> and <!-- plan-dashboard:end -->. Static: it names which issue implements which task and asserts no status, so it never goes stale. Only that region is ever rewritten. source marker — binds an epic to its input: <!-- plan-to-issues:plan=<path> --> on the file path (unchanged from 1.x, so existing epics keep resolving), or <!-- plan-to-issues:conversation=<slug> --> on the conversation path. source-faithful — every word of every issue traces to the input. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills luongnv89/plan-to-issues