From nas-hr-skills
Converts NAS HR Confluence documentation into Jira issues. Takes a Confluence page URL or uses the current conversation context, parses it into Epics / Stories / Tasks, shows the proposed breakdown for confirmation, then creates the issues in Jira. NAS HR context (cloud ID, known pages, skip rules) is built in.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nas-hr-skills:confluence-docThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When this skill is invoked, execute the following steps **in order** without asking unnecessary questions upfront. Move fast — the goal is to go from doc to Jira board in one flow.
When this skill is invoked, execute the following steps in order without asking unnecessary questions upfront. Move fast — the goal is to go from doc to Jira board in one flow.
Check in this order:
/confluence-doc <URL or page ID>, use that directly."Using [page title] from the current conversation.""Which Confluence page do you want to convert to Jira? Paste the URL or page ID."Use getConfluencePage with contentFormat: "html" and cloudId: "49d0fe33-339b-4873-9930-c4c6250918ca" (NAS HR default cloud).
If the page URL is from a different Confluence instance, extract the cloud ID from the URL or ask the user.
If the page is already loaded in the current conversation context (content was fetched earlier in the session), skip the fetch and use what you have.
Analyze the page and propose a Jira issue breakdown. Use this mapping:
| Confluence Element | Jira Issue Type |
|---|---|
| The page itself | Epic — one Epic per page |
| Each numbered section (h2) | Story — one Story per major section |
| Each Feature N subsection (h3) | Task — one Task per feature |
| Validation Guardrails section | Tasks — one Task per guardrail rule |
| "Already Live" items | Skip — do not create issues for things already done |
NAS HR module pages follow this pattern:
Naming convention for issues:
[Module Name] — [Page Title][Module] — [Section Title][Module] — [Feature/Rule Name]Print the full proposed issue tree before creating anything. Format:
Epic: [title]
Story: [section title]
Task: [feature/rule]
Task: [feature/rule]
Story: [section title]
Task: [feature/rule]
...
Then ask:
"Does this breakdown look right? You can tell me to skip any section, merge stories, or change priorities. Type 'yes' to create all, or give me adjustments."
Before creating, confirm:
Medium. Ask only if the user has a preference.Create in this order:
For each issue, include in the description:
"Full spec: [Confluence page URL]"Use createJiraIssue for each item. Print confirmation as you go:
✅ Epic created: [key] [title]
✅ Story created: [key] [title]
✅ Task: [key] [title]
...
When all issues are created, print a final summary:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Confluence → Jira — Done
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Source: [Confluence page title + URL]
Project: [Jira project key]
Created:
1 Epic
X Stories
X Tasks
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
When working with NAS HR Performance module pages, apply these defaults automatically:
49d0fe33-339b-4873-9930-c4c6250918ca139952129139886594139984899npx claudepluginhub karimeltalawyy/nas-hr-skills --plugin nas-hr-skillsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.