Run any Skill in Manus with one click

Get Started

godark-create-issues

Stars16

Forks1

UpdatedMarch 27, 2026 at 00:03

Create GitHub issues from a phase planning doc

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

peter-stratton

peter-stratton/dark-factory

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	godark-create-issues
description	Create GitHub issues from a phase planning doc
argument-hint	<phase-number>
disable-model-invocation	true

Create Issues

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.

Steps

Read config — Read godark.yaml to get the repo, roadmap_path (default: docs/roadmap/), 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:
- Which issues are new (will be created)
- Which already exist and whether their body differs from the planning doc (offer to update)
- Dependency ordering
- The milestone and labels that will be applied
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 the phase file (e.g. docs/roadmap/phase-30.md), add or update the **Issues** line with the issue number range (e.g., **Issues**: #14-#17).
Print summary — List each created issue with its number, title, and URL.

Rules

Never create duplicate issues — always check existing issues first.
Issue bodies must follow the exact format that godark vet issues validates: ## Description, ## Acceptance criteria (with checkboxes), ## Test cases (with named entries).
Dependencies must use **Blocked by**: #N format with real issue numbers.
If a dependency hasn't been created yet (e.g., within the same batch), create dependency issues first, then use their numbers.
Apply the phase label (e.g., phase-2) to every issue.
All issues must be assigned to the correct milestone.
Do not modify scenario specs — that is handled by /godark-create-scenarios.
If some issues already exist and some are new, only create the new ones and update the planning doc with all numbers (existing + new).

CRITICAL — Next step

When this skill completes, suggest the user run /godark-create-scenarios next. Do NOT attempt to create scenario specs yourself — the skill contains specific formatting, structure, and coverage directives that must be followed exactly. The full workflow order is:

/godark-create-milestone
/godark-create-planning-doc
/godark-create-issues (this skill)
/godark-create-scenarios

More from this repository

same repository

godark-configure-project

peter-stratton/dark-factory

Analyze an existing project and populate godark.yaml with modules, codegen, CI, and env configuration

2026-04-0316

godark-create-scenarios

peter-stratton/dark-factory

Generate scenario spec files for a phase or individual issue

2026-03-2716

godark-create-milestone

peter-stratton/dark-factory

Create a project roadmap and GitHub milestones through conversation

2026-03-2716

godark-create-phase-overview

peter-stratton/dark-factory

Generate a practical overview with real-world examples for a completed roadmap phase

2026-03-2716

godark-create-planning-doc

peter-stratton/dark-factory

Create a detailed planning doc for a roadmap phase

2026-03-2716

godark-harness-claude-md

peter-stratton/dark-factory

Compress and organize CLAUDE.md into a minimal directory of pointers

2026-03-2716

Create Issues

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.

Steps

Read config — Read godark.yaml to get the repo, roadmap_path (default: docs/roadmap/), 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:

Which issues are new (will be created)
Which already exist and whether their body differs from the planning doc (offer to update)
Dependency ordering
The milestone and labels that will be applied

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 the phase file (e.g. docs/roadmap/phase-30.md), add or update the **Issues** line with the issue number range (e.g., **Issues**: #14-#17).

Print summary — List each created issue with its number, title, and URL.

Rules

Never create duplicate issues — always check existing issues first.

Issue bodies must follow the exact format that godark vet issues validates: ## Description, ## Acceptance criteria (with checkboxes), ## Test cases (with named entries).

Dependencies must use **Blocked by**: #N format with real issue numbers.

If a dependency hasn't been created yet (e.g., within the same batch), create dependency issues first, then use their numbers.

Apply the phase label (e.g., phase-2) to every issue.

All issues must be assigned to the correct milestone.

Do not modify scenario specs — that is handled by /godark-create-scenarios.

If some issues already exist and some are new, only create the new ones and update the planning doc with all numbers (existing + new).

CRITICAL — Next step

/godark-create-milestone

/godark-create-planning-doc

/godark-create-issues (this skill)

/godark-create-scenarios