feat(skill): add /plan-to-issues skill#744
Merged
JeremyDev87 merged 1 commit intomasterfrom Mar 21, 2026
Merged
Conversation
…rsion - Convert completed PLANs into GitHub parent + sub-issues - Use GitHub native sub-issue API with label+comment fallback - Three principles: Independent, Deployable, Structured - Issue body has essentials only, details go into comments - 7-step workflow with user confirmation before creation - v2.0 frontmatter: disable-model-invocation, argument-hint, allowed-tools
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/plan-to-issuesskill that converts completed PLANs into GitHub parent + sub-issues/repos/{owner}/{repo}/issues/{number}/sub_issues) with label+comment fallbackdisable-model-invocation,argument-hint,allowed-tools,user-invocablepriority:must/should/couldmappingTest plan
/plan-to-issuesappears in/menu/plan-to-issuesafter a PLAN session and confirm issue creation flow