Skip to content
Skills Library
Management & product · Planning

forge-create-issue

/forge-create-issue

Collaboratively plan and create well-structured Issues through interactive discussion (GitHub, markdown plan/ folder, or other providers). Use when the user wants to create an Issue, report a bug, or scope out work that is already understood — use forge-shape first when the idea is still vague.

Repository
forge ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Collaboratively plan and create well-structured Issues through interactive discussion (GitHub, markdown plan/ folder, or other providers). Use when the user wants to create an Issue, report a bug, or scope out work that is already understood — use forge-shape first when the idea is still vague.

Original author description

Collaboratively plan and create well-structured Issues through interactive discussion (GitHub, markdown plan/ folder, or other providers). Use when the user wants to create an Issue, report a bug, or scope out work that is already understood — use forge-shape first when the idea is still vague.

How it works

  1. Input
  2. Process
  3. Guidelines
  4. Related Skills
  5. Example Usage
Original SKILL.md headings · 113 lines, 569 words
SKILL.md preview
---
name: forge-create-issue
description: Collaboratively plan and create well-structured Issues through interactive discussion (GitHub, markdown plan/ folder, or other providers). Use when the user wants to create an Issue, report a bug, or scope out work that is already understood — use forge-shape first when the idea is still vague.
disable-model-invocation: true
allowed-tools: Read, Edit, Write, Bash, Grep, Glob, WebSearch, AskUserQuestion
---

# Create Issue

Collaboratively plan and create well-structured Issues through interactive discussion. The Issue is created in the project's Issue tracker — see [issue-operations](_shared/issue-operations.md) for provider detection.

## Input

The Issue idea or problem description: $ARGUMENTS

Optional: `-- <additional context>` for execution guidance.

If no argument is provided, ask the user what they'd like to create an Issue for.

## Process

### Step 1: Research the Codebase

Parse the user's input, then explore the relevant code before asking anything:
- Find related existing implementations and patterns
- Identify integration points and potential reuse

Verify external dependencies are accessible if relevant — flag broken ones before proceeding.

### Step 2: Clarify

Use AskUserQuestion to gather what the code can't answer:
- **Problem context** — what triggered this, who's affected, current vs desired behavior
- **Success criteria** — how will we know this is done
- **Constraints** — technical limitations, dependencies

### Step 3: Present Alternative Approaches

**Skip this step** if the input already contains a chosen approach with rationale — the decision was already made through deliberate analysis. Proceed directly to Step 4.

Otherwise, present the structurally distinct approaches you found — usually two to four — rather than a single recommendation; the choice belongs to the user.

For each approach:
- One-line summary
- How it works (brief)
- Pros and cons
- Relative complexity (Low / Medium / High)
- Key files affected

Let the user choose or combine approaches via AskUserQuestion.

### Step 4: Assess Scope

Evaluate if this should be one Issue or multiple.

**Split when:** distinct deliverables, different codebase areas, parallelizable work, or effort exceeds 1-2 days.

**Keep together when:** tightly coupled changes or splitting adds coordination overhead.

When splitting, slice **vertically** — each Issue is a thin end-to-end path (see [vertical-slicing](_shared/vertical-slicing.md)). Classify each as **AFK** or **HITL** (see [afk-vs-hitl.md](references/afk-vs-hitl.md)). Order by dependency.

If splitting makes sense, offer: single Issue, multiple linked Issues, or epic with sub-issues.

### Step 5: Draft the Issue

**Title:** Use conventional commit format — `<type>(<scope>): <description>`

**Labels:** Discover what labels exist before applying any — see [issue-operations](_shared/issue-operations.md). Apply at least one type label and relevant area labels.

**Body structure:**

```markdown
## Summary
[1-2 sentences]

**Execution mode:** [AFK | HITL] <!-- markdown provider: use the `mode` frontmatter field instead -->

## Problem / Motivation
[Why this needs to exist]

## Proposed Solution
[Chosen approach with implementation details]

### Alternatives Considered
[Other approaches and why they weren't chosen]

### Implementation Constraints
[When applicable: preferred libraries, config locations, patterns to follow, external dependencies]

## Acceptance Criteria
- [ ] [Specific, testable criteria]
- [ ] Tests added/updated
- [ ] Documentation updated (if applicable)
```

### Step 6: Review and Create

Present the draft to the user and iterate until satisfied (use AskUserQuestion for approve/revise decisions). Then create the Issue using the project's Issue tracker — see [issue-operations](_shared/issue-operations.md) for provider-specific mechanics, including epics with sub-issues.

Share the Issue reference. Suggest using `forge-implement` to start implementation.

## Guidelines

- **Be curious** — challenge assumptions, ask "why" and "what if"
- **Don't over-specify** — leave room for implementer judgment
- **No time estimates in the Issue** — the Step 4 effort heuristic is for deciding splits, not for the Issue body

## Related Skills

**Next step:** Use `forge-implement` to implement the Issue.

## Example Usage

```
/forge-create-issue add dark mode support
/forge-create-issue add dark mode support -- keep it to a single Issue
/forge-create-issue
```
Files in this package (3)
  • SKILL.md 4 KB
  • _shared 1 KB
  • references/afk-vs-hitl.md 2 KB

Versions

The database has no other skills named forge-create-issue.

Database snapshot: 13.11.2026 · package version f47292277b9f (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

  • 100create-github-issue
    Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
  • 100forge-shape
    Shape a vague idea into a clear plan through codebase investigation and convergent one-at-a-time questioning. Use when the user has a rough idea or problem that needs specifying before issue creation.
  • 91issue-create
    Creates a GitHub issue from the project's issue form templates. Use when the user asks to open an issue, not to fix a bug.
  • 90issue-create
    Create well-structured GitHub issues with SDLC metadata, project board sync, and optional parent/child linking. Use when filing a new issue or epic that the pipeline will pick up, so it lands board-ready with correct labels and links. User-invoked: the user types `/nightgauge:issue-create`.
  • 100issue-tracking
    Create, manage, and track issues in GitHub, Linear, or GitLab. Use when the user asks to "create an issue", "file a bug", "check issues", "update a ticket", "create an epic", or anything about issue/ticket management.
  • 100issue-create
    Investigate a bug or define requirements for a feature, then produce a structured issue document. Use when the user asks to "create an issue", "write a ticket", "investigate a bug", "define a feature", or needs a well-structured problem statement for their tracker.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.