skills.rest
brandtam
brandtamCOMMUNITY
Explore all skills by this author →
𝕏@brandtamGitHub

new-ticket

Create tickets via guided intake, wiki pages, and optional mirroring.

Updated Jul 20, 2026
Search Tags:#automation#workflow#wiki#backends#ticketing#intake#mirroring
One-click install
npx skills add https://github.com/brandtam/rubber-ducky --skill new-ticket
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-ticket
Source: https://github.com/brandtam/rubber-ducky/tree/main/src/skills/new-ticket
Command: npx skills add https://github.com/brandtam/rubber-ducky --skill new-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating new work tickets manually is error-prone and hard to scale. This Skill automates the end-to-end workflow: it handles intake setup, creates the corresponding wiki page, and optionally mirrors the ticket to downstream backends, all in a safe, auditable sequence.

Core Features & Use Cases

  • Guided intake orchestration: prompts to configure backends, projects, and mirroring before any external writes.
  • Wiki-first ticket creation: creates the local wiki task page and defers external writes until user confirmation.
  • Mirror-ready workflow: supports optional mirroring to a secondary backend after intake and wiki creation.
  • Audit trails: progress persistence across sessions and explicit logging for investigation.

Quick Start

Describe a task you found and I will guide you through intake setup, wiki creation, and optional mirroring to downstream backends.

Frequently Asked Questions about new-ticket

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

FAQPage Schema
How do I automate ticket creation from informal ideas using a guided intake flow?▼

Ticket creation automation handles intake configuration, generates wiki task pages, and optionally mirrors tickets to downstream backends. It applies a guided flow to ensure safe, auditable ticket creation from informal ideas.

Can I mirror new tickets to a secondary backend after creating them?▼

Yes, mirroring to downstream backends is supported. After intake configuration and local wiki page creation, the workflow optionally mirrors the ticket to a secondary backend, but only after user confirmation is received.

Do I need a configured workspace to set up automated ticket intake?▼

Yes, a configured workspace with intake and optionally mirror backends is required. The workflow coordinates with a ticket-writer sub-agent and wiki task pages, needing this environment to ensure safe, auditable ticket creation.

What is the best way to ensure auditable ticket creation and track progress across sessions?▼

Auditable ticket creation is ensured through progress persistence across sessions and explicit logging. The wiki-first approach defers external backend writes until user confirmation, providing a safe sequence for investigation.

Why does the workflow create a wiki task page before writing to external ticketing backends?▼

Creating a wiki task page first defers external writes until user confirmation. This wiki-first approach ensures ticket creation is safe, auditable, and reviewable locally before any data is committed to downstream backends.

Related Skills

Explore More Product & Management Skills→
brandtambrandtam
2

push

Push wiki task pages to external ticket backends with confirmation gating and audit logging.

Community
Advanced
duc01226duc01226
7

entity-event-handler

Implement entity event handlers triggering side effects after CRUD operations.

Community
Advanced
sakthiramsakthiram

multi-agent

Coordinate specialized agents to complete complex tasks with persistent sessions.

Community
Advanced
hoainam183hoainam183

tmux

Manage persistent tmux sessions, windows, and panes via shell scripts.

Community
Intermediate