issue-create
/issue-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.
- Author
- znorris ↗
- Repository
- claude-marketplace ↗
- Licence
- MIT
- Last repository change
- 14.07.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 14.07.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
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.
Triggers from the description
Original author description
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.
How it works
- Investigation Phase
- Issue Document Structure
- Quality Checklist
- Principles
- Output
SKILL.md preview
--- name: issue-create description: 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. --- As a Staff Software Engineer, investigate the provided error, bug report, or feature request and produce a well-defined issue document. Focus on thoroughly understanding and documenting the **problem** - solution planning comes later. Your goal: Create an issue so clear that any developer could understand the problem completely and then plan a solution. ## Investigation Phase Understand the problem before documenting it: ### For Bugs/Errors - **Trace the symptom**: Follow code paths, collect logs and stack traces - **Identify root cause**: What code or condition triggers this? - **Assess scope**: Isolated or systemic? What's the blast radius? - **Measure impact**: Users affected, severity, frequency ### For Features/Improvements - **Map current state**: How does it work today? What's missing? - **Define the goal**: What user problem does this solve? - **Note constraints**: Technical, business, or resource limitations ### General - Explore relevant areas of the codebase - Check documentation for involved systems - Look for related issues or past attempts ## Issue Document Structure ```markdown # [Descriptive Title] Specific title describing the problem (not the solution). Bad: "Fix login" | Good: "Login fails silently when SSO session expires mid-authentication" ## Summary 2-3 sentences: What's the problem, who's affected, and why does it matter? ## Problem Description ### Current Behavior - Observable symptoms - Error messages or logs (quote relevant excerpts) - Reproduction steps (for bugs) - Root cause, if identified ### Expected Behavior What should happen instead. Be specific. ### Impact - Who is affected (users, systems, teams) - Severity (data loss, degraded experience, inconvenience) - Frequency (constant, intermittent, edge case) ## Context What a developer needs to understand this problem: - Relevant code: `[filename.ext:line](path#Lline)` - Architecture or system components involved - Dependencies or integrations - Key constraints ## Scope ### This Issue Addresses - Specific problem(s) to solve - Clear boundaries ### Out of Scope - Related concerns for separate issues ## Acceptance Criteria How we know this is done: - [ ] Specific, testable criterion - [ ] Another measurable outcome - [ ] Relevant tests pass Keep criteria focused on **outcomes**, not implementation details. ## Additional Context - Related issues or PRs - Customer reports or support tickets - Screenshots, logs, or examples --- **Signals:** - Severity: [Low | Medium | High | Critical] - Complexity Estimate: [Small | Medium | Large | XL] ``` ## Quality Checklist Before finalizing: - [ ] Problem is clear: Could a developer explain this to someone else? - [ ] Evidence-based: Symptoms and root cause supported by code/logs? - [ ] Properly scoped: One cohesive problem, not multiple issues bundled? - [ ] Impact articulated: The "why it matters" is explicit? - [ ] Testable criteria: Each acceptance criterion is unambiguous? - [ ] No premature solutioning: Describes the problem, not a predetermined fix? ## Principles **Focus on the problem.** Define *what* needs solving and *why*. **Capture context.** Include enough detail that someone unfamiliar can understand without asking questions. **Be evidence-driven.** Reference specific code, quote actual errors, cite real data. **Scope ruthlessly.** A focused issue gets solved. A sprawling issue becomes backlog. ## Output Save as `issue-brief-problem-description.md` in the appropriate location (project root, `.github/issues/`, or as specified).
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · znorris/claude-marketplace | 100 | MIT |
| awinogradov/code-assistants | 100 | MIT |
| modelcontextprotocol/servers | 95 | MIT |
| p2p2sp/viber | 91 | MIT |
| nightgauge/nightgauge | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version d73967bacb32 (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
- 100define
Use when a new feature request, bug report, or work request needs requirements defined before implementation - 90issue
Create a GitHub issue, or update an existing issue's description, with a body that captures the problem and why it matters, in the chalk voice. Use when the user says "open an issue", "file a bug", "raise an issue", "create an issue", "file a ticket", "write up a feature… - 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. - 100ticket-authoring
Write complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub… - 9004-issue-create
Create an issue in the configured ticketing tool. Use when the user wants to file a bug, open an issue, or report a problem. Not for committing, opening a pull request, or commenting on an existing issue. - 100gh-create-issue
Use when asked to file, report, open, or raise a GitHub issue for a bug, feature, audit, or review finding.