القائمة
Draft a Jira/GitHub/Linear ticket with testable AC (ADF-ready for Atlassian). Triggers: "write/draft/create a ticket/issue", or converting rough requirements into one.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Design/spec a new feature, component, or behavior change before any code. Triggers: "how should we…", "what's the best way", "let's build/add/create", "design", "plan", "spec". Outputs an approved spec → hands off to worker.
Implement code from a spec or requirement — plan, small steps, evidence-verified. Triggers: "build", "implement", "fix", "work on", "let's start", or any multi-step change after a spec.
Ultra-terse caveman replies — drops articles, filler, hedging, pleasantries. Keeps all technical content.
Root-cause a bug before fixing — reproduce, evidence, single hypothesis, minimal test. Use for any bug, test failure, build break, or unexpected behavior — especially when a "quick fix" feels obvious.
Simplify recently changed files — remove dead code, clearer names, less nesting — without behavior change. Triggers: "/polish", "clean up", "simplify", "tidy".
Design/spec a new feature, component, or behavior change before any code. Triggers: "how should we…", "what's the best way", "let's build/add/create", "design", "plan", "spec". Outputs an approved spec → hands off to worker.
| name | ticket-writer |
| description | Draft a Jira/GitHub/Linear ticket with testable AC (ADF-ready for Atlassian). Triggers: "write/draft/create a ticket/issue", or converting rough requirements into one. |
Turn rough requirements into clear, testable tickets / issues. Practical, deterministic, never post without explicit user approval.
Adapt to the target tracker. If issue-tracker MCP tools are available (jira_*, github_*, linear_*, mcp_*), prefer them for project info, issue types, labels, custom fields, and submission. Otherwise fall back to plain output for the user to paste.
For Jira/Confluence targets requiring ADF, load references/adf-format.md — full markdown→ADF conversion reference. Skip ADF entirely for GitHub Issues / Linear / plain markdown trackers.
Collect inputs. Confirm or ask for: title, type (Story/Bug/Task), goal (1–2 sentences), acceptance criteria, optional context/testing/implementation notes, board/project key, labels/custom fields. Ask only for what's missing.
Draft in markdown first.
# <Title>
## Type
<Story|Bug|Task>
## Goal
<1–2 sentences>
## Acceptance Criteria
1. <AC 1>
2. <AC 2>
## Additional Context
<optional>
## Testing Guidance
<optional>
## Implementation Notes
<optional>
Optional AC table (ADF). Three columns: AC / DEV / PM. One row per AC, DEV and PM cells empty. See references/adf-format.md for the table schema.
Approval gate. Confirm with the user: (a) content correct, (b) board/project, (c) approve creation. Proceed only when all three are yes.
Create payload. Convert to valid ADF, map fields, validate shape, submit, return ticket link + field summary. If submission fails with ADF errors, fix once and retry with an explanation.
Preview (markdown) + Missing Inputs.Final Fields + ADF JSON + Submission Result (ticket key/link).