jit-migrate

Name: jit-migrate
Availability: InStock
Author: erankavija

Migrate project planning artifacts to JIT issue tracker with dependency DAGs.

Updated Nov 26, 2025

Search Tags:#project planning #migration #dependency analysis #issue tracking #JIT

Ready to run

npx skills add https://github.com/erankavija/just-in-time --skill jit-migrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jit-migrate
Source: https://github.com/erankavija/just-in-time/tree/main/.claude/skills/jit-migrate
Command: npx skills add https://github.com/erankavija/just-in-time --skill jit-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jit, mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of migrating project plans to the JIT issue tracker, simplifying the transition from legacy planning tools to JIT.

Core Features & Use Cases

Project Planning Migration: Scan planning artifacts and automatically extract work items and dependency DAGs.
JIT Integration: Populate the .jit/ directory with issues and dependencies for easy tracking and management within JIT.
Use Case: For a project with complex workflows, use this Skill to migrate existing planning documents and workflows into JIT, streamlining the tracking of tasks and milestones.

Quick Start

Run the jit-migrate skill to scan and migrate your project's planning artifacts to JIT.

Frequently Asked Questions about jit-migrate

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

FAQPage Schema

How do I migrate project planning artifacts to the JIT issue tracker?▼

To migrate project planning artifacts to the JIT issue tracker, you scan planning documents and inline TODO/FIXME comments to automatically extract work items and build dependency DAGs. This process generates a JSON plan for review and populates the .jit/ directory.

What is the best way to extract work items and dependency DAGs from existing planning documents?▼

The best way to extract work items and dependency DAGs from planning documents is by automating the scan of planning artifacts and inline TODO/FIXME comments. This automatically builds the dependency DAGs and outputs a structured JSON plan for review.

Do I need the JIT CLI and MCP tools to automate issue tracker migration?▼

Yes, automating issue tracker migration requires the JIT CLI and MCP tools. These dependencies are essential for scanning planning artifacts, extracting work items, building dependency DAGs, and populating the .jit/ directory with issues.

Can I scan inline TODO and FIXME comments to generate JIT issues?▼

Yes, you can scan inline TODO and FIXME comments to generate JIT issues. The migration process supports scanning these inline comments alongside planning artifacts to automatically extract work items and map dependency DAGs into a JSON plan.

What limitations exist when migrating complex workflows to JIT using automation?▼

A key limitation when migrating complex workflows to JIT is that the automation outputs a JSON plan for review rather than executing changes directly. Users must manually review the extracted work items and dependency DAGs before finalizing the migration into the .jit/ directory.