Jira Create
Productivityjira-createJira Create is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
This skill should be used when creating JIRA epics, stories, and tasks from code files or descriptions. It analyzes the provided input, determines the appropriate issue hierarchy, and creates issues with comprehensive quality requirements including test-first development and documentation.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/integration/jira-create-codyswanngt-lisa-3/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/jira-create, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Create JIRA Issues from $ARGUMENTS
Analyze the provided file(s) and create a comprehensive JIRA hierarchy with all mandatory quality gates.
Process
- Analyze: Read $ARGUMENTS to understand scope
- Determine Structure:
- Epic needed if: multiple features, major changes, >3 related files
- Direct tasks if: bug fix, single file, minor change
- Create Issues with hierarchy:
Epic → User Story → Tasks (test, implement, document, cleanup)
Mandatory for Every Code Issue
Test-First: Write tests before implementation Quality Gates: All tests/checks must pass, no SonarCloud violations Documentation: Check existing, update/create new, remove obsolete Feature Flags: All features behind flags with lifecycle plan Cleanup: Remove temporary code, scripts, dev configs
Issue Requirements
Each issue must clearly communicate to:
- Coding Assistants: Implementation requirements
- Developers: Technical approach
- Stakeholders: Business value
Default project: SE (override via arguments) Exclude unless requested: migration plans, performance tests
Execute the analysis and create the complete JIRA structure with proper parent-child relationships.