import

Import tasks.md into the Coco tracker as an epic with dependencies.

7|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/skullninja/coco-workflow --skill import-skullninja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: import
Source: https://github.com/skullninja/coco-workflow/tree/main/skills/import
Command: npx skills add https://github.com/skullninja/coco-workflow --skill import-skullninja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import a tasks.md into the Coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker. This automation saves time and ensures traceability between feature specs and issue tracking.

Core Features & Use Cases

  • Reads specs/{feature}/tasks.md and parses structure including sub-phases and dependencies.
  • Creates a tracker Epic and sub-phase tasks, applying correct dependencies and metadata.
  • Bridges to the configured issue tracker to create corresponding issues and associate them with tracker tasks.

Quick Start

Run the import skill to load specs/{feature}/tasks.md into Coco's tracker and generate matching issues in your configured tracker.

Frequently Asked Questions about import

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

FAQPage Schema
How do I import a tasks.md file into an issue tracker as an epic?

To import a tasks.md file, the skill parses sub-phases and dependencies from the file, creates a corresponding epic in the Coco tracker, and generates matching issues in your configured external issue tracker.

What do I need to set up before importing tasks.md into the Coco tracker?

You need a valid .coco/config.yaml file for tracker configuration and a present specs/{feature}/tasks.md file defining sub-phases and dependencies before running the import automation.

Can I automatically link imported tracker tasks to an external issue tracker?

Yes, the import process bridges to your configured issue tracker to create corresponding issues and associates them with the newly generated Coco tracker tasks using metadata.

How are task dependencies handled when importing a tasks.md file?

Dependencies defined in the tasks.md file are parsed and automatically applied to the created sub-phase tasks within the tracker epic to ensure accurate structural traceability.

Does the import skill work without a configured .coco/config.yaml file?

No, a valid .coco/config.yaml is strictly required. The automation relies on this configuration to execute coco-tracker commands for creating epics, tasks, and issue links.

What is the best way to load feature spec tasks into a tracker with dependencies?

Using the import skill parses the specs/{feature}/tasks.md structure, loads it into Coco's tracker as an epic with correct dependencies, and optionally bridges the data to an external tracker.