name	plan-issue
description	Turn the feature plan from the current conversation into one or more GitHub issues and cut a feature branch. Run this AFTER a plan is agreed (e.g. after plan mode) and BEFORE writing any code. Do not use once commits exist — use open-pr for that.

plan-issue

Convert the plan produced in this conversation into well-formed GitHub issue(s) matching bfportal conventions, then cut a single feature branch to work on. A feature typically decomposes into several issues that later share one PR (e.g. #248/#249/#250 → PR #251).

Preconditions

A plan/spec has been discussed in this session. If no clear plan exists, ask the user to share or point to it — do NOT invent scope.
Working tree is clean and on main (or an up-to-date base). If not, tell the user and stop; don't stash or switch over uncommitted work.

Steps

Split the plan into issues. One issue per logical, independently-describable change (mirror how a feature breaks into backend/models/frontend pieces). A small plan may be a single issue; don't force a split.
Draft each issue. Do not re-plan; summarize what was agreed.
- Title: imperative, concise, no trailing period. E.g. Register BF6 scripts models and add migration.
- Body: match the house format —
  - One plain intro line describing the change.
  - A bulleted list of concrete specifics; wrap identifiers, files, and symbols in backticks (`ScriptsCategory`, `bf6.models`, `0003`).
  - No "Part of the X feature" footer — the PR will link these issues, so the relationship is captured there.
Pick labels per issue (pass each with its emoji exactly as gh label list shows):
- Exactly one type:* — type:backend 🖥, type:frontend 🏞, type:style 🎨, or type:3rd party 🧿. If an issue spans backend+frontend, apply both.
- enhancement ✨✨ for new features/requests, bug ⚠ for fixes.
- Add a priority (0 priority: High 🥇 / 1 priority: medium 🥈 / 2 priority: Low 🥉) only if the user stated urgency; otherwise leave unset.
- Do NOT add Has PR — that is applied by the open-pr skill.
Show the user the drafted title/body/labels for every issue — plus the master issue (step 6). Get a thumbs-up (or edits) before creating — issue creation is outward-facing.

Create the issues:

gh issue create --title "<title>" --body "<body>" \
  --label "enhancement ✨✨" --label "type:backend 🖥"

Capture each issue number from the returned URLs.

Always create a master/umbrella tracking issue that groups the sub-issues (skip it only when the plan is a single issue — a master over one child is pointless). Its body summarizes the overall feature (intro + why); do not list the sub-issues as a - [ ] #NNN checklist — the native links added in step 7 render that panel automatically. Give it the union of the sub-issues' type:* labels plus enhancement ✨✨.

Link each sub-issue to the master using GitHub's native sub-issue feature (not just a task list). Fetch node IDs, then call the addSubIssue GraphQL mutation:

PARENT=$(gh issue view <master#> --json id -q .id)
for n in <child#> <child#> ...; do
  CHILD=$(gh issue view "$n" --json id -q .id)
  gh api graphql -f query='mutation($p:ID!,$c:ID!){addSubIssue(input:{issueId:$p,subIssueId:$c}){subIssue{number}}}' \
    -f p="$PARENT" -f c="$CHILD"
done

This makes the children appear in the master's Sub-issues panel (with a progress bar) and shows the parent on each child.

Cut ONE feature branch from up-to-date main, named after the feature (kebab-case, descriptive — e.g. bf6-scripts-snippets), NOT after any issue number, since the branch/PR bundles all the issues:
```
git fetch origin main
git switch -c <feature-slug> origin/main
```
Report every issue number/URL (master + sub-issues) and the branch name. Note the sub-issue numbers so the eventual open-pr can link them all. Do not commit or push anything.

Notes

Never fabricate scope not present in the discussed plan.
If gh isn't authenticated, tell the user to run ! gh auth login rather than guessing.

plan-issue

Preconditions

A plan/spec has been discussed in this session. If no clear plan exists, ask the user to share or point to it — do NOT invent scope.

Working tree is clean and on main (or an up-to-date base). If not, tell the user and stop; don't stash or switch over uncommitted work.

Steps

Split the plan into issues. One issue per logical, independently-describable change (mirror how a feature breaks into backend/models/frontend pieces). A small plan may be a single issue; don't force a split.

Draft each issue. Do not re-plan; summarize what was agreed.

Title: imperative, concise, no trailing period. E.g. Register BF6 scripts models and add migration.
Body: match the house format —
- One plain intro line describing the change.
- A bulleted list of concrete specifics; wrap identifiers, files, and symbols in backticks (`ScriptsCategory`, `bf6.models`, `0003`).
- No "Part of the X feature" footer — the PR will link these issues, so the relationship is captured there.

Pick labels per issue (pass each with its emoji exactly as gh label list shows):

Exactly one type:* — type:backend 🖥, type:frontend 🏞, type:style 🎨, or type:3rd party 🧿. If an issue spans backend+frontend, apply both.
enhancement ✨✨ for new features/requests, bug ⚠ for fixes.
Add a priority (0 priority: High 🥇 / 1 priority: medium 🥈 / 2 priority: Low 🥉) only if the user stated urgency; otherwise leave unset.
Do NOT add Has PR — that is applied by the open-pr skill.

Show the user the drafted title/body/labels for every issue — plus the master issue (step 6). Get a thumbs-up (or edits) before creating — issue creation is outward-facing.

Create the issues:

gh issue create --title "<title>" --body "<body>" \
  --label "enhancement ✨✨" --label "type:backend 🖥"

Capture each issue number from the returned URLs.

Always create a master/umbrella tracking issue that groups the sub-issues (skip it only when the plan is a single issue — a master over one child is pointless). Its body summarizes the overall feature (intro + why); do not list the sub-issues as a - [ ] #NNN checklist — the native links added in step 7 render that panel automatically. Give it the union of the sub-issues' type:* labels plus enhancement ✨✨.

Link each sub-issue to the master using GitHub's native sub-issue feature (not just a task list). Fetch node IDs, then call the addSubIssue GraphQL mutation:

PARENT=$(gh issue view <master#> --json id -q .id)
for n in <child#> <child#> ...; do
  CHILD=$(gh issue view "$n" --json id -q .id)
  gh api graphql -f query='mutation($p:ID!,$c:ID!){addSubIssue(input:{issueId:$p,subIssueId:$c}){subIssue{number}}}' \
    -f p="$PARENT" -f c="$CHILD"
done

This makes the children appear in the master's Sub-issues panel (with a progress bar) and shows the parent on each child.

Cut ONE feature branch from up-to-date main, named after the feature (kebab-case, descriptive — e.g. bf6-scripts-snippets), NOT after any issue number, since the branch/PR bundles all the issues:

git fetch origin main
git switch -c <feature-slug> origin/main

Report every issue number/URL (master + sub-issues) and the branch name. Note the sub-issue numbers so the eventual open-pr can link them all. Do not commit or push anything.

Notes

Never fabricate scope not present in the discussed plan.

If gh isn't authenticated, tell the user to run ! gh auth login rather than guessing.

plan-issue

plan-issue

Preconditions

Steps

Notes

このリポジトリの他の Skills

このリポジトリの他の Skills

plan-issue

Preconditions

Steps

Notes