Run Jira
Productivityrun-jiraRun Jira is an Agent Skill for productivity published in the DataDog/datadog-agent repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Fetch a Jira issue and propose an implementation plan based on codebase analysis
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/DataDog/datadog-agent/blob/HEAD/.claude/skills/run-jira/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/run-jira, 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.
Fetch the Jira issue $ARGUMENTS from the Datadog Atlassian instance and use it as the basis for a codebase analysis and implementation proposal.
Step 1: Gather Jira issue data
Use the Atlassian MCP tools to fetch the issue. Only request the fields you need to avoid huge responses:
- Call
mcp__atlassian__getJiraIssuewith:cloudId:datadoghq.atlassian.netissueIdOrKey:$ARGUMENTSfields:["summary", "description", "status", "assignee", "issuetype", "comment", "priority"]
- Extract the title (summary), description, status, assignee, and comments from the response.
If the issue cannot be found, stop and inform the user.
Step 2: Summarize the issue
Present a clear summary of the Jira issue:
- Key: $ARGUMENTS
- Title: the issue summary
- Status: current status
- Assignee: who is assigned
- Description: the full description
- Comments: any relevant context or discussion from comments
- Link: https://datadoghq.atlassian.net/browse/$ARGUMENTS
Step 3: Fetch linked resources
Scan the issue description and comments for links to external resources and fetch them for additional context:
- Datadog notebooks / postmortems (
app.datadoghq.com/notebook/<id>): usemcp__datadog-mcp__get_datadog_notebookwith the notebook ID - GitHub PRs (
github.com/.../pull/<number>): usegh pr view <number>via Bash - GitLab commits/pipelines or other URLs: use
WebFetchif accessible
This step is critical — linked resources often contain the root cause analysis, timelines, and technical details that the Jira description alone does not capture.
Step 4: Analyze the codebase
Based on the issue requirements and linked resources, explore the codebase to understand:
- Which files and packages are relevant
- Existing patterns and conventions that should be followed
- Dependencies and potential impacts
Use Glob, Grep, and Read tools extensively. For broad exploration, use the Task tool with subagent_type=Explore.
Step 5: Propose an implementation
Enter plan mode with EnterPlanMode and write a detailed implementation plan that includes:
- A breakdown of the changes needed, organized by file
- Any new files that need to be created
- Test strategy
- Potential risks or open questions
Wait for user approval before implementing.