scaffold-sub-issues

To convert markdown feature plans into Linear sub-issues, use this Skill to parse PLAN-*.md files and generate a proposed parent ticket with ordered sub-issues. It captures acceptance criteria and dependency mappings before creating anything in Linear.

Yes, you can map blocks and blocked-by dependencies when creating Linear issues. The Skill parses sub-task relationships from your plan format and builds corresponding dependency edges to maintain execution order across repositories.

Scaffolding Linear issues does not automatically create missing repository labels. The Skill performs missing repo label discovery and requires explicit user confirmation before writing any new labels or issues to ensure safe workflow kickoff.

The best way to structure a Linear parent issue is to embed the full plan markdown into the parent description and apply the union of all repo labels used by the sub-tasks. This preserves acceptance criteria detail and scope.

To preview Linear sub-issues before writing them, the Skill presents a confirmation gate showing the proposed parent issue, ordered sub-tasks, and dependency mappings. No Linear MCP tools are executed until you explicitly approve the preview.

The Skill supports both strict and loose plan formats. It parses sub-tasks and acceptance criteria from either formatting style to generate tracker-ready tickets, ensuring flexible integration for various project planning workflows.