home / skills / codyswanngt / lisa / jira-create

jira-create skill

safe

This skill creates a complete Jira epic, stories, and tasks from code inputs, enforcing test-first, documentation, and quality gates.

npx playbooks add skill codyswanngt/lisa --skill jira-create

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.7 KB

---
name: jira-create
description: 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.
allowed-tools: ["Read", "Glob", "LS", "mcp__atlassian__createJiraIssue", "mcp__atlassian__getVisibleJiraProjects", "mcp__atlassian__getJiraProjectIssueTypesMetadata", "mcp__atlassian__getAccessibleAtlassianResources"]
---

# Create JIRA Issues from $ARGUMENTS

Analyze the provided file(s) and create a comprehensive JIRA hierarchy with all mandatory quality gates.

## Process

1. **Analyze**: Read $ARGUMENTS to understand scope
2. **Determine Structure**:
   - Epic needed if: multiple features, major changes, >3 related files
   - Direct tasks if: bug fix, single file, minor change
3. **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.

Overview

This skill generates complete JIRA epics, stories, and tasks from code files or textual descriptions. It analyzes scope, infers the correct issue hierarchy, and creates issues that embed mandatory quality requirements such as test-first development, documentation, feature flags, and cleanup steps. The default project is SE unless overridden.

How this skill works

The skill reads provided files or descriptions to determine scope and relatedness (single file vs. multi-feature). It applies rules to decide whether an Epic is required and then emits a structured hierarchy: Epic → User Story → Tasks. Each created issue includes concrete acceptance criteria, test-first instructions, documentation actions, feature flag requirements, and cleanup tasks.

When to use it

Turning a multi-file change or set of related features into a tracked Epic and child issues
Converting a single-file bug or minor change into a direct task with clear tests and docs
Preparing work for AI-assisted coding so coding assistants have explicit implementation and test instructions
Onboarding new engineers with pre-scoped stories that include quality gates
When you need consistent, policy-compliant issue templates for feature rollout and rollback

Best practices

Provide relevant files or a concise description to improve scope accuracy
Accept the default Epic rule for >3 related files or multiple features, override only when necessary
Keep test-first requirement: list unit/integration tests to author before implementation
Specify feature flag lifecycle: rollout criteria, monitoring, and removal timeline
Include stakeholder value and technical approach fields in every issue to align engineers and non-technical reviewers

Example use cases

Create an Epic and user stories for a multi-module feature change across front-end and back-end files
Generate a single task for a bug fix in one TypeScript file with prewritten test cases and docs updates
Break a new API work item into story and tasks: tests, implementation, docs, feature-flag enablement, and cleanup
Convert a design doc or plain description into an actionable Jira hierarchy with acceptance criteria and CI checks

FAQ

Can I override the default project or exclude items?

Yes. The default project is SE but you can override via arguments. You can also request exclusion of migration plans or performance tests.

What mandatory gates are added to each code issue?

Every code issue includes test-first instructions, quality gates (all tests and checks must pass, no SonarCloud violations), documentation updates, feature-flag requirements, and a cleanup task.