task-import

Import tasks from JSON files into a project management system.

20|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/lukas-grigis/ralphctl --skill task-import
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-import
Source: https://github.com/lukas-grigis/ralphctl/tree/main/.claude/skills/task-import
Command: npx skills add https://github.com/lukas-grigis/ralphctl --skill task-import

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of adding multiple tasks to your project by allowing you to import them from a structured JSON file, ensuring consistency and saving manual entry time.

Core Features & Use Cases

  • JSON Import: Accepts a JSON array of task objects, each with defined fields.
  • Dependency Mapping: Supports blockedBy field to establish task dependencies during import.
  • Ticket Linking: Allows associating imported tasks with existing tickets via ticketId.
  • Use Case: You have a list of development tasks generated by a planning tool, formatted as JSON. Use this Skill to quickly import them into your current sprint, complete with dependencies and ticket links.

Quick Start

Use the task-import skill to import tasks from the file 'new_tasks.json'.

Frequently Asked Questions about task-import

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

FAQPage Schema
How do I import tasks from a JSON file into a project management system?

To import tasks from JSON, provide a structured JSON array of task objects containing fields for task descriptions, steps, and inter-task dependencies. The skill validates the task structure and cross-references any specified ticket IDs against existing project data before creating the tasks.

Can I define task dependencies when importing a JSON task list?

Yes, you can define task dependencies during JSON import by using the 'blockedBy' field within each task object. This maps inter-task relationships directly, establishing the exact workflow dependencies required for your project management setup.

Does the task import process support linking to existing project tickets?

Yes, the task import process supports linking to existing project tickets via the 'ticketId' field. It cross-references these ticket IDs against your current project data to ensure accurate association and validation during the task creation workflow.

What JSON structure is needed to bulk import tasks and their step definitions?

The JSON structure required is an array of task objects, where each object handles task creation, description, and step definition. The skill validates this structure to ensure consistency and properly formats the imported task data before entry.

What happens if a ticket ID in my imported JSON does not match existing project data?

The skill validates task structure and cross-references ticket IDs against existing project data during import. If a ticket ID does not match, the validation process will identify the discrepancy to prevent incorrect linking and maintain project data integrity.