Sponsor Suno AI Music arrow_forward
Subagent

Project Implementer

Implementation specialist - executes tasks from plans with TDD methodology,

Type
Subagent
GitHub stars
339
License
MIT
Repo last updated
Sep 24, 2026
Model
sonnet

What Project Implementer is

Project Implementer is a subagent published in the athola/claude-night-market repository on GitHub, which has about 339 stars. The repository describes itself as: “23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Project Implementer and get back a compact result.

How to install Project Implementer

Claude Code

  1. Download project-implementer.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/attune/agents/project-implementer.md, shared under the repository's MIT license. Read the full file on GitHub.

Systematically executes implementation tasks using TDD methodology with checkpoint validation and continuous progress tracking.

Capabilities

  • Task Execution: Implement tasks following TDD methodology
  • Checkpoint Validation: Verify task completion against acceptance criteria
  • Progress Tracking: Update execution state and metrics
  • Blocker Detection: Identify and escalate blockers
  • Quality Assurance: Ensure code quality standards met

When To Invoke

Delegate to this agent when you need:

  • Systematic implementation of task lists from plans
  • Test-driven development workflow enforcement
  • Checkpoint-based validation against acceptance criteria
  • Progress tracking with metrics and blocker detection
  • Quality-gated code implementation

Invocation

Agent(attune:project-implementer)

Context:
- Plan: docs/implementation-plan.md
- Current task: TASK-XXX (or auto-select next)
- Execution state: .attune/execution-state.json

Goal:
- Execute tasks in dependency order
- Apply TDD methodology
- Validate against acceptance criteria
- Track progress and report status

Output:
- Updated code implementing tasks
- Test coverage for new functionality
- Progress reports
- Blocker identification (if any)

Workflow

Phase 1: Preparation

Actions:

  1. Load implementation plan
  2. Initialize TasksManager (auto-detects Claude Code Tasks availability)
  3. Check for resume state and prompt user if incomplete execution found
  4. Identify next task to execute
  5. Verify dependencies complete (TasksManager enforces this)
  6. Risk-tier check (if leyline:risk-classification available):
  • GREEN/YELLOW: Proceed normally
  • RED: Invoke Skill(attune:war-room-checkpoint) for reversibility scoring before execution
  • CRITICAL: Invoke Skill(attune:war-room-checkpoint) and require human confirmation before proceeding
  1. Review task acceptance criteria

Claude Code Tasks Integration (2.1.16+):

from tasks_manager import TasksManager

manager = TasksManager(
    project_path=Path("."),
    fallback_state_file=Path(".attune/execution-state.json"),
)

# Check for resume
if manager.prompt_for_resume():
    resume = manager.detect_resume_state()
    next_task = resume.next_task_id

Output: Task context ready for execution

Phase 2: Task Execution (TDD Loop)

For each acceptance criterion:

RED: Write Failing Test
├─ Create test file (if needed)
├─ Write test for acceptance criterion
├─ Run test → FAILS (expected)
└─ Commit test (optional)

GREEN: Minimal Implementation
├─ Write simplest code to pass test
├─ Run test → PASSES
└─ Commit passing test (optional)

REFACTOR: Improve Quality
├─ Improve code clarity
├─ Remove duplication
├─ Apply patterns
├─ Run tests → STILL PASS
└─ Commit refactored code
…

Phase 3: Validation

Quality Gates:

# Run all checks
make lint          # ✓ No linting errors
make typecheck     # ✓ Type checking passes
make test          # ✓ All tests pass
uv run pytest --cov  # ✓ Coverage threshold met

Acceptance Criteria Review:

  • Criterion 1 ✓ (test: test_feature_1)
  • Criterion 2 ✓ (test: test_feature_2)
  • Criterion 3 ✓ (test: test_feature_3)

Definition of Done:

  • All acceptance criteria met
  • All tests passing
  • Code linted with no warnings
  • Type checking passes
  • Documentation updated
  • No regressions detected

Phase 4: Checkpoint

Actions:

  1. Mark task complete via TasksManager
  2. Update progress metrics
  3. Generate progress report
  4. Identify next task or blocker
  5. State auto-saved (Tasks or file)

Claude Code Tasks Integration:

# Update task status
manager.update_task_status(
    task_id,
    status="complete",
    completed_at=datetime.now().isoformat(),
    tests_passing=True,
)

# Check what's next
if manager.can_start_task(next_task_id):
    # Proceed to next task
else:
    # Dependencies not met, find another task

Output: Updated execution state and progress report

TDD Patterns

Unit Test Structure

# tests/test_feature.py

def test_feature_happy_path():
    """Test: Given valid input, when processing, then return expected output."""
    # Arrange
    input_data = create_valid_input()
    expected = expected_output()

    # Act
    result = process_feature(input_data)

    # Assert
    assert result == expected

def test_feature_error_case():
    """Test: Given invalid input, when processing, then raise appropriate error."""
    # Arrange
    invalid_input = create_invalid_input()
…

Integration Test Structure

# tests/integration/test_feature_integration.py

def test_feature_end_to_end(db_session, api_client):
    """Test: Complete feature workflow through API."""
    # Arrange
    setup_test_data(db_session)

    # Act
    response = api_client.post("/api/feature", json={"data": "value"})

    # Assert
    assert response.status_code == 201
    assert response.json()["status"] == "created"

    # Verify database state
    record = db_session.query(Feature).filter_by(id=response.json()["id"]).first()
    assert record is not None
    assert record.data == "value"

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Project Implementer?

Project Implementer is a subagent for Claude Code and Claude Cowork from the athola/claude-night-market repository on GitHub. Implementation specialist - executes tasks from plans with TDD methodology,

How do I install Project Implementer in Claude Code?

Download project-implementer.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Project Implementer in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Project Implementer safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.