القائمة
Create and update local ticket markdown drafts for Jira, GitHub, or generic trackers using consistent YAML frontmatter, Obsidian-first links, and stable-context sections.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Configure a resilient KDE Plasma home workstation so terminal sessions, desktop windows, browser tabs, and selected app workspaces recover after accidental closes, logout/login, reboot, or crash as much as Linux realistically allows. Use this skill whenever the user wants a sustainable desktop/home system, worries about losing workflow after reboot, wants KDE session restore, browser tab restore, tmux terminal persistence, or wants to reproduce this setup on another KDE Plasma machine.
Orchestrate the user's custom skill ecosystem. Use when creating, improving, classifying, installing, documenting, publishing, or maintaining user-owned skills and skill repositories; when recovering from installed skill artifact edits; when designing skill subscriptions; or when deciding where reusable skill knowledge belongs.
Recover from unmet user expectations and make the appropriate future behavior durable. Use whenever a user says they expected something else, asks why an action was missed, says "I expected you to…" or "you should have…", or indicates that an immediate fix also needs to prevent recurrence.
Bootstrap implementation planning when the user explicitly wants to start, plan, implement, or work on a work item. Do not use this skill for simple fetch, view, read, or summary requests.
| name | ticket-markdown |
| description | Create and update local ticket markdown drafts for Jira, GitHub, or generic trackers using consistent YAML frontmatter, Obsidian-first links, and stable-context sections. |
Use this skill to keep local ticket notes consistent, portable, and easy to navigate.
Resolve note root in this order:
system=jira and ~/Documents/Jira exists, use ~/Documents/Jira.system=github and ~/Documents/GitHub exists, use ~/Documents/GitHub.~/Documents/Tickets/<system-or-generic>.<system-or-generic> should be jira, github, or generic.
<ROOT>/<TICKET-ID>/<TICKET-ID>.md<ROOT>/<TICKET-ID>/<TICKET-ID>-<short-name>.md<ROOT>/CURRENT_DRAFT.mdCreate parent folders when missing.
Start every ticket note with YAML frontmatter:
---
summary: <ticket summary>
system: jira
ticket_id: TICKET-123
native_ref: PROJ-123
external_link: https://example.com/tickets/123
project: project-or-repo
issue_type: Story
priority: Major
parent: "[[TICKET-100]]"
children:
- "[[TICKET-124]]"
related:
- "[[TICKET-150]]"
---
Rules:
~ for unknown values.parent, children, and related only when known.When citing another ticket inline and a URL is available, use both forms side by side:
[[TICKET-123]] [TICKET-123](https://example.com/tickets/123)
When URL is unknown, use wikilink only:
[[TICKET-123]]
When importing from remote tickets or issue bodies:
TBD and ask the user to confirm before treating them as requirements.