[Extension]: Update Linear Weave to v1.0.2
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 70/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Ambito
- release
Direzione di ricerca
Inizia leggendo la voce esistente del catalogo linear-weave, aggiunta originariamente in #3603 e aggiornata l’ultima volta in #3758. Confronta la sua versione e l’URL di download con la voce proposta in questo issue; aggiorna quei campi a 1.0.2 e all’URL dell’archivio v1.0.2. Verifica che gli altri campi siano invariati e che il catalogo punti alla nuova release.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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 —
storyis consistently identified as the shipped default granularity, and the README describes status transitions via the configurablestatuses.in_progress/statuses.donevalues.
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.ymlmanifest 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:
- Installed extension from the GitHub release v1.0.1 into a real project
- Configured
linear-config.yml(defaultstorygranularity) - Ran a full
/speckit-linear-weave-flow(specify → clarify → plan → tasks) against a Linear issue, then/speckit-implement - Verified: requirements pulled from the Linear issue,
spec.mdlinked 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 https://github.com/tonydwoodhouse/spec-kit-linear-weave/issues/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.
- Lingua principale
- Python
- Stelle
- 141k
- Fork
- 12.6k
- Merge medio
- 23h 11m
- PR unite (30g)
- 194
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/spec-kit
-
feature-assess feature-go triage-can-wait
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
github/spec-kit#4804 · 6 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: specify init writes speckit.manifest.json without the speckit-converge skill it just installedForse già presa @github-actions l’ha presa 5 giorni fa. Apertabug-assess severity-medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/spec-kit#4273 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: /speckit-implement counts checkbox markers inside fenced code blocks — example checkboxes can falsely block implementationForse già presa @ntdatt812 l’ha presa 40 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
[Extension]: Jira Integration (Sync Engine) v0.5.0 (version update of jira-sync)Forse già presa @github-actions l’ha presa 64 giorni fa. Apertaextension-submission validation-passed
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/spec-kit#4099 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[Extension]: Add spec-kit-switchForse di nuovo libera @wagner-sousa l’ha presa 80 giorni fa e non c’è nessuna pull request aperta. Apertaextension-submission validation-passed
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
github/spec-kit#3932 · 6 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di github/spec-kit
Issue simili
-
[Bug] Unit tests reach real Bedrock call paths without patching the modelForse già presa @proton0210 l’ha presa oggi. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
aws-samples/sample-aws-genai-db-modernizer#1318 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
pyarrow-25.0.1-cp310-cp310-manylinux_2_28_x86_64.whl: 1 vulnerabilities (highest severity is: 5.3)ApertaMend: dependency security vulnerability
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
capitalone/locopy#394 ·
-
[Bug] Unhandled ValueError terminates watchdog thread when GISRC value contains multiple colonsApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
sdk-typescript: unquoted COPY globs in shell form are silently dropped from the image build contextApertabug javascript
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
ietf-tools/datatracker#11922 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno