workflow

Manage ticket-based development workflows with branches, worktrees, and context files.

Updated Jan 26, 2026

Search Tags:#automation #workflow #branching #linear #git-worktree #ticket-based

Ready to run

npx skills add https://github.com/dohernandez/claude-skills --skill workflow-dohernandez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/dohernandez/claude-skills/tree/main/plugins/workflow/skills/workflow
Command: npx skills add https://github.com/dohernandez/claude-skills --skill workflow-dohernandez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the development environment lifecycle for ticket-based work, including branch creation, worktree management, context, and delegation to the appropriate skills.

Core Features & Use Cases

Automates start, status, merge, and finish workflows for ticket-driven development.
Coordinates with /bugfix and /task to implement bug fixes or features within isolated worktrees.
Keeps a per-repo workflow context to enable handoffs between Claude sessions and IDEs.

Quick Start

Start a workflow with /workflow start PROJ-123 to initialize a new ticket-based development session.

Frequently Asked Questions about workflow

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

FAQPage Schema

How do I automate ticket-based development workflows with git worktree and Linear?▼

Automate ticket-based workflows by initializing a session that creates git worktrees, branches, and context files. The system coordinates start, status, and finish phases for Linear tickets while delegating implementation to specialized bugfix and task skills.

What is the best way to manage isolated development branches for multiple Linear tickets?▼

Manage isolated development branches by using git worktree to create separate working directories for each Linear ticket. The workflow builds per-repo context files to enable seamless handoffs between Claude sessions and IDEs across different environments.

Can I use plain text descriptions instead of Linear tickets to start a development workflow?▼

Yes, development workflows can be started using plain text descriptions as an alternative to Linear tickets. The workflow processes both Linear ticket identifiers and plain text descriptions to initialize branches, worktrees, and context for the session.

How do I prevent losing uncommitted changes when starting a new ticket workflow?▼

Prevent losing uncommitted changes through built-in safeguards that check workspace status before starting. The workflow enforces safeguards for uncommitted changes, PR status, and workspace setup to ensure a clean environment before initializing new ticket-based sessions.

Does the workflow skill handle merging and finishing pull requests for ticket-based branches?▼

Yes, the workflow handles merge and finish phases for ticket-based branches. It coordinates the end-to-end execution by checking PR status and delegating the final implementation steps to bugfix and task skills before completing the workflow.