linear-spec-plugin
vv2Spec-driven project execution pipeline backed by Linear. Same skills and agents as spec-plugin, but writes specs, stories and validation to Linear via GraphQL while keeping reasoning artifacts on disk.
By Jaison Erick1 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code and Agent Plugins
- Parsed components
- 9 skill or MCP entries
- Source updated
- Sep 16, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install linear-spec-plugin for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install linear-spec-plugin@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/nexaedge/nexaedge-marketplaceClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/linear-spec-plugin/.
Plugin files
├── .claude-plugin/plugin.json├── plugin.json├── skills/architect/SKILL.md├── skills/architect-version/SKILL.md├── skills/build-stories/SKILL.md├── skills/execute-task/SKILL.md├── skills/ideate/SKILL.md├── skills/orchestrate/SKILL.md├── skills/plan/SKILL.md├── skills/run-retrospective/SKILL.md└── skills/validate-execution/SKILL.md
Included Skills9
Create the project-level implementation approach as a Linear Project Document. For code projects: technology stack, schemas, API contracts, system design. For non-code projects: delivery approach, document structure, resource plan. Adapts based on the project spec. Use after /ideate.
Deep-dive architecture for a single spec. Reads the Linear spec issue, the deliverable's Architecture document, and adjacent spec issues, then writes the spec body to the issue description and creates a `Spec vX.Y — Architecture` Project Document. Use before /build-stories.
Break down a single Linear spec issue into executable story sub-issues. Reads the spec body, the spec architecture document, and the deliverable architecture, then creates one ordered sub-issue per story under the spec issue. Adapts to project type. Use after /architect-version.
Execute a single story sub-issue end-to-end — either a new story or a fix from validation findings. Reads the sub-issue, parent spec, and architecture, then produces working output that meets all acceptance criteria. Code goes through worktrees; execution logs and state changes go to Linear.
Build a comprehensive project specification through conversational refinement. Adapts to any project type — code, business, research, consulting. Reads workspace context to understand where it is and what kind of project this is. Use at the very start of a new project or major initiative.
Execute a Linear spec end-to-end with a coordinated agent team. Cycles through architect-version → build-stories → execute-task → validate-execution until the spec ships. Accepts a Linear identifier or text to search. A spec is shipped when the human signs off.
Design an evolutionary delivery roadmap by creating a Linear initiative (where applicable), deliverable projects, and one issue per spec. Adapts to project type — code releases, consulting milestones, research phases. Use after /ideate and /architect.
Post-spec retrospective that captures lessons learned, fixes documentation drift, and proposes skill improvements. Reads the Linear spec, story sub-issues with comments, and the Validation Report. Writes retrospective to the knowledge base on disk and posts a back-link comment on the spec issue.
Validate a Linear spec's implementation against its Definition of Done. For code projects: runs automated tests against the live application. For non-code projects: reviews deliverables against acceptance criteria. Writes a `Spec vX.Y — Validation Report` Project Document and comments the link on the spec issue. Runs incrementally on re-runs.
Plugin manifests2
{
"name": "linear-spec-plugin",
"description": "Spec-driven project execution pipeline backed by Linear. Same skills and agents as spec-plugin, but writes specs, stories and validation to Linear via GraphQL while keeping reasoning artifacts on disk.",
"version": "v2",
"author": {
"name": "Jaison Erick",
"url": "https://github.com/jaisonerick"
}
}{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "linear-spec-plugin",
"version": "v2",
"description": "Spec-driven project execution pipeline backed by Linear. Same skills and agents as spec-plugin, but writes specs, stories and validation to Linear via GraphQL while keeping reasoning artifacts on disk.",
"author": {
"name": "Jaison Erick",
"email": "[email protected]",
"url": "https://github.com/jaisonerick"
},
"homepage": "https://github.com/nexaedge/nexaedge-marketplace",
"repository": "https://github.com/nexaedge/nexaedge-marketplace",
"keywords": [
"spec",
"linear",
"agents",
"orchestration"
],
"extensions": {
"com.nexaedge.marketplace": {
"displayName": "Linear Spec Plugin",
"tagline": "The spec pipeline, with Linear as the system of record",
"category": "Developer Tools",
"platforms": [
"claude"
],
"requires": "plugin-provided subagents"
}
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[linear-spec-plugin on Agent Plugins Marketplace](https://pluginsmp.com/plugins/linear-spec-plugin)