[Extension]: Update Linear Weave to v1.0.2 #5045

Extension ID

linear-weave

Extension Name

Linear Weave

Version

1.0.2

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.2.zip

License

MIT

Homepage (optional)

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

Documentation URL (optional)

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

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)

linear-mcp (required) — 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. Declared in extension.yml's requires.tools since v1.0.1.

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.
• New in 1.0.2: documentation consistency fixes — story is consistently identified as the shipped default granularity, and the README describes status transitions via the configurable statuses.in_progress / statuses.done values.

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:

• Windows 11 with Spec Kit v0.13.0

Test project: a real feature workflow in a private project, linked to Linear issues.

Test scenarios:

1. Installed extension from the GitHub release v1.0.1 into a real project
2. Configured linear-config.yml (default story granularity)
3. Ran a full /speckit-linear-weave-flow (specify → clarify → plan → tasks) against a Linear issue, then /speckit-implement
4. Verified: requirements pulled from the Linear issue, spec.md linked back to it, sub-issues created per user story with correct task checklists, and all statuses reconciled to Done once tasks completed.

(End-to-end scenarios above were run on v1.0.1.) What's new in 1.0.2: documentation-only changes (command prompt wording and README); no change to extension.yml beyond the version, and no runtime behaviour change.

Example Usage

# Install extension
specify extension add linear-weave --from https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.2.zip

# Use it — no Linear steps typed in chat, just reference the issue
/speckit-specify ENG-123
/speckit-clarify
/speckit-plan
/speckit-tasks
/speckit-implement

# Or drive specify -> clarify -> plan -> tasks in one guided chat using sub-agents for context management
/speckit-linear-weave-flow ENG-123

Proposed Catalog Entry

{
  "linear-weave": {
    "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.2",
    "download_url": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.2.zip",
    "repository": "https://github.com/tonydwoodhouse/spec-kit-linear-weave",
    "homepage": "https://github.com/tonydwoodhouse/spec-kit-linear-weave",
    "documentation": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/README.md",
    "changelog": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.13.0,<1.0.0",
      "tools": [{ "name": "linear-mcp", "required": true }]
    },
    "provides": { "commands": 5, "hooks": 5 },
    "tags": ["linear", "issue-tracking", "integration", "workflow"]
  }
}

Additional Context

Update to the existing linear-weave entry (originally #3603, last updated via #3758). Only the version and download URL change, to 1.0.2. This release fixes documentation inconsistencies reported in tonydwoodhouse/spec-kit-linear-weave#1: the tasks command no longer labels task as the default granularity (story is the shipped default), and the README describes status transitions via the configurable statuses.done value rather than a literal Done. All other fields are unchanged.