linear-implement-feature

Implement approved OpenSpec proposals into feature branches and pull requests.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/jankneumann/agentic-content-analyzer --skill linear-implement-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-implement-feature
Source: https://github.com/jankneumann/agentic-content-analyzer/tree/main/.gemini/skills/linear-implement-feature
Command: npx skills add https://github.com/jankneumann/agentic-content-analyzer --skill linear-implement-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end work of taking an approved OpenSpec proposal through isolated development, test-driven implementation, quality validation, and pull request creation so engineers and agents avoid manual coordination, branch conflicts, and repetitive checklist work.

Core Features & Use Cases

  • Isolated worktree setup: Create and operate inside a per-change worktree to avoid conflicts with other sessions.
  • TDD-led change context: Generate a traceability matrix and failing tests first, then implement code to satisfy those tests.
  • Coordinator-aware execution and guardrails: Integrate optional locking, handoff, queueing, and guardrail checks; support parallel task execution and aggregated quality checks. Use case: an engineer or automation agent receives an approved openspec change-id and needs to produce a verified feature branch with tests passing and a PR ready for review.

Quick Start

Implement the OpenSpec change-id 12345 through to PR creation.

Frequently Asked Questions about linear-implement-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement an OpenSpec proposal into a pull request?

To implement an OpenSpec proposal into a pull request, this Skill automates the end-to-end workflow by creating an isolated worktree, generating a TDD-led change context, and running quality checks before PR creation. You provide the approved openspec change-id.

How does test-driven development work with OpenSpec changes?

Test-driven development with OpenSpec changes works by generating a traceability matrix and writing failing tests first. The Skill then implements code specifically to satisfy those tests, ensuring requirements are validated before the code is merged.

Can I run parallel task execution for OpenSpec feature implementation?

Yes, you can run parallel task execution for OpenSpec feature implementation. The Skill supports coordinator-aware execution with optional locking, queueing, and guardrails, allowing multiple tasks to operate concurrently without branch conflicts.

What is an isolated worktree and why is it needed for feature development?

An isolated worktree is a per-change Git working directory that prevents conflicts with other active sessions. It is needed for feature development to maintain a clean environment while tracing, implementing, and validating OpenSpec proposal artifacts.

Do I need an approved change-id to start repository-based feature development?

Yes, you need an approved change-id to start repository-based feature development. The Skill requires an openspec/changes/<change-id> proposal that defines the tasks, tests, and design artifacts necessary to trace and validate the implementation.