A one-pass implementation workflow for completing a single ticket or small code change during the current session. It includes checking the work, reviewing it, and updating the ticket when finished.

Use it to implement a ready ticket or a small, well-defined change, with testing, simplification, verification, review, and a commit.

It gives a small piece of work a clear start-to-finish process. It also checks prerequisites and acceptance criteria so incomplete or blocked tickets are not treated as done.

implement — Skill for Claude Code by lttr

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add lttr/claude-marketplace --skill implement

Clone the repo

git clone --depth 1 https://github.com/lttr/claude-marketplace

Made for: Claude Code.

Or install aiwork, the plugin that ships this one along with the rest of its 11 skills, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lttr/claude-marketplace/implement.svg)](https://agentmods.dev/skills/lttr/claude-marketplace/implement)

Your own site

<a href="https://agentmods.dev/skills/lttr/claude-marketplace/implement"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/implement.svg" alt="Measured on agentmods" height="20"></a>

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 574 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00019	$0.00574
Opus 5	$0.00010	$0.00287
Sonnet 5	$0.00004	$0.00115
Haiku 4.5	$0.00002	$0.00057

Measured 3d ago against content hash fa897f5634e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

implement scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/aiwork/skills/implement/SKILL.md · 33 lines

How it starts

The opening of the file, as written. The whole thing — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement

Follows the aiwork-protocol skill. Don't enter plan mode — the ticket is the plan. One work item, one pass, this session; for a whole spec with a ticket graph use /implement-spec.

Resolve input

$ARGUMENTS is one of:

Ticket path: use directly. Verify the ticket is status: ready and every blocked_by ticket is status: done; if not, warn and ask.
Inline description: if trivial (fits one session, obvious approach), treat it as the work item. If non-trivial, stop and suggest /to-spec.
Spec/PRD or task folder path: stop and suggest /implement-spec.

Do

Set ticket status: in-progress (if working from a ticket).
Implement. Use /tdd where possible, at the seams recorded in the spec's Testing Decisions section.
Tidy the diff yourself — naming, duplication, dead scaffolding. Not /simplify: its reviewers would rediscover context you already have. Skip for a mechanical edit.
Run the project's check command (see its scripts). Green before anything below.
Run /verify <ticket-path> so it verifies the ticket's acceptance criteria, not just the diff. Check off - [ ] → - [x] for each criterion it passed.
Run /code-review low --fix. Re-run the checks if it changed code.
Set ticket status: done and verified: to the passes that ran (checks, behaviour, review), then commit. Do not ask. Report what was done and anything left open.

Stopping is hooked: the plugin's verified-gate holds the turn when a ticket claims done without an on-app pass (behaviour, ux or human in verified:) or with unticked acceptance criteria. Set the frontmatter because the passes ran, never to get past the hook. If a pass genuinely cannot run, leave the ticket in-progress and say why in implementation-notes.md. See /aiwork:implement-spec for details.

Record a note in the task folder's implementation-notes.md per aiwork-protocol when the reader must act on it: work only a human can finish, anything left unverified, a spec ambiguity you resolved, a deliberate deviation. A few sentences, never a log of what you built. Nothing to note is the normal case.

Read the full file on GitHub · 33 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago Changed · +3 lines fa897f5634e8
8d ago First seen · 30 lines · 19 tokens per session scan A c8c4eee41bec

Subscribe to this mod's changes

implement is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 574 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Project management claude-ai workflow

issue-triage

Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).

paperclipai/paperclip · 48 tokens

multi-agent

A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.

fengshao1227/ccg-workflow · 49 tokens

tencent-meeting-mcp

A Tencent Meeting assistant for scheduling meetings and working with participants, recordings, transcripts, and AI-generated meeting notes.

UnicomAI/wanwu · 327 tokens

flow-next-plan

Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).

gmickel/flow-next · 36 tokens

flow-next-tracker-sync

Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.

gmickel/flow-next · 44 tokens

stakeholder-communication

Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…

rampstackco/claude-skills · 103 tokens