[Extension]: Add Linear Weave

[tonydwoodhouse]

Extension ID

linear-weave

Extension Name

Linear Weave

Version

1.0.0

Description

Weave Spec Kit into Linear: pull requirements, mirror tasks.md into sub-issues, sync statuses.

Author

Tony Woodhouse

Repository URL

https://github.com/tonydwoodhouse/spec-kit-linear-weave

Download URL

https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.0.zip

License

MIT

Homepage (optional)

https://github.com/tonydwoodhouse/spec-kit-linear-weave

Documentation URL (optional)

https://github.com/tonydwoodhouse/spec-kit-linear-weave#readme

Changelog URL (optional)

https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.13.0,<1.0.0

Required Tools (optional)

A connected Linear MCP server in the coding agent (Claude Code: /mcp, or the claude.ai connector settings). All hooks no-op silently when the MCP server is unavailable, so the plain Spec Kit workflow is never blocked.

Number of Commands

5

Number of Hooks (optional)

5

Tags

linear, issue-tracking, integration, workflow

Key Features

• Pulls requirements from a referenced Linear issue (before_specify) and links the feature back to it (after_specify) — the only local state is one **Linear Issue**: line in spec.md.
• Mirrors tasks.md into Linear sub-issues at configurable granularity — task, phase, or story (one sub-issue per user story + a shared bucket; minimises issue count). Deduplicates on re-runs and places sub-issues on the parent's project board.
• Reconciles tasks.md checkbox state with Linear statuses during implement (before/after_implement), rewriting per-task checklists inside story/phase sub-issues. Idempotent.
• Ships a guided one-chat orchestrator (/speckit-linear-weave-flow) that runs specify → clarify → plan → tasks with a review gate after each phase, isolating heavy phases in subagents. Stops before implement.
• All hooks no-op silently when a feature isn't linked to Linear, so the plain Spec Kit workflow is never blocked.

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on Spec Kit 0.13.0 via a specify extension add --dev . install into a real project. All five commands compiled and the extension.yml manifest validated (specify extension list reports Commands: 5 | Hooks: 5). Ran a full /speckit-linear-weave-flow orchestration (specify → clarify → plan → tasks) followed by /speckit-implement against a real Linear workspace: requirements were pulled from the referenced issue, tasks.md was mirrored into sub-issues at story granularity on the parent's project board, dedup held on re-runs, and statuses reconciled correctly during implement. Confirmed hooks no-op silently for features with no Linear reference and when the Linear MCP server is disconnected.

Example Usage

/speckit-specify ENG-123     # requirements pulled from the Linear issue
/speckit-plan ...            # unchanged
/speckit-tasks               # main issue updated + sub-issues created at configured granularity
/speckit-implement           # Linear statuses tracked against tasks.md

# Or drive the whole authoring workflow in one chat with a review gate per phase:
/speckit-linear-weave-flow ENG-123

Proposed Catalog Entry

{
  "name": "Linear Weave",
  "id": "linear-weave",
  "description": "Weave Spec Kit into Linear: pull requirements, mirror tasks.md into sub-issues, sync statuses.",
  "author": "Tony Woodhouse",
  "version": "1.0.0",
  "download_url": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.0.zip",
  "repository": "https://github.com/tonydwoodhouse/spec-kit-linear-weave",
  "license": "MIT",
  "requires": { "speckit_version": ">=0.13.0,<1.0.0" },
  "tags": ["linear", "issue-tracking", "integration", "workflow"]
}

Additional Context

Commands: 5 total. Four are hook-bound (pull → before_specify, link → after_specify, tasks → after_tasks, sync → before_implement + after_implement), giving 5 hook bindings across those four commands. The fifth command, flow (/speckit-linear-weave-flow), is user-invocable with no hook. Linear is the source of truth — the only local state is a single **Linear Issue**: line written into each feature's spec.md.

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Pull request created: #3609

Generated by Add Community Extension from Issue Submission · 195.5 AIC · ⌖ 15.1 AIC · ⊞ 34.5K

[mnriem]

@tonydwoodhouse Can you validate that the comment at #3609 (review) is correct and it should be adjusted?

[tonydwoodhouse]

@mnriem yes I agree, required: true is a more accurate representation of what the extension does. My extension.yml doesn't set the tool dependency explicitly, so there's no conflict on the release - please go ahead and apply it. I can add it to the manifest and tag a new v1.0.1 release if you'd prefer it declared at the source too.

[mnriem]

Thank you!