create-issue

Create structured Linear issues with predefined fields, types, and dependencies.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jamesc/skills --skill create-issue-jamesc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/jamesc/skills/tree/main/skills/create-issue
Command: npx skills add https://github.com/jamesc/skills --skill create-issue-jamesc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of issues in Linear by ensuring all necessary fields, types, and relationships are correctly defined, preventing common errors and improving workflow clarity.

Core Features & Use Cases

  • Structured Issue Creation: Define Epics, Features, Bugs, etc., with all required fields like Team, Assignee, Labels, and Estimates.
  • Dependency Management: Automatically set up "blocks" relationships between issues.
  • Use Case: When a new feature request comes in, use this Skill to create a Feature type issue, assign it to the correct team, add relevant labels (like agent-ready and class-system), and link it as a dependency to an existing Epic.

Quick Start

Use the create-issue skill to make a new feature called "Implement basic lexer token types" and set its area to parser.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I create structured Linear issues with predefined fields and dependencies?

To create structured Linear issues, you define predefined fields like Team, Assignee, Labels, and Estimates, then automatically set up blocks relationships for dependency management. This ensures consistent issue tracking and prevents common workflow errors.

What's the best way to manage task breakdown and dependencies in Linear?

Managing task breakdown and dependencies in Linear is best handled by creating structured issues with specific types like Epics or Features, then linking them via blocks relationships to map dependencies and maintain workflow clarity.

Do I need specific labeling conventions to track bugs and features in Linear?

Yes, tracking bugs and features in Linear requires adherence to specific labeling conventions for agent state, issue type, item area, and size estimates to ensure consistent issue tracking and accurate workflow processing.

Can I link a new feature request as a dependency to an existing Epic in Linear?

Yes, you can link a new feature request as a dependency to an existing Epic in Linear. The Skill sets up blocks relationships between issues, allowing you to assign the feature to a team and attach relevant labels.

How does dependency management work when creating issues in Linear?

Dependency management works by automatically setting up blocks relationships between newly created issues and existing ones. This facilitates task breakdown by ensuring structured issues are correctly linked within software development workflows.

What issue types can I define when creating bugs and features in Linear?

When creating bugs and features in Linear, you can define structured issue types such as Epics, Features, and Bugs. Each type requires specific fields including Team, Assignee, Labels, and Estimates for proper tracking.