implementation-workflow

Implements tasks and issues as sliced, reviewed branches through a gated autonomous workflow.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/hacker-cb/claude-code-plugins --skill implementation-workflow-hacker-cb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-workflow
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/implementation-workflow
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill implementation-workflow-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a task or issue into finished, reviewed code involves intake, codebase analysis, slicing, branching, development, review, and completion — a long chain where decisions get lost and half-finished work gets packaged as done. This Skill runs that whole chain: it reads the tasks, slices the work, settles every foreseeable decision at one planning gate, then executes each slice autonomously. ## Core Features & Use Cases - Forge-neutral intake: Accepts free-text asks, GitHub/GitLab issue numbers, or a mix, ruling each issue current against the refreshed base before building on it. - One planning gate: Settles slice breakdown, branch layout, architectural forks, completion mode (local merge or change request), merge strategy, and merge authorization in a single approval, with tier-scaled weight so trivial work skips the gate entirely. - Autonomous per-slice execution: Cuts each slice branch from its parent's current tip, develops it, and hands completion to the shipping-workflow skill, stopping and reporting honestly on failure rather than auto-reverting. - Use Case: You receive "do issue #42 and these two tickets". The Skill reads all three, proposes a two-slice plan with branches and a recommended completion mode, and after your approval implements, reviews, and ships each slice, ending with a cross-slice report. ## Quick Start Ask the assistant to implement issue #42 using the implementation-workflow skill and open the pull requests when done.

Frequently Asked Questions about implementation-workflow

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

FAQPage Schema
How do I implement a GitHub issue end to end with Claude Code?▼

Invoke the implementation-workflow skill with the issue number, such as "do issue #42". It reads the issue as a spec, checks it against the refreshed base branch, proposes a slice plan at one planning gate, then develops and ships each slice autonomously.

How does the skill split large tasks into reviewable slices?▼

It deep-reads the codebase against the tasks and drafts independently reviewable slices, each small enough to review and coherent enough to stand alone. One slice is the normal case; multiple slices stack on a shared feature branch cut from the base.

Can it merge locally instead of opening pull requests?▼

Yes. The planning gate settles a completion mode: local merges each slice into its parent branch with no forge involved, while request mode opens a change request per slice. Analysis, development, and review are identical in both modes.

When should I not use the implementation-workflow skill?▼

Do not use it for work already finished that only needs completing — that is shipping-workflow. It also does not drive an existing pull request (github-pr-workflow) or perform diff review (multi-review); it owns intake through implementation only.

What happens if a slice fails during the autonomous run?▼

The run stops without auto-reverting completed slices, reports the partial state, and skips later slices that depended on the failed one. A half-finished set is reported as half-finished, never packaged as whole.

Does the workflow survive a session restart or context compaction?▼

Yes. Multi-slice runs persist the plan — mode, merge authorization, strategy, and each slice's cut point — in a durable plan-doc plus the native task list. After a restart these are read first, then verified against the actual git tree, which outranks both.