issue-authoring

Create GitHub and Jira issue tickets with validation and duplicate detection.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill issue-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-authoring
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/issue-tracking/issue-authoring
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill issue-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces consistent, high-quality issue creation so trackers do not fill with vague titles, missing acceptance criteria, broken cross-references, or duplicate tickets.

Core Features & Use Cases

  • Formatting and required fields enforcement: Ensures titles follow standards and descriptions include Context, Acceptance Criteria, Technical Notes, and References.
  • Validation and safety checks: Queries label and assignee existence, verifies issue identifiers via issue-verify, and applies hard blocks for broken cross-references.
  • Duplicate detection and workflow guidance: Searches for existing issues before creation and prompts to comment on duplicates instead of creating new tickets.
  • Adapters and integration: Works with configured tracker adapters (shipped: GitHub, Jira) and requires adapter create_issue operations for final submission.
  • Use Case: Convert a conversation or bug report into a tracked, triage-ready issue with validated labels, assignee, and acceptance criteria.

Quick Start

Create a new issue by providing a concise title and a description with Context, Acceptance Criteria, Technical Notes, and References, then run duplicate detection, validate labels and assignee, and call the configured adapter to create the ticket.

Frequently Asked Questions about issue-authoring

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

FAQPage Schema
How do I create well-structured GitHub issues with required fields like acceptance criteria?

To create well-structured GitHub issues, this Skill enforces title standards and requires descriptions to include Context, Acceptance Criteria, Technical Notes, and References before submission. It ensures tickets are triage-ready by validating required fields during issue creation.

What is the best way to check for duplicate issues in Jira before creating a new ticket?

The best way to check for duplicate issues is using automated duplicate detection. This Skill searches existing Jira tickets before creation and prompts you to comment on duplicates instead of generating redundant issue tracker tickets.

Can I validate labels and assignees when filing bug reports through automated workflows?

Yes, you can validate labels and assignees when filing bug reports. This Skill queries label and assignee existence against configured tracker adapters and blocks creation if validation fails, ensuring accurate ticket metadata.

How do I convert a discussion into a tracked issue with acceptance criteria?

You can convert a discussion into a tracked issue by providing a concise title and a description with Context and Acceptance Criteria. This Skill then runs duplicate detection, validates metadata, and calls the adapter to create the ticket.

Do I need configured GitHub or Jira adapters to use automated issue creation?

Yes, you need configured GitHub or Jira adapters to use automated issue creation. This Skill requires adapter create_issue operations for final ticket submission and invokes issue-verify for cross-reference checks during validation.

Why does issue creation get blocked by broken cross-references?

Issue creation gets blocked by broken cross-references to prevent invalid tickets. This Skill applies hard blocks for broken cross-references after verifying issue identifiers via issue-verify, ensuring all linked tracker tickets exist.