linear-spec-plugin

What linear-spec-plugin does, in the publisher's words

From the project README, punctuation lightly normalized · Open the README on GitHub →

Links

• github.com/nexaedge/nexaedge-marketplace
• plugins/linear-spec-plugin/plugin.json (manifest)

Skills · 9

architect-version

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.

architect

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.

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-task

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.

ideate

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.

orchestrate

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.

plan

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.

run-retrospective

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-execution

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 t…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

Category

Agent Tooling. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.

Keywords

spec · linear · agents · orchestration

Related by publisher and keywords

• spec-pluginnexaedge

  Spec-driven project execution pipeline, from ideation to verified deliverables, orchestrated by AI agents. Works with any project type. Built on a team of subagents plus a tool-use hook, so it needs an agent that can run plugin-provided subagents and hooks.

• artifact-publishnexaedge

  Publish a self-contained HTML file as a shareable artifact on artifacts.nexaedge.com. Sign in with any Google Workspace account: the artifact belongs to that account's domain, and only that domain can open it. Also issues expiring links for people outside the domain.

• cloudflare-dnsnexaedge

  Manage Cloudflare DNS zones and records through Terraform in the nexaedge/infrastructure repository. Automates the full workflow: edit Terraform files, open PR, review plan, merge, watch apply, and verify.

• html-reportnexaedge

  Turn finished analysis results into a self-contained interactive HTML report: charts, cohort heatmaps, sortable tables and stat tiles, all inline in one file that opens by double-click with no network. Carries no brand of its own: it derives a theme from a brand color, or lifts one verbatim out of a report it built earlier.

• miro-boardnexaedge

  Read any Miro board you can open in your browser, then work out what it says. Miro's public API cannot reach a board you were invited to in someone else's team, and the canvas is WebAssembly so there is nothing in the page to scrape; this reads the board through your own signed-in session instead, opening Chrome once and then talking to Miro's realtime gateway directly. Extraction and interpretation are kept apart on purpose: the scripts measure geometry, colour, containment and edge alignment and never conclude anything, offering overlapping candidate groupings with the evidence behind each, because what a board means lives in how it was arranged and only reading the text can settle it.

• nexaedgenexaedge

  Front end for the nexaedge marketplace that works the same on Claude Code, Codex and Antigravity. Detects which agent is running, translates to that agent's native install path, and keeps everything at user scope so a plugin is installed once per machine rather than copied into each repository.