How does it handle branch naming and commits?

It automatically generates branch names based on the Linear issue ID and title, and formats commits to include descriptions and closing tags for better traceability.

Does this skill require a Linear account?

Yes, it utilizes the Linear MCP server to fetch issues, update statuses, and post design/plan links directly to your tickets.

Can I skip the TDD phase?

No, the workflow enforces TDD for every change to maintain high code quality and minimize regressions, requiring failing tests before implementation.

What happens if a quality gate fails?

The ship command will block PR creation until all tests, linting, and typechecks pass with zero errors and no high-confidence code review issues remain.

Team Development Workflow

Name: Team Development Workflow
Author: jeremyodell

byjeremyodell

Collaboration Tools

Enforces a structured, phase-gated development cycle for teams using Claude Code and Linear.

About

This skill provides a deterministic framework for software development, guiding users through a strict six-phase workflow from initial issue setup to final shipping. By integrating directly with Linear and mandating Test-Driven Development (TDD), it ensures that every code change is planned, tested, and quality-vetted before a pull request is created. It acts as a digital project manager within Claude Code, automating status updates, branch naming, and commit formatting to maintain high standards across the entire development lifecycle.

Key Features

Linear MCP integration for automatic issue fetching and status updates
Enforced Test-Driven Development (TDD) for every code change
Mandatory six-phase workflow: Setup, Brainstorm, Plan, Execute, Quality Check, and Ship
Automated quality gates including linting, typechecking, and AI-driven code reviews
Standardized Git workflow with automated branch naming and commit formatting
0 GitHub stars

Use Cases

Professional development teams looking to standardize Claude Code output quality
Projects requiring strict synchronization between Linear tickets and code progress
Developers who want to ensure 100% TDD compliance and zero-error shipping

About

Key Features

Linear MCP integration for automatic issue fetching and status updates
Enforced Test-Driven Development (TDD) for every code change
Mandatory six-phase workflow: Setup, Brainstorm, Plan, Execute, Quality Check, and Ship
Automated quality gates including linting, typechecking, and AI-driven code reviews
Standardized Git workflow with automated branch naming and commit formatting
0 GitHub stars

Use Cases

Professional development teams looking to standardize Claude Code output quality
Projects requiring strict synchronization between Linear tickets and code progress
Developers who want to ensure 100% TDD compliance and zero-error shipping