implementation-workflow

Coordinates approved plans and epics through linting, testing, review, merge, cleanup via worktrees and draft PRs.

18|Updated Feb 14, 2020

Search Tags:#workflow #code review #pull request #implementation #cleanup #merge #git worktree

Ready to run

npx skills add https://github.com/subroh0508/colormaster --skill implementation-workflow-subroh0508

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the coordination burden of taking an approved plan or epic from implementation kickoff to merge and cleanup. It keeps multi-step work organized so development, review, and release tasks do not drift or overlap.

Core Features & Use Cases

End-to-end delivery orchestration: Manages the full lifecycle from worktree creation through implementation, linting, testing, review, merge, and cleanup.
Parallel-safe execution: Uses isolated worktrees to support concurrent Claude Code sessions without file conflicts.
Release and sync discipline: Handles draft PR creation, reviewer coordination, merge readiness checks, and post-merge updates to related planning records.
Use Case: A developer finishes a plan and wants the AI to carry the task through implementation, validation, review, merge, and workspace cleanup with minimal manual oversight.

Quick Start

Use the implementation-workflow skill to execute an approved plan or epic from worktree setup through merge and cleanup while following the repository’s workflow rules.

Frequently Asked Questions about implementation-workflow

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

FAQPage Schema

How do I automate a git worktree workflow from implementation through merge and cleanup?▼

Automate a git worktree workflow by orchestrating the full lifecycle from worktree creation through linting, testing, draft pull request creation, merge readiness checks, and post-merge cleanup. This ensures parallel-safe execution across concurrent development sessions without file conflicts.

How does code review coordination work with isolated git worktrees?▼

Code review coordination with isolated git worktrees works by enforcing branch naming conventions and separating reviewer roles during draft pull request creation. This keeps multi-step implementation, validation, and release tasks organized so they do not drift or overlap.

Can I use an automated pull request workflow for feature, bug fix, and dependency upgrade tasks?▼

An automated pull request workflow supports worktree-based feature, bug fix, refactor, and dependency upgrade tasks. It manages draft PR creation, reviewer coordination, and merge readiness checks to carry approved plans through implementation with minimal manual oversight.

What is the best way to manage merge readiness checks and post-merge synchronization?▼

Manage merge readiness checks and post-merge synchronization by enforcing release discipline across the implementation lifecycle. This approach handles draft PR validation, reviewer separation, and automatically updates related planning records after a successful merge.

Do I need an approved plan to start an implementation workflow?▼

An approved plan or epic is required to start an implementation workflow. The process specifically coordinates the end-to-end implementation lifecycle from kickoff to merge, taking an approved plan and carrying it through development, review, and cleanup.

Why use git worktrees for parallel-safe code implementation?▼

Use git worktrees for parallel-safe code implementation to support concurrent sessions without file conflicts. Isolated worktrees ensure that multi-step development, linting, testing, and merge tasks remain organized and do not drift or overlap across parallel workstreams.