Jira Scribe

This skill automates issue management in Jira Server/Data Center, verifying the existence of global issues and subtasks, and proposing their creation if they don't exist.

Since it works against a shared external system, it must never create issues, subtasks, or transition states without explicit user confirmation.

Language: Spanish Jira Instance

IMPORTANT: This skill is designed to work against a Spanish-language Jira Server/Data Center instance. This means:

• Issue types are in Spanish: Tarea, Subtarea, Historia, Error, Epic (Epic is typically kept in English even on Spanish Jira). Always use the localized issue type names matching the target Jira instance — do not use English types like Task, Sub-task, Story, Bug.
• Issue summaries and descriptions are written in Spanish: When creating issues or subtasks, write all user-facing text (summary, description, comments) in Spanish.
• Descriptions are required for new issues/subtasks: Always include a small, clear Spanish description explaining what needs to be done and why. Keep it concise, usually 1-3 sentences, and derive it from the user's request and available context.
• Transition names are in Spanish: Available transitions will have Spanish names like En Revisión, Terminado, En Progreso, To Do, etc. Always fetch and display the actual transition names from the API rather than assuming English names.
• All user interaction is in Spanish: Confirmations, summaries, and prompts shown to the user are in Spanish.
• JQL queries work in any language: JQL keywords (AND, OR, project =, summary ~) are always in English regardless of the Jira locale.

Required Configuration