Menü
Create GitHub issues from a phase planning doc
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Analyze an existing project and populate godark.yaml with modules, codegen, CI, and env configuration
Create a project roadmap and GitHub milestones through conversation
Generate a practical overview with real-world examples for a completed roadmap phase
Create a detailed planning doc for a roadmap phase
Generate scenario spec files for a phase or individual issue
Compress and organize CLAUDE.md into a minimal directory of pointers
| name | godark-create-issues |
| description | Create GitHub issues from a phase planning doc |
| argument-hint | <phase-number> |
| disable-model-invocation | true |
Read a planning doc and create GitHub issues with the proper structure for agent consumption. Update the planning doc and roadmap with assigned issue numbers.
Read config — Read godark.yaml to get the repo, roadmap_path
(default: docs/ROADMAP.md), and planning_dir (default: docs/planning/).
Find the planning doc — Use the phase number argument to locate the
planning doc by globbing <planning_dir>/phase-<N>-*.md. If no match is
found, report an error. Parse the file to extract the milestone name and
each issue's title, description, acceptance criteria, test cases, and
dependencies.
Check existing issues — Run gh issue list --milestone "<Milestone>" --repo <repo> --state all --limit 200 to see what already exists. Match by
title to avoid creating duplicates.
Confirm with user — Present the list of issues, noting:
Ask the user to confirm before creating or updating anything.
Create or update issues — For each new issue, run:
gh issue create --title "<Title>" --body "<body>" \
--milestone "<Milestone>" --label "phase-N" --repo <repo>
The issue body must include:
## Description section## Acceptance criteria section with - [ ] checkboxes## Test cases section with - **Name**: entries**Blocked by**: #N line if the issue has dependencies (using the real
issue numbers from GitHub, not the planning doc order)For existing issues the user chose to update, run:
gh issue edit <number> --body "<body>" --repo <repo>
Update the planning doc — Replace ## Issue: <Title> headings with
## Issue N: <Title> using the assigned GitHub issue numbers.
Update the roadmap — In docs/ROADMAP.md, add or update the **Issues**
line for this phase with the issue number range (e.g., **Issues**: #14–#17).
Print summary — List each created issue with its number, title, and URL.
godark vet issues validates:
## Description, ## Acceptance criteria (with checkboxes), ## Test cases
(with named entries).**Blocked by**: #N format with real issue numbers.phase-2) to every issue./godark-create-scenarios.