work-items-to-linear

To create Linear issues from markdown, this skill reads a work-items.md file, validates dependencies, and publishes each plan slice as an individual issue in a single target team via the Linear MCP server. It maps in-file references to native Linear blocked-by relationships after creation.

Yes, you can convert plan dependencies into native Linear blocked-by relationships. The skill reads 'Depends on' references from the work-items.md file and links them as native issue dependencies after all target issues are created in Linear.

Yes, you need a configured Linear MCP server to publish work items. The skill requires this server to read team states, labels, and members, and to execute the API calls for creating issues and linking dependencies within the target team.

The best way to manage project blockers when migrating work items to Linear is using a pre-broken-down work-items.md file. The skill validates these blockers during publishing and automatically converts them into native Linear blocked-by relationships for consistent dependency tracking.

To assign existing Linear team labels and states to imported work items, the skill resolves the target team's configuration and applies optional project, parent nesting, initial state, and labels to fit team conventions during issue creation.

When you rerun issue creation for the same work-items.md file, the skill annotates created issues with Linear IDs in the source headings. This audit-friendly behavior ensures the run resumes correctly without duplicating previously published issues.