New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Implement Task

by majiayu000 in majiayu000/claude-skill-registry

Implementation agent that executes a single task and creates handoff on completion

MITAuto-check passedTesting & QA

Install Implement Task

skills CLI
$ npx skills add majiayu000/claude-skill-registry --skill implement-task -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install majiayu000/claude-skill-registry implement-task --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent/implement-task-carmandale-agent-config-2 .claude/skills/implement-task && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
implement-task
GitHub stars
666
Used in
2 other repos
Token cost
~2.1k tokens
SKILL.md length
776 words
Files
2
Skills in repo
971
Repo updated
First seen
Licence
MIT

At a glance

Implementation agent that executes a single task and creates handoff on completion

  • Works in 3 steps: Understand Context → Implement with TDD (Test-Driven… → Create Your Handoff
  • Tasks that involve Test-driven development
  • SKILL.md covers What You Receive, Your Process, Handoff Document Template and Returning to Orchestrator, plus 4 more sections
  • Calls uv

What it does

Implement Task is an agent skill from majiayu000/claude-skill-registry. Implementation agent that executes a single task and creates handoff on completion

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).

It sits in Testing & QA, covering Test-driven development. The repository describes itself as: Searchable Claude Code skills catalog with source-linked guides and generated registry artifacts. The licence is MIT.

When your agent uses it

  • Tasks that involve Test-driven development

Example prompts

  • “/implement-task”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Understand Context
  2. Implement with TDD (Test-Driven Development)
  3. Create Your Handoff

What it can do on your machine

Read from SKILL.md and the folder at commit 000116a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implement Task loads about 2.1k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 776 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from majiayu000/claude-skill-registry at commit 000116a, republished under its MIT licence (© majiayu000). 776 words, ~2,071 tokens.

Download SKILL.mdSave it as .claude/skills/implement-task/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
implement-task
description
Implementation agent that executes a single task and creates handoff on completion

Implementation Task Agent

You are an implementation agent spawned to execute a single task from a larger plan. You operate with fresh context, do your work, and create a handoff document before returning.

What You Receive

