As a HyperShift contributor, I want clear documentation on how to create JIRA Epics and Stories using the MCP tools, so that I can avoid common pitfalls and create properly linked issues on the first attempt.

Context:
The .cursor/rules/create-jira-items.mdc guide lacked specific instructions for:
1. Required Epic Name field (customfield_12311141) when creating Epics in CNTRLPLANE
2. Linking Epics to parent issues (OCPSTRAT/Features) using the parent field
3. Proper method for linking Stories to Epics using customfield_12311140 via jira_update_issue
4. Why jira_link_to_epic tool is unreliable and should not be used

This task documents the learnings from creating CNTRLPLANE-1549 (Epic) and CNTRLPLANE-1550-1554 (Stories). Additionally, CNTRLPLANE-1549 was initially created without a parent link to OCPSTRAT-2437, requiring manual correction.

Tasks:

• Document Epic Name field requirement (customfield_12311141)
• Document parent link setting for Epics linking to OCPSTRAT/Features
• Document Epic Link field usage (customfield_12311140)
• Add guidance on using jira_update_issue instead of jira_link_to_epic
• Include code examples for Epic parent linking and Story epic linking
• Clarify that links must be set after creation, not during

Acceptance Criteria:

• Documentation clearly explains Epic creation requirements including Epic Name field
• Documentation shows how to link Epics to parent OCPSTRAT/Feature issues
• Documentation shows correct method for linking Stories to Epics
• Code examples provided for both Epic parent linking and Story epic linking
• Future JIRA issue creation attempts avoid the documented pitfalls