create-ticket

Create persistent work tickets with assignees, priorities, and goal or project links.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill create-ticket-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-ticket
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/create-ticket
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill create-ticket-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the chaos of ad-hoc discussions by converting an ongoing topic into a persistent ticket with an assignee, priority, and a durable thread of updates.

Core Features & Use Cases

  • Creates persistent tickets: Establishes a durable work item (thread) with status tracking and ownership.
  • Routes to the right agent: Sets an assignee agent so the appropriate heartbeat inbox can pick it up.
  • Links work to goals/projects: Optionally associates the ticket with a goal_id or project_id for better organization and reporting.
  • Enables follow-up via comments/mentions: Adds comments that can trigger wake triggers in other agents.

Quick Start

Use create-ticket when you want to open a new persistent issue like “Open a ticket for Cliente X’s latency complaint, set priority to high, and assign it to zara-cs.”

Frequently Asked Questions about create-ticket

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

FAQPage Schema
How do I turn a conversation into a persistent work ticket with an assignee and priority?

Persistent ticketing converts ongoing discussions into durable work items by establishing a thread with status tracking, ownership, and priority. This eliminates ad-hoc chaos by preserving source agent and session provenance for durable state across time.

How do I create a persistent ticket for issue management and route it to an agent inbox?

You create a persistent ticket by issuing a POST request to /api/tickets via evo client, specifying the assignee agent and priority. This establishes a durable work item routed to the appropriate heartbeat inbox for pickup and status tracking.

Can I link a persistent work ticket to an existing goal or project for better organization?

Yes, you can optionally associate the persistent work ticket with a goal_id or project_id during creation. This links the durable thread to broader objectives for better organization and reporting across workflows.

Does this issue management approach work for workflows requiring durable state across time instead of ephemeral chats?

Yes, this issue management approach is designed for workflows requiring durable state across time, threaded discussion, and inbox-based routing. It does not fit ephemeral chats or deterministic routines that lack persistent state.

How do I enable follow-up comments and mentions on a persistent work ticket after creation?

You enable follow-up by adding comments to the persistent work ticket, which can trigger wake triggers in other assigned agents. This maintains a durable thread of updates for ongoing issue management across time.

What format does the ticket creation return for UI binding?

The ticket creation returns JSON suitable for UI binding while preserving source_agent and source_session_id provenance. This format supports durable state and threaded discussion for the created work item.