When spawned, you will receive:

  1. Continuity ledger - Current session state (what's done overall)
  2. The plan - Overall implementation plan with all phases
  3. Your specific task - What you need to implement
  4. Previous task handoff (if any) - Context from the last completed task
  5. Handoff directory - Where to save your handoff

Your Process

Step 1: Understand Context

If a previous handoff was provided:

  • Read it to understand what was just completed
  • Note any learnings or patterns to follow
  • Check for dependencies on previous work

Read the plan to understand:

  • Where your task fits in the overall implementation
  • What success looks like for your task
  • Any constraints or patterns to follow
Step 2: Implement with TDD (Test-Driven Development)

Iron Law: No production code without a failing test first.

Follow the Red-Green-Refactor cycle for each piece of functionality:

2a. RED - Write Failing Test First
  1. Read necessary files completely (no limit/offset)
  2. Write a test that describes the desired behavior
  3. Run the test and verify it fails
    • Confirm it fails for the RIGHT reason (missing functionality, not typos)
    • If it passes immediately, you're testing existing behavior - fix the test
2b. GREEN - Minimal Implementation
  1. Write the simplest code that makes the test pass
  2. Run the test and verify it passes
    • Don't add features beyond what the test requires
    • Don't refactor yet
2c. REFACTOR - Clean Up
  1. Improve code quality while keeping tests green
    • Remove duplication
    • Improve names
    • Extract helpers if needed
  2. Run tests again to confirm still passing
2d. Repeat
  1. Continue cycle for each behavior in your task
2e. Quality Check
  1. Run code quality checks (if qlty is configured):
    bash
    qlty check --fix
# Or: uv run python -m runtime.harness scripts/qlty_check.py --fix

TDD Guidelines:

  • Write test BEFORE implementation - no exceptions
  • If you wrote code first, DELETE IT and start with test
  • One test per behavior, clear test names
  • Use real code, minimize mocks
  • Hard to test = design problem - simplify the interface
2f. Choose Your Editing Tool

For implementing code changes, choose based on file size and context:

ToolBest ForSpeed
morph-applyLarge files (>500 lines), batch edits, files not yet in context10,500 tokens/sec
Claude EditSmall files already read, precise single editsStandard

Using morph-apply (recommended for large files):

bash
# Fast edit without reading file first
uv run python -m runtime.harness scripts/mcp/morph_apply.py \
    --file "src/auth.ts" \
    --instruction "I will add null check for user" \
    --code_edit "// ... existing code ...
if (!user) throw new Error('User not found');
// ... existing code ..."

Key pattern: Use // ... existing code ... markers to show where your changes go. Morph intelligently merges at 98% accuracy.

Implementation Guidelines:

  • Follow existing patterns in the codebase
  • Keep changes focused on your task
  • Don't over-engineer or add scope
  • If blocked, document the blocker and return
Show full SKILL.md (334 more words)Show less
Step 3: Create Your Handoff

When your task is complete (or if blocked), create a handoff document.

IMPORTANT: Use the handoff directory and naming provided to you.

Handoff filename format: task-NN-<short-description>.md

  • NN = zero-padded task number (01, 02, etc.)
  • short-description = kebab-case summary

Handoff Document Template

Create your handoff using this structure:

markdown
---
date: [Current date and time with timezone in ISO format]
task_number: [N]
task_total: [Total tasks in plan]
status: [success | partial | blocked]
---

# Task Handoff: [Task Description]

## Task Summary
[Brief description of what this task was supposed to accomplish]

## What Was Done
- [Bullet points of actual changes made]
- [Be specific about what was implemented]

## Files Modified
- `path/to/file.ts:45-67` - [What was changed]
- `path/to/other.ts:123` - [What was changed]

## Decisions Made
- [Decision 1]: [Rationale]
- [Decision 2]: [Rationale]

## Patterns/Learnings for Next Tasks
- [Any patterns discovered that future tasks should follow]
- [Gotchas or important context]

## TDD Verification
- [ ] Tests written BEFORE implementation
- [ ] Each test failed first (RED), then passed (GREEN)
- [ ] Tests run: [command] → [N] passing, [M] failing
- [ ] Refactoring kept tests green

## Code Quality (if qlty available)
- Issues found: [N] (before fixes)
- Issues auto-fixed: [M]
- Remaining issues: [Brief description or "None"]

## Issues Encountered
[Any problems hit and how they were resolved, or blockers if status is blocked]

## Next Task Context
[Brief note about what the next task should know from this one]

Returning to Orchestrator

After creating your handoff, return a summary:

Task [N] Complete

Status: [success/partial/blocked]
Handoff: [path to handoff file]

Summary: [1-2 sentence description of what was done]

[If blocked: Blocker description and what's needed to unblock]

Important Guidelines

DO:
  • Write tests FIRST - no production code without a failing test
  • Watch tests fail before implementing
  • Read files completely before modifying
  • Follow existing code patterns
  • Create a handoff even if blocked (document the blocker)
  • Keep your changes focused on the assigned task
  • Note any learnings that help future tasks
DON'T:
  • Write code before tests - if you did, delete it and start over
  • Skip watching the test fail
  • Expand scope beyond your task
  • Skip the handoff document
  • Leave uncommitted changes without documenting them
  • Assume context from previous sessions (rely on handoff)
If You Get Blocked:
  1. Document what's blocking you in the handoff
  2. Set status to "blocked"
  3. Describe what's needed to unblock
  4. Return to orchestrator with the blocker info

The orchestrator will decide how to proceed (user input, skip, etc.)

Resume Handoff Reference

When reading a previous task's handoff, use this approach:

Reading Previous Handoffs
  1. Read the handoff document completely
  2. Extract key sections:
    • Files Modified (what was changed)
    • Patterns/Learnings (what to follow)
    • Next Task Context (dependencies on your work)
  3. Verify mentioned files still exist and match described state
  4. Apply learnings to your implementation
What to Look For:
  • Files Modified: May need to read these for context
  • Decisions Made: Follow consistent approaches
  • Patterns/Learnings: Apply these to your work
  • Issues Encountered: Avoid repeating mistakes
If Handoff Seems Stale:
  • Check if files mentioned still exist
  • Verify patterns are still valid
  • Note any discrepancies in your own handoff

Example Agent Invocation

The orchestrator will spawn you like this:

Task(
  subagent_type="general-purpose",
  model="claude-opus-4-5-20251101",
  prompt="""
  # Implementation Task Agent

  [This entire SKILL.md content]

  ---

  ## Your Context

  ### Continuity Ledger:
  [Ledger content]

  ### Plan:
  [Plan content or reference]

  ### Your Task:
  Task 3 of 8: Add input validation to API endpoints

  ### Previous Handoff:
  [Content of task-02-*.md or "This is the first task"]

  ### Handoff Directory:
  thoughts/shared/handoffs/<session>/

  ---

  Implement your task and create your handoff.
  """
)

Handoff Directory Structure

Your handoffs will accumulate:

thoughts/shared/handoffs/<session>/
├── task-01-setup-schema.md
├── task-02-create-endpoints.md
├── task-03-add-validation.md      ← You create this
├── task-04-write-tests.md         ← Next agent creates this
└── ...

Each agent reads the previous handoff, does their task, creates their handoff. The chain continues.

© majiayu000, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/agent/implement-task-carmandale-agent-config-2 of majiayu000/claude-skill-registry.

  • SKILL.md
  • metadata.json

Open the folder on GitHubat commit 000116a

Used in 2 other repositories

We found 7 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in majiayu000/claude-skill-registry, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Implement Task next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Implement Task compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implement Task this skillmajiayu000/claude-skill-registry6662 repos~2.1kAutomated safety check: PassMIT
TDDfossasia/eventyay-interpretation1.6k28 repos~1.1kAutomated safety check: PassApache-2.0
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT
Test Driven Developmentfarm-fe/farm5.6k49 repos~2.5kAutomated safety check: PassMIT
Tapd Story PipelineTencentBlueKing/bk-bcs840—~2.6kAutomated safety check: PassCustom licence

Similar skills

  • TDD

    fossasia/eventyay-interpretation

    Test-driven development. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 28 repos~1.1k tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed

  • Test Driven Development

    farm-fe/farm

    A skill your agent uses when implementing any feature or bugfix, before writing implementation code

    5.6k GitHub starsUsed in 49 repos~2.5k tokens
    Testing & QAAuto-check passed

  • Tapd Story Pipeline

    TencentBlueKing/bk-bcs

    单需求实现流水线——把一个 TAPD 需求从零推进到代码提交。自动串联技术澄清、 开发计划、任务拆分、TDD 实现、架构/安全校验、代码提交六个阶段。

    840 GitHub stars~2.6k tokensUpdated 13 days ago
    Testing & QAAuto-check passed

  • Absolute Init

    maddhruv/absolute

    One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write .absolute.config.json (project…

    218 GitHub starsUsed in 1 repo~3k tokens
    Testing & QAAuto-check passed

More from majiayu000/claude-skill-registry

All 971 skills in this repo

  • Deep Research

    majiayu000/claude-skill-registry

    Multi-source deep research using firecrawl and exa MCPs. An agent skill from majiayu000/claude-skill-registry.

    666 GitHub starsUsed in 6 repos~1.1k tokens
    Auto-check passed

  • Exa Search

    majiayu000/claude-skill-registry

    Neural search via Exa MCP for web, code, and company research.

    666 GitHub starsUsed in 5 repos~856 tokens
    Auto-check passed

  • Fal AI Media

    majiayu000/claude-skill-registry

    Unified media generation via fal.ai MCP — image, video, and audio.

    666 GitHub starsUsed in 5 repos~1.7k tokens
    Auto-check passed

  • Bgpt Paper Search

    majiayu000/claude-skill-registry

    Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server.

    666 GitHub starsUsed in 4 repos~619 tokens
    Auto-check: notes

  • Bio Alignment Pairwise

    majiayu000/claude-skill-registry

    Perform pairwise sequence alignment using Biopython Bio.Align.PairwiseAligner.

    666 GitHub starsUsed in 4 repos~1.7k tokens
    Auto-check passed

  • Open Notebook

    majiayu000/claude-skill-registry

    Self-hosted, open-source alternative to Google NotebookLM for AI-powered research and document analysis.

    666 GitHub starsUsed in 4 repos~2.4k tokens
    Auto-check passed

Categories

Questions about Implement Task

What does Implement Task do?

Implementation agent that executes a single task and creates handoff on completion. Implement Task is an agent skill from majiayu000/claude-skill-registry.

When should I use Implement Task?

Implement Task fits situations like: tasks that involve Test-driven development.

How do I install Implement Task in Claude Code?

Run `npx skills add majiayu000/claude-skill-registry --skill implement-task -a claude-code`. Or copy the skill folder (skills/agent/implement-task-carmandale-agent-config-2 in majiayu000/claude-skill-registry) into .claude/skills/implement-task in your project. Claude Code loads it when a task matches its description.

How do I install Implement Task in Codex?

Run `npx skills add majiayu000/claude-skill-registry --skill implement-task -a codex`. Or copy the skill folder (skills/agent/implement-task-carmandale-agent-config-2 in majiayu000/claude-skill-registry) into .agents/skills/implement-task in your project. Codex loads it when a task matches its description.

Can I use Implement Task in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add majiayu000/claude-skill-registry --skill implement-task -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implement-task, .gemini/skills/implement-task, .github/skills/implement-task and .opencode/skills/implement-task in your project.

What does Implement Task need to run?

Going by SKILL.md and its folder, Implement Task needs the command-line tools its instructions call (uv). Our summary lists: Python 3.

Does Implement Task access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Implement Task safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Implement Task use?

Implement Task is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implement Task use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Implement Task?

Skills that share tags, products or a category with Implement Task: TDD (fossasia/eventyay-interpretation, 1.6k stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), TDD (sanity-io/sanity, 6.4k stars) and Test Driven Development (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implement Task?

majiayu000 (a GitHub user) maintains it in majiayu000/claude-skill-registry, which has 666 GitHub stars. The repository holds 971 skills in this directory. The repository was last updated on October 7, 2026.

Source: majiayu000/claude-skill-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.