jira-pe-tickets
Skill0 starsChanged 8 months agoNo licenceView on GitHub
Create and structure Jira issues on the iDC Holdings Platform Engineering (PE) board — epics, tasks under epics, and subtasks under tasks — with the team's labelling conventions, hierarchy rules, and what-not-to-ticket guidance. Use this skill whenever the user says "create a jira ticket", "new epic in PE", "task under PE-N", "subtask under PE-N", "add to the PE board", "ticket in jira", "PE board", or otherwise asks to put work onto the PE Jira project. Also use when reviewing or labelling existing PE issues. **Load this skill before calling any `mcp__claude_ai_Atlassian__*` tool against project PE** — the conventions encoded here change the call shape, not just the metadata around it. The common failure when this skill is skipped: defaulting to issueType "Story" (PE has no Story), creating Subtasks without a Task parent (orphans), labels outside the five-category taxonomy, and pre-creating future-phase tickets that clutter the kanban — each of which the team then has to clean up. Encodes the cloudId, project key, hierarchy semantics, the five-category label taxonomy (domain / source-system / activity / wait-state / cross-cutting), the five labelling rules, and the no-future-phase-clutter convention. Do NOT trigger on bare "ticket" or "track this" — those collide with the local `tickets/` directory pattern and the `ticket-creator` skill, which writes markdown ticket files rather than Jira issues. Do NOT trigger for non-PE Jira projects.
In this repository5 other files it gives its agents.
- context-handoffSkill
- granola-tool-routingSkill
- meeting-prepSkill
- skill-creatorSkill
- skills-repoSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

