jira-plan

Convert session context into Jira subtasks under a specified parent.

3|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/open-horizon-labs/bottle --skill jira-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-plan
Source: https://github.com/open-horizon-labs/bottle/tree/main/.claude-plugin/plugins/miranda/skills/jira-plan
Command: npx skills add https://github.com/open-horizon-labs/bottle --skill jira-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The jira-plan skill converts grounding and session context into concrete Jira subtasks, reducing manual planning time and ensuring consistent traceability.

Core Features & Use Cases

  • Generates Jira subtasks from both session context and fresh investigations.
  • Produces structured task descriptions, acceptance criteria, and contextual notes to enable immediate work.
  • Supports dependency links between subtasks and updates the session file with created subtasks.

Quick Start

Run /jira-plan PROJ-100 "auth-refactor" to create subtasks under a parent issue, or run with an existing session: /jira-plan PROJ-100 auth-refactor, using the session file at .oh/auth-refactor.md for context

Frequently Asked Questions about jira-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate Jira subtasks from session context?

To generate Jira subtasks automatically, provide a parent issue ID and a session context file. The skill translates grounding context into structured, actionable work items under the specified parent.

What is the best way to create structured Jira subtasks from an investigation?

Using an automated planning skill is the best way to create structured subtasks from investigations. It generates task descriptions, acceptance criteria, and dependency links directly in Jira.

Does Jira subtask generation work with an existing session file?

Yes, Jira subtask generation works with existing session files. You reference a file like .oh/auth-refactor.md to supply the context needed to create structured subtasks.

Do I need a Jira MCP connection to create subtasks automatically?

Yes, you need a Jira MCP connection. The skill ensures Jira MCP availability before creating subtasks under a parent issue and updating the session context file.

Can I link dependencies between newly created Jira subtasks?

Yes, you can link dependencies. The planning process supports dependency links between generated subtasks and updates the session context file with the created work items.