work-on-issue

Orchestrate the nine-phase SDLC workflow for a Linear issue.

Updated Oct 15, 2025
One-click install
npx skills add https://github.com/kingler/v0-jetvision-assistant --skill work-on-issue-kingler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-on-issue
Source: https://github.com/kingler/v0-jetvision-assistant/tree/main/.claude/skills/work-on-issue
Command: npx skills add https://github.com/kingler/v0-jetvision-assistant --skill work-on-issue-kingler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the full SDLC workflow for a Linear issue, unifying workspace setup, testing, implementation, code review, PR creation, and merge.

Core Features & Use Cases

  • End-to-end lifecycle coordination across 9 phases
  • Workspace automation and context fetching
  • Hooks and MCP tool integrations for issue tracking and PR flow

Quick Start

Invoke /work-on-issue ONEK-XXX to initialize the workspace, fetch context, and detect the current phase.

Frequently Asked Questions about work-on-issue

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

FAQPage Schema
How do I automate the Linear issue workflow from start to finish?

To automate the Linear issue workflow, this skill coordinates the full SDLC lifecycle, unifying workspace setup, testing, implementation, code review, and PR merge into a single command chain.

How do I start work on a Linear issue using a command?

You can start work on a Linear issue by invoking the command with your issue ID to initialize the workspace, fetch context, and detect the current phase automatically.

Can I resume an in-progress Linear issue if the workspace context is lost?

Yes, you can resume an in-progress Linear issue because the skill detects the current phase within the nine-phase SDLC lifecycle and restores the necessary workspace metadata.

Does this Linear issue manager enforce prerequisites before moving to code review?

Yes, the Linear issue manager enforces strict prerequisites and provides safety hooks to ensure proper transitions between phases like implementation and code review.

What is the best way to manage a nine-phase SDLC lifecycle for a Linear issue?

The best way to manage a nine-phase SDLC lifecycle is using a dedicated orchestration skill that applies safety hooks and workspace metadata to track issue transitions end-to-end.

Why does my Linear issue workflow fail to transition between implementation and PR creation?

Your Linear issue workflow fails to transition because it enforces strict prerequisites and relies on hooks to ensure proper transitions before proceeding to PR creation.