m-sdd-tasks-to-issues

Migrate tasks from tasks.md to linked Jira tickets via Devin CLI.

2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill m-sdd-tasks-to-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m-sdd-tasks-to-issues
Source: https://github.com/mituso89/Spec-Driven-Development-toolkits/tree/main/m-sdd-tasks-to-issues
Command: npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill m-sdd-tasks-to-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically pushes tasks from the 'tasks.md' file to Jira as linked developer tickets, simplifying task management and keeping team members aligned during the development phase.

Core Features & Use Cases

  • Automated Task Migration: Push tasks from 'tasks.md' directly to Jira with links back to the original tasks for context.
  • Integration with Devin CLI: Leverages the Devin CLI infrastructure for seamless task-to-tickets migration.
  • Use Case: A feature development phase, where tasks are moved from a task document to Jira for better tracking and prioritization.

Quick Start

To convert tasks from the 'tasks.md' file into Jira tickets, execute 'm-sdd-tasks-to-issues' in Devin CLI.

Frequently Asked Questions about m-sdd-tasks-to-issues

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

FAQPage Schema
How do I migrate tasks from markdown to Jira issues?

You can automatically migrate tasks from a 'tasks.md' file to Jira issues by running this Skill within the Devin CLI environment. It translates markdown tasks into structured Jira tickets and links them back to the original document.

What is the best way to push feature tasks to Jira for development tracking?

The best way to push feature tasks to Jira for development tracking is using an automated task-to-issue migration tool. This Skill converts 'tasks.md' entries into linked Jira developer tickets to keep team members aligned.

Do I need Devin CLI to convert tasks.md files into Jira tickets?

Yes, you need the Devin CLI to convert 'tasks.md' files into Jira tickets. This Skill operates within the Devin CLI environment, using its scripting interface to execute the task-to-tickets migration.

Can I link migrated Jira issues back to my original markdown task list?

Yes, you can link migrated Jira issues back to your original markdown task list. The automated migration pushes tasks from 'tasks.md' to Jira while generating links back to the original tasks for context.

Does this task migration tool require any external dependencies?

No, this task migration tool does not require any external dependencies. It operates entirely within the Devin CLI environment using a scripting interface to parse markdown and format Jira issues.

When should I use an automated markdown to Jira issue converter?

You should use an automated markdown to Jira issue converter during feature development phases. It simplifies task management by moving prioritized tasks from a local markdown document into Jira for structured project tracking.