What problem does it solve? Turning a conversation into a tracked work item requires manually choosing a platform, formatting a title and body, applying labels, linking related tickets, and keeping local records in sync. This Skill automates that entire flow so a ticket is created on the correct remote platform with consistent conventions. ## Core Features & Use Cases - Multi-platform creation: Resolves the target platform from project preferences or the git remote, then creates the ticket via GitHub (gh issue create) or Jira (connected tools or acli). - Conventional titles and labels: Renders the ticket title with describe-change.mjs using the work type and scope, and maps type/scope to GitHub labels via .meta/label-map.json. - Relationships and artifacts: Applies parent, blocked-by, and blocking relationships, persists the branch-to-ticket association, and saves ticket and plan artifacts locally with standardized frontmatter. - Use Case: While discussing a bug in a coding session, ask the agent to file it; the Skill creates a GitHub issue with the right labels, links it as blocked by another issue, and saves a local ticket artifact. ## Quick Start Ask the agent to create a ticket for the problem we just discussed, optionally with --parent or --blocked-by references.