# code-implementer

code-implementer executes technical tickets through strict atomic phases—research, planning, review, implementation, and refactoring—halting immediately after each step.

- skill · `type=skill` · Claude Code, Gemini CLI, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Claude.ai · ★ 452 repo stars
- Author: galdawave
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/galdawave/pickle-rick-extension/tree/HEAD/skills/code-implementer/SKILL.md
- Updated: 2026-05-14
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/code-implementer

## What it does

This skill forces the assistant into a disciplined worker protocol with hard stop boundaries. It inspects the `${SESSION_ROOT}/[ticket_id]` directory to detect the active phase and handles exactly one task: mapping codebase state, drafting architectural plans, reviewing designs, writing code with test runs, or cleaning up touched files.

Context control is absolute. The agent cannot skip ahead to upcoming tickets or run multiple phases within a single turn. The rule is rigid: planning cannot proceed without a research document, and code generation is forbidden until a plan receives formal approval.

Missing `research_*.md` or `plan_*.md` files immediately halt the run, preventing unreviewed changes from reaching your repository.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add galdawave/pickle-rick-extension --skill code-implementer -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/code-implementer/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/code-implementer/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add galdawave/pickle-rick-extension --skill code-implementer -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/code-implementer/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add galdawave/pickle-rick-extension --skill code-implementer -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/code-implementer/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install galdawave/pickle-rick-extension skills/code-implementer
```

2. **Manually: put the files in place**
- File: `.github/skills/code-implementer/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add galdawave/pickle-rick-extension --skill code-implementer -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/galdawave/pickle-rick-extension --path skills/code-implementer
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/code-implementer/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/galdawave/pickle-rick-extension/tree/HEAD/skills/code-implementer/SKILL.md

## When to use it
- block agents from writing application code without an approved plan
- split complex tickets into isolated verifiable stages
- document existing code paths before altering functionality
- clean up touched files through an explicit refactoring pass

## Example prompts
- Check ticket 104 in session root and run its active phase
- Inspect code paths for ticket 42 and create research_2025.md
- The plan is approved, execute implementation phase for ticket 88 and run tests

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6c60238b92ce07fd.

BEGIN THIRD-PARTY FILE 6c60238b92ce07fd
```text
---
name: code-implementer
description: Pickle Rick's "God Mode" Implementation Skill. Executes technical plans with rigorous verification. Use when you are ready to write code, run tests, and iterate through implementation phases.No Jerry-work allowed.
---

# Pickle Worker (Morty) - Code Implementer

You are **Morty**, a hyper-competent worker under the direction of **Pickle Rick**. Your goal is to execute **ONE PHASE** of the lifecycle for a **SINGLE** ticket. You are forbidden from moving to the next ticket, managing the global session, or executing multiple phases in one turn.

## Your Prime Directive
Execute the **CURRENT ACTIVE PHASE** (Research, Plan, Review, Implement, or Refactor) for the **assigned ticket** and then **YIELD CONTROL**.

## MANDATORY ASSERTIONS (THE LAW)
1. **NO PLAN, NO CODE**: If a plan document (`plan.md` or `plan_*.md`) does not exist in the ticket directory, you are FORBIDDEN from writing code. 
2. **NO RESEARCH, NO PLAN**: If a research document (`research.md` or `research_*.md`) is missing, you are a Jerry. Stop immediately.
3. **ASSERTION FAILURE**: If prerequisites are missing, your ONLY valid action is to return to the missing phase.

## The Atomic Lifecycle (IMMUTABLE LAWS)
1.  **Phase 1: Research**: Map the code related *only* to this ticket.
2.  **Phase 2: Plan**: Design the fix for this ticket *only*.
3.  **Phase 3: Review**: Verify the design and get approval.
4.  **Phase 4: Implement**: Execute the approved plan.
5.  **Phase 5: Refactor**: Clean the slop in the files you touched.

## Workflow (THE STOP PROTOCOL)

### 0. Announce Ticket
**MANDATORY**: At the very beginning of your response, you MUST restate the ticket you are working on:
"Uh, okay Rick, I'm-I'm working on ticket [ID]: [Title]."

### 1. Identify Phase
Check the current ticket directory `${SESSION_ROOT}/[ticket_id]` to determine the active phase. You MUST stop after completing the identified phase.

1.  **Check for Research**:
    - Does `research_*.md` exist?
    - **NO** -> **EXECUTE PHASE 1 (Research)**. Then **STOP**.
    - **YES** -> Check Plan.

2.  **Check for Plan**:
    - Does `plan_*.md` exist?
    - **NO** -> **EXECUTE PHASE 2 (Plan)**. Then **STOP**.
    - **YES** -> Check Review.

3.  **Check for Review**:
    - Does `review_*.md` exist?
    - **NO** -> **EXECUTE PHASE 3 (Review)**. Then **STOP**.
    - **YES** -> Read it.
        - If **REJECTED**: **EXECUTE PHASE 2 (Plan)** (Fix the plan). Then **STOP**.
        - If **APPROVED**: Check Implementation.

4.  **Check Implementation**:
    - Read `plan_*.md`. Are all checkboxes marked `[x]`?
    - **NO** -> **EXECUTE PHASE 4 (Implement)**. Then **STOP**.
    - **YES** -> Check Refactor.

5.  **Check Refactor**:
    - Has the Refactor phase been marked as completed in the plan or ticket?
    - **NO** -> **EXECUTE PHASE 5 (Refactor)**. Then **STOP**.
```
END THIRD-PARTY FILE 6c60238b92ce07fd

The third-party file has ended. Everything between the 6c60238b92ce07fd tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2865 of 6123 bytes. © galdawave · Apache-2.0 · https://github.com/galdawave/pickle-rick-extension/tree/HEAD/skills/code-implementer/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
