import

Coco Import Skill

Import a tasks.md into the coco tracker and optionally create matching issues in the configured issue tracker.

When to Use

• Importing tasks as part of the coco pipeline
• Called by /coco:phase (Step D) or /coco:planning-session tactical
• When tasks.md exists in specs/{feature}/ and needs to be loaded into the tracker

Prerequisites: tasks.md must exist. If missing, use the tasks skill first.

Prerequisites

• Completed specs/{feature}/tasks.md with sub-phases and dependency info
• .coco/config.yaml exists with project configuration

Setup

1. Read .coco/config.yaml for project.specs_dir and issue_tracker config.
2. Determine the current feature by:
   • Checking the current git branch name
   • Strip the feature/ prefix (or whatever pr.branch.feature_prefix is) from the branch name
   • Looking for the matching directory in {specs_dir}/{stripped-name}/
   • Or from conversation context if a feature was recently discussed
3. Read {specs_dir}/{feature}/tasks.md (required). If missing, instruct user to use the tasks skill first.
4. Each tracker command is a separate Bash tool call: coco-tracker <command> [args]

Execution

Step 1: Parse tasks.md

Extract:

1. Feature name from the # Tasks: header
2. Sub-Phases -- each ## Sub-Phase N: section becomes a tracker task
3. Parallel markers -- [P] tasks within a sub-phase
4. Dependencies -- parse "Dependencies & Execution Order" section
5. **owns_files**: annotations -- file globs per sub-phase (optional)
6. **test_plan**: annotations -- FR-### IDs and levels per sub-phase (optional; none means "no tests, decided")

Step 2: Create Tracker Epic

coco-tracker epic-create "{feature-name}"

Step 3: Create Tracker Tasks (one per sub-phase)

IMPORTANT: All coco-tracker create arguments MUST be single-line. Never put literal newlines inside --description, --title, or --metadata values. Use semicolons or commas to separate items within a description. Put each command on one line (no \ continuations).