valec3/my-code-arsenal/jira-issues
Claude Code and agent skill by valec3/my-code-arsenal
- community
Checking that the SKILL.md file is still in the repository.
Create and validate Jira backlog entries (Epics, User Stories, Tasks) for the node-jira-bot hierarchical provisioner. Covers the JSON schema, field reference, priority values, and multi-project structure. Trigger: When creating or editing backlog.json, defining Jira issues (épicas, historias de usuario, tareas), or preparing a Jira project backlog for provisioning.
Install
npx vskill@latest install valec3/my-code-arsenal/jira-issuesSKILL.md
The same SKILL.md was published earlier as valec3/my-code-arsenal/jira-issues.
When to Use
- Creating or editing a
backlog.jsonfile for the node-jira-bot - User asks to "crear épicas", "agregar historias", "definir tareas" for Jira
- User mentions
backlog.json, "provisionar Jira", or "cascada de backlog" - User wants to know what fields are available for each issue type
- User needs to validate their backlog structure before provisioning
Critical Patterns
1. Hierarchy (MANDATORY — do NOT deviate)
- Epic: Top-level container. Has
stories[]. Never hastasks[]directly. - Story (Historia de Usuario): Child of Epic. Has
tasks[]. Can havestoryPoints. - Task: Child of Story. Leaf node. Standard Jira "Task" type, NOT "Sub-task".
NEVER nest tasks under epics directly. The hierarchy is strict: Epic contains Stories, Stories contain Tasks.
2. Issue Types (Jira)
| JSON level | Jira issue type | Config variable | Default | |
|---|---|---|---|---|
| Epic | Epic | JIRA_EPIC_TYPE | Epic | |
| Story | Story | JIRA_STORY_TYPE | Story | |
| Task | Task | JIRA_TASK_TYPE | Task |
Task is NOT Sub-task. The bot creates standard Jira Tasks linked to their parent Story via the parent field. If your Jira project uses a custom name for Tasks, set JIRA_TASK_TYPE in your project's .env.
3. Multi-Project Structure
Each project has its own folder under projects/<name>/:
The root .env contains shared credentials (JIRA_HOST, JIRA_USER_EMAIL, JIRA_API_TOKEN). The project .env overrides/adds JIRA_PROJECT_KEY.
Backlog JSON Schema
Field Reference
| Field | Level | Required | Type | Example | |
|---|---|---|---|---|---|
summary | Epic, Story, Task | ✅ Yes | string | "ÉPICA: Auth y Seguridad" | |
description | Epic, Story, Task | No | string | "Implementar flujo completo..." | |
priority | Epic, Story, Task | No | string | "Highest", "High", "Medium", "Low", "Lowest" | |
stories | Epic | No | BacklogStory[] | [{...}, {...}] | |
tasks | Story | No | BacklogTask[] | [{...}, {...}] | |
storyPoints | Story | No | number | 5, 8, 13 |
Priority Values
Use the exact Jira priority names for your instance. Common values:
| Priority | Use for | |
|---|---|---|
"Highest" | Critical path, MVP must-have, blockers | |
"High" | Important but not blocking | |
"Medium" | Standard priority | |
"Low" | Nice to have | |
"Lowest" | Backlog filler, future consideration |
Verify your Jira instance's exact priority names. Some instances use different labels (e.g., "Critical" instead of "Highest"). The bot passes these as-is to the Jira API.
Naming Conventions
- Epic summary: Prefix with
ÉPICA:orEPIC:→"ÉPICA: Core - Carga de Archivos" - Story summary: Prefix with
HU:orUS:→"HU: Registro con correo y contraseña" - Task summary: Prefix with
[BACKEND],[FRONTEND],[DB],[DEVOPS]→"[BACKEND] Endpoint POST /api/auth/login"or useTarea:→"Tarea: Diseñar formulario UI"
These prefixes are conventions, not enforced by the bot. They help with readability in Jira.
Commands
Resources
- Minimal template: See assets/backlog-minimal.json — one epic, one story, one task
- Full example: See assets/backlog-full.json — multiple epics with stories and tasks
- Multi-project guide: See the project README.md
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingnode-jira-bot/.agent/skills/jira-issues/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/valec3/my-code-arsenal/jira-issues)