Create Jira Epics and stories for NFRs from YAML data.
npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill nfr-jira-epic
Please help me install this Agent Skill. Skill: nfr-jira-epic Source: https://github.com/DavidROliverBA/ArchitectKB/tree/main/.claude/skills/nfr-jira-epic Command: npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill nfr-jira-epic
This Skill automates the creation of Jira Epics and Stories for Non-Functional Requirements (NFRs), transforming compliance tracking into actionable sprint tasks.
nfr-reference.yaml, nfr-evidence-rules.yaml) as the single source of truth for NFRs.Create a Jira Epic and associated stories for NFR compliance for the ERPSystem, CS1 tier, covering all NFR types, in the ARCH project.
High-intent search queries and answers about installing and using this skill.
You can automate Jira issue creation by parsing NFR data from YAML files to generate a parent Epic and individual linked stories for each applicable Non-Functional Requirement. This converts abstract compliance needs into concrete development tasks for sprint planning.
Turn NFR compliance tracking into actionable sprint tasks by generating a Jira Epic with associated stories based on system, tier, and type. It uses YAML reference files as the source of truth to structure abstract requirements into trackable work.
Yes, you can use YAML files like nfr-reference.yaml and nfr-evidence-rules.yaml as the single source of truth. The Skill parses this NFR data and utilizes Atlassian MCP tools to generate the Jira Epic and link associated stories automatically.
Yes, NFR Jira epic generation requires specific system, tier, and type inputs to filter applicable Non-Functional Requirements. Providing these parameters ensures the created stories accurately reflect the compliance needs for your defined system.
The best way to structure non-functional requirements for sprint planning is creating a parent Jira Epic with individual stories for each applicable NFR. This transforms compliance tracking into actionable development tasks linked directly to sprint workflows.
NFR compliance tasks may not appear as linked Jira stories if the YAML data is improperly formatted or the Atlassian MCP tools fail to link them to the parent Epic. Ensure your system, tier, and type parameters match the YAML reference files.
DavidROliverBAGenerate NFR tables for HLDs filtered by criticality and project type.
falconntPlan and track hierarchical Kanban work items with YAML frontmatter metadata and states.
BigdropsManage Jira tickets, sprints, and workflows via natural language.
dasheck0Convert Jira Epics into testable user stories with acceptance criteria.