create-issues
/create-issues
Use when the roadmap and ready specs in docs/design/ should become issues. Creates the milestones and issues (GitHub, GitLab, local files, Jira, Linear or Redmine) from the roadmap and the ready specs, but only after showing the plan and getting the user's yes; nothing is created before. Idempotent - existing issues and milestones are skipped, nothing is closed or labeled - so it can be run again at any stage, for example after every design studio session.
- Author
- AlbertoRiorda95 ↗
- Repository
- agent-team ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the roadmap and ready specs in docs/design/ should become issues. Creates the milestones and issues (GitHub, GitLab, local files, Jira, Linear or Redmine) from the roadmap and the ready specs, but only after showing the plan and getting the user's yes; nothing is created before. Idempotent - existing issues and milestones are skipped, nothing is closed or labeled - so it can be run again at any stage, for example after every design studio session.
Arguments
/create-issues [--team]
Original author description
Use when the roadmap and ready specs in docs/design/ should become issues. Creates the milestones and issues (GitHub, GitLab, local files, Jira, Linear or Redmine) from the roadmap and the ready specs, but only after showing the plan and getting the user's yes; nothing is created before. Idempotent - existing issues and milestones are skipped, nothing is closed or labeled - so it can be run again at any stage, for example after every design studio session.
How it works
- 1. Preconditions
- 2. Pick the script
- 3. Show the plan
- 4. Create
- What this never does
- In Codex or OpenCode
SKILL.md preview
---
name: create-issues
description: Use when the roadmap and ready specs in docs/design/ should become issues. Creates the milestones and issues (GitHub, GitLab, local files, Jira, Linear or Redmine) from the roadmap and the ready specs, but only after showing the plan and getting the user's yes; nothing is created before. Idempotent - existing issues and milestones are skipped, nothing is closed or labeled - so it can be run again at any stage, for example after every design studio session.
argument-hint: "[--team]"
---
Create the issues of the project's roadmap and ready specs. Talk to the user in
their language.
## 1. Preconditions
- A reachable tracker: run `python3 <scripts>/tracker.py check` (scripts
folder chosen as in step 2). By default the tracker is GitHub or GitLab, from
the Git remote, with an authenticated `gh` or `glab`; `.agent-team/config.json`
can choose local files, Jira, Linear or Redmine (see `docs/general/trackers.md`,
or `${CLAUDE_PLUGIN_ROOT}/template/docs/general/trackers.md`). If the check
fails, say what to do (push the repository, `gh auth login`, set the
tracker's environment variables) and stop.
- At least `docs/design/project.md` with a `## Roadmap`, or one spec with
`ready: yes`. Otherwise there is nothing to create: suggest
`/agent-team:design-studio`.
## 2. Pick the script
Use `scripts/create-issues.py` from the project if it exists together with
`scripts/agentteam/`, otherwise the plugin's copy
`${CLAUDE_PLUGIN_ROOT}/template/scripts/create-issues.py`. Run it
from the project root. If the project's copy differs from the plugin's, the
project may be on an older template: mention `/agent-team:upgrade`, but use the
project's copy unless the user says otherwise.
## 3. Show the plan
Run `python3 <script> --dry-run` (add `--team` if the user passed it) and
summarize the output for the user:
- milestones to create and those that exist;
- issues to create, per milestone, with their dependencies;
- issues that exist or are tracked by the `Issue` column, and those that would
get a milestone they do not have;
- issues created earlier that are no longer in the plan (the script never
closes them: the user decides).
If a spec says "Team task possible: yes", ask whether the user wants one
`agent:team` issue for it (`--team`, one PR) or one issue per task.
If the output reports milestone issues from the old layout ("M0 · ..." parent
issues), explain that milestones are now native and offer
`python3 <script> --migrate --dry-run` first, then `--migrate` on the user's yes.
## 4. Create
Only after the user says yes, run the same command without `--dry-run`. Report
what was created and linked. Remind the user that no labels were added: an
agent starts only when they add `agent:<role>` to a task issue, in the order
of the dependencies, or with `/agent-team:dispatch`.
## What this never does
It never closes, relabels or rewrites an issue; the only change to an existing
issue is giving a milestone to one that has none. Running it twice creates
nothing new.
## In Codex or OpenCode
`${CLAUDE_PLUGIN_ROOT}` is the plugin folder in Claude Code. In Codex or
OpenCode, which load these skills from `~/.agents/skills/`, use the folder where
the agent-team repository is cloned (`$AGENT_TEAM_HOME`) instead.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · AlbertoRiorda95/agent-team | 90 | MIT |
| afonsoft/skills | 100 | MIT |
| useful-toys/slf4j-toys | 98 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 6be5d1528efe (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100split-issue
Use when one or more issues are too big for one agent and should become tasks. Splits one issue, several (12 15 18) or a milestone (--milestone M1) into task issues, one per role (GitHub, GitLab, local files, Jira, Linear or Redmine) - shows one overview, and creates the… - 100issues
File GitHub milestones and issues from a roadmap, a phase file or a spec — one milestone per phase, one issue per task or slice — then write the issue numbers back into the docs so /wf:feature and /wf:autopilot can name branches and close issues. Safe to re-run: reconciles… - 100issues-and-roadmap
Use when planning work on a GitHub repo, such as milestones, a roadmap, a project board or sizes, when writing an issue someone else should be able to pick up, including good first issues and "writers wanted", when setting issue types, sub-issues or blocked-by links, or when… - 90dev10x:project-scope
Scope a multi-ticket project with milestones, blocking relationships, and tracker integration. Accepts a parent ticket URL/ID or free-text description and creates the full project structure in Linear, JIRA, or GitHub Issues. TRIGGER when: scoping a multi-ticket project with… - 100prd-to-issues
Turn a finished Product Requirements Document (PRD) into GitHub milestones and complete, scored issues with typed dependencies and Execution blocks. Use for "file the issues from the PRD", "/prd-to-issues", or "break this into GitHub issues". Stage 4 of the new-app-pipeline. - 100roadmap
Generates ROADMAP.md from project milestones, issues, and boards (GitHub, GitLab, or Bitbucket). Structures content with mission statement, current milestone progress, upcoming milestones, and community involvement section. Use when creating or updating a project roadmap.