Work Items To Linear

Project Context

• personal config directory: !bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"
• project .han/config.md: !cat .han/config.md 2>/dev/null || echo ""

As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md probe supplies content, apply it per config-rule.md, which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.

Work Items to Linear Issues

Take an already-broken-down work-items.md file (produced by /plan-work-items) and publish each slice as a Linear issue in a single target team.

The breakdown work — drafting slices, assigning symbolic IDs, specifying dependencies, inventorying references — has already been done upstream. This skill validates the format, confirms the target against the live team, creates one issue per slice through the Linear MCP server, links the within-file dependencies as native "blocked by" relations, and reports.

Rules

• Every slice posts into one Linear team. This skill does not split work across teams or repos. A work-items.md that names multiple code repos still produces issues in the single team you name; the repo prose is informational only.
• Dependencies are within-file only. Every SYM named in a Depends on line must resolve to another slice in the same file. A Depends on that names an unknown SYM, names the slice itself, or forms a cycle is a format error to surface for repair, never published.
• Symbolic-ID prefixes: accept whatever the input uses. Any uppercase prefix shape is valid (W-N, V2-N, EV-N, ...); the prefix has no effect on team placement.
• Resolve against the live team before writing. Read the team's real workflow states, labels, Projects, and members, and resolve every named option against them before creating any issue. Nothing is assigned, categorized, grouped, or moved unless asked.
• No issue types. Linear has no issue-type concept. The skill never asks for or sets one. Categorization is via the team's real labels, chosen by the user.
• Every slice issue MUST carry the reference artifacts an implementer needs — API/event contracts, design references, schema docs, runbooks, ADRs, coding standards. Full include/exclude list in references/reference-artifact-inventory.md.
• NEVER include process artifacts in issue descriptions. Excluded: iteration histories, decision logs, review findings, team findings, facilitation summaries, gap analyses, and anything under an artifacts/ subfolder of the plan that is not a contract or design reference.
• No image upload or embedding. Design references are carried as links, not uploaded into Linear. See references/linear-issue-template.md.

Process

0. Linear MCP preflight (hard requirement)

This skill cannot run without a configured and connected Linear MCP server. Confirm it is reachable by calling mcp__plugin_linear_linear__list_teams. If the tool is unavailable, the call errors, or no workspace is accessible, stop immediately and tell the user the skill requires the Linear MCP server to be installed, configured, and authenticated. Do not fall back to any other publishing target.

If the integration exposes more than one Linear workspace, note which are available and confirm which one to use before resolving the team.

1. Locate the work-items file

If the path is not provided, ask for it. The input is a single work-items.md produced by /plan-work-items. Read it. Its format is described in references/work-items-file-format.md.

2. Gather the run options

Read these from the arguments and conversation; do not guess defaults the user did not ask for:

• Target team — --team <name or key>. Required. If absent, ask for it in Step 3.
• Project — --project <name or ID>. Optional. Groups every created issue under a Linear Project.
• Parent — --parent <issue id>. Optional. Nests every created issue as a sub-issue under the named parent.
• State — --state <name>. Optional; defaults to the team's initial/default workflow state.
• Labels — --label <name>, repeatable. Optional; resolved against the team's real labels.
• Assignee — --assignee <name/email/me>. Optional; defaults to unassigned.

3. Resolve the target against the live team

Resolve everything concretely now so failures surface before any issue is created. This is a strict, fail-before-write sequence:

• Team (required). Confirm the named team with mcp__plugin_linear_linear__list_teams. If none is named, ask. If the name matches more than one team, present the matches and ask which one. Do not proceed without exactly one team.
• Read the team's configuration with mcp__plugin_linear_linear__list_issue_statuses, mcp__plugin_linear_linear__list_issue_labels, and mcp__plugin_linear_linear__list_users. These reads are independent and may run together.
• State. If --state was given, match it against the team's real states. The default is the team's initial/default state. If a named state does not exist, present the team's real states and ask.
• Labels. If --labels were given, match each against the team's labels. When categorization was not specified, present the team's real labels and let the user choose one, several, or none. If the team defines no labels, say so and proceed without categorization.
• Assignee. If named, resolve it with mcp__plugin_linear_linear__get_user: the literal token me resolves to the authenticated Linear identity, and a name or email resolves to that member. If unset, leave issues unassigned. The creator is recorded automatically by Linear as the authenticated user; never set it.
• Project (optional). Resolve a named Project at workspace scope with mcp__plugin_linear_linear__list_projects (Projects are not strictly team-scoped), and confirm the target team participates in it.
• Parent (optional). Resolve a named parent issue with mcp__plugin_linear_linear__get_issue and confirm it belongs to the target team.

For any option that cannot be resolved, do not silently drop or invent it. Distinguish "no such option exists in the team" (present the team's real options for that field) from "it exists but belongs to a different team" (name that team). Ask the user to pick or correct before continuing.

4. Validate the format with evidence-based repair

Check the work-items file against the invariants in references/work-items-file-format.md and references/linear-issue-template.md:

• Heading shape. Every slice heading matches ## <SYM-N> — <title> with an em-dash separator (already-published headings annotated as ## <SYM-N> (<LINEAR-ID>) — <title> are valid too).
• Depends on line. Literal bold marker **Depends on.**, trailing period, None. or comma-separated SYMs.
• Within-file blockers. Every SYM named in a Depends on line resolves to another slice in this file. A SYM that names the slice itself (self-block) or that forms a dependency cycle with other slices is a format error.
• References block. Present whenever the slice consumes an HTTP endpoint, event payload, design frame, ADR, coding standard, or other named artifact.
• No process artifacts. No links to iteration histories, decision logs, review findings, team findings, facilitation summaries, gap analyses, or anything under an artifacts/ subfolder that is not a contract or design reference.

When a check fails, attempt evidence-based repair. Pull evidence from the source work-items.md, the parent plan referenced in its intro, the feature spec in the same folder, sibling files in the plan folder, and the relevant repo's ADRs / coding standards / docs:

• Malformed heading — propose the corrected shape based on surrounding text. Cite the line number.
• Missing Depends on line — propose None. if no blockers are evident. Cite the absence.
• Unknown-SYM, self-block, or cycle — propose the correct in-file SYM (if a typo is evident), or None., or breaking the cycle. Cite the SYM list this file defines.
• Missing References bullet for an HTTP-consuming or UI slice — propose the contract section or design frame from the parent plan or feature spec. Cite the anchor.
• Process-artifact link found — propose removing the link and, if the slice still needs the context, restating the decision in plain language with a Plan decisions References bullet naming the ID plus a one-sentence description. Cite the include/exclude list.

After validation, report findings in plain language. For each: (1) what is wrong — slice SYM, line reference, failing invariant; (2) the proposed fill — corrected line, new bullet, removed link; (3) the evidence — file path with line number, document section, or named source.

Then give the user three actions: Continue with fills (apply the repairs to the source work-items.md and proceed), Correct the fills (user provides the right values; apply those and proceed), or Stop (exit without creating issues). If validation passes with no findings, proceed to Step 5.