Skip to content

GravionLabs/elysion / .agents/skills/github-issue

github-issue

Verified

GitHub issue conventions: types, [Level] titles, branches, commits, native sub-issues, plan-to-issue creation. Use for any GitHub issue work.

references/create-from-plan.md

View on GitHub
# Create issues from a plan

Input: the `plan.json` of `planner` (its `references/plan-schema.md`). The plan has no issue
numbers of its own; this procedure creates the issues, links them to the parent and sets the
blocked-by links. Link calls and their gotchas: `sub-issues.md`.

## 1. Before anything is created

- `status` is `ok`; on `fail` show `summary` and stop.
- Show every entry of `questions[]` (question, options, recommended, why, blocked items) to the
  user and wait for the answers. Fold the answers into the affected item bodies; create nothing
  before that.
- Show the items (id, title, size, `blocked_by`) for approval.

## 2. Create each item, in plan order

| `level`   | Title               | Label     |
| :-------- | :------------------ | :-------- |
| `feature` | `[Feature] <title>` | `feature` |
| `pbi`     | `[PBI] <title>`     | `pbi`     |

There is no `task` level: no `[Task]` issue is created.

The body is used as given; its first line is already `Parent …: #N` (none for a split of an issue without parent).

A split of a PBI or Bug (`input_type` `pbi` or `bug`): `p1` is not created, it replaces the title and body of `parent_issue` (`gh issue edit <parent_issue> --title "<its level prefix> <title>" --body-file -`, `$created['p1'] = <parent_issue>`); the other items are created as `[PBI]`s.

```powershell
$url = $item.body | gh issue create --label <level> --title "[<Level>] <title>" --body-file -
$nr  = [int]($url -split '/')[-1]   # remember: $created[<plan id>] = $nr
```

## 3. Link to the parent

Link every created issue to `parent_issue` (`sub-issues.md`, "Link a child to a
parent"); in a split, to the Feature of the body's first line (no line: no link). A plan from a
description creates no issues.

## 4. Blocked-by links

For every item and every entry of its `blocked_by`: a plan id (string) resolves to
`$created[<id>]`, an integer is an existing issue number and stays. Then add the link per
`sub-issues.md`, "Blocked-by links" (database id of the blocker, `-F issue_id=`).

## 5. Verify

Per `sub-issues.md`, "Verify": the parent's `sub_issues` count equals the item count (a split: they include every created number), each body's
first line names the parent, and each issue's `dependencies/blocked_by` numbers equal its resolved
`blocked_by`. Fix gaps instead of reporting success; report the created numbers by plan id.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall