skills.rest
rjskene
rjskeneCOMMUNITY
Explore all skills by this author →
GitHub

create-issues

Convert brainstormed code-change ideas into GitHub issues after user confirmation.

Updated Apr 10, 2026
Search Tags:#brainstorming#github#project planning#workflow orchestration#issue creation#safety guardrails#tracker rollup
One-click install
npx skills add https://github.com/rjskene/pipeline --skill create-issues-rjskene
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-issues
Source: https://github.com/rjskene/pipeline/tree/main/skills/create-issues
Command: npx skills add https://github.com/rjskene/pipeline --skill create-issues-rjskene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps users brainstorm and refine changes without directly modifying code, then converts decisions into actionable GitHub issues.

Core Features & Use Cases

  • Brainstorm-to-issues workflow: Guides discussion through scope and confirmation before creating issues.
  • Grouping and tracker rollups: Detects overlaps with existing tracker issues and can propose grouped rollups to reduce fragmentation.
  • Read-only safety guardrails: Enforces no source edits and uses GitHub issue tools only, including duplication checks.

Quick Start

Use the /pipeline:create-issues skill and tell it what you want to improve or fix, and it will help you confirm and create one or more GitHub issues for the plan.

Frequently Asked Questions about create-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn brainstormed ideas into GitHub issues?▼

To turn brainstormed ideas into GitHub issues, this workflow guides scope discussion, detects duplicate tracker issues, and creates formatted GitHub issues via GitHub tooling after explicit user confirmation.

What's the best way to avoid duplicate GitHub issues during project planning?▼

To avoid duplicate GitHub issues during project planning, this workflow performs duplicate detection against existing tracker issues and proposes grouped rollups to reduce fragmentation before creating new entries.

Can I create GitHub issues without modifying my source code?▼

You can create GitHub issues without modifying source code because this workflow enforces read-only execution constraints and safety guardrails, using only GitHub issue tooling rather than direct code edits.

Does this issue creation workflow require YAML configuration?▼

This issue creation workflow requires YAML-defined discovery metadata to operate, ensuring structured workflow orchestration when transforming brainstormed code-change ideas into actionable GitHub issues.

What types of changes are suitable for an issue-driven workflow?▼

Suitable changes for an issue-driven workflow include feature proposals, refactors, bug reports, and improvement suggestions where actual code implementation should be deferred until the GitHub issue is created and approved.

Related Skills

Explore More Software Engineering Skills→
vitalliumvitallium
10

ce-brainstorm

Generate a structured requirements document with YAML frontmatter from collaborative brainstorming.

Community
Advanced
DonTiziDonTizi
2

implement

Translate GitHub issue specs into incremental implementation plans with tests and commits.

Community
Advanced
cmbayscmbays
1

backlog-auditor

Automates GitHub issue backlog hygiene by detecting stale, duplicate, and unlabeled issues.

Community
Advanced
thydethyde

github-issues

Create, update, and search GitHub issues with LucidData templates and labels.

Community
Intermediate