Jira Custom Context

This documentation was generated with the assistance of AI. Please report any inaccuracies.

Gather any additional, organization- or repository-specific context for a Jira ticket being drafted by iru-create-jira-ticket, beyond what that skill already asks generically. This skill only exists to be extended in place — out of the box it asks one generic, optional question.

Purpose

iru-create-jira-ticket already asks for the context every ticket needs regardless of organization: purpose, linked URLs/attached files, related tickets, an optional epic, a due date, and an importance level. Some organizations need more before a ticket is genuinely ready to file — a required custom field, a specific team or component, a customer/account name, an affected environment, a compliance or security classification, and so on. iru-jira-custom-context is the explicit customization point for that: rather than growing iru-create-jira-ticket itself with organization-specific questions that wouldn’t apply to every installation of this catalog, that skill delegates here during its own context-gathering step. Out of the box this skill defines no organization-specific questions yet — it asks a single generic, optional catch-all and returns whatever the user provides. Its value comes entirely from being extended, in place, with the fixed-choice questions, open-ended questions, or automated lookups a given organization’s Jira workflow actually needs — one file, edited per repository/organization, instead of a fork of the whole ticket-creation flow.

Purpose group

Ticket Intake

Invocation

/iru-jira-custom-context
/iru-jira-custom-context <task purpose>

Primarily called programmatically by iru-create-jira-ticket’s own context-gathering step (`Skill({skill: "iru-jira-custom-context", args: "<purpose>"})) rather than run standalone by a person — though the slash-command form works directly too, e.g. to test an extension in isolation.

Inputs

Argument Required Description Default

task purpose

No

The task’s stated purpose, normally forwarded by `iru-create-jira-ticket’s Step 3 — used to judge which of this skill’s defined questions are actually relevant to this task, skipping ones that plainly don’t apply.

None — with no argument, every defined question (or, out of the box, the single generic catch-all) is asked unconditionally.

Outputs

  • No file or code changes — this skill only gathers information and reports it back as plain text.

  • Out of the box: the answer to a single generic, optional question ("is there any other context this ticket should carry — team/component ownership, a customer or account, an affected environment, compliance/security considerations, or anything else specific to how your organization tracks Jira tickets?"), or an explicit note that nothing was provided if the user declined it.

  • Once extended: whatever additional fixed-choice answers, free-text answers, or automated-lookup results the added questions produce.

  • A short list of label/value pairs (e.g. "Team: Payments", "Environment: production") returned to the caller, clear enough for `iru-create-jira-ticket’s own drafting step to fold each one in directly — either as its own bullet in the ticket description, or as a matching Jira field/label/component if one exists for it.

Execution flow

flowchart TD A[Start /iru-jira-custom-context] --> B{Purpose argument given?} B -- yes --> C["Judge which defined questions\nare relevant to this task"] B -- no --> D["Ask every defined question\n(out of the box: just the\ngeneric catch-all)"] C --> D D --> E["Ask the relevant question(s)\n(AskUserQuestion for fixed choices,\nplain text for open-ended,\nor an automated lookup)"] E --> F["Return gathered context as\nlabel/value pairs, or an explicit\n'nothing provided' note"]

Dependencies

Invokes

None — iru-jira-custom-context does not call any other skill in this catalog; any extension added to it may use AskUserQuestion, ToolSearch/MCP tools, or plain reads directly rather than delegating further.

Invoked by

  • Create Jira Ticket — Step 4, during its own additional-context gathering, passing the task’s stated purpose so this skill can judge which of its (extended) questions apply. A nothing provided response is never a blocker — iru-create-jira-ticket proceeds with just its own generic context in that case.

Related agents

None — iru-jira-custom-context does not spawn any agent.

Source

SKILL.md on GitHub — the file this page was generated from.