repl-driven-development

Name: repl-driven-development
Availability: InStock
Author: Pyze

Guides a 13-phase REPL-driven workflow with TDD and clojure_eval for Clojure development.

Updated Mar 16, 2026

Search Tags:#testing #tdd #development workflow #repl #clojure #incremental development

Ready to run

npx skills add https://github.com/pyze/claude-plugin --skill repl-driven-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repl-driven-development
Source: https://github.com/pyze/claude-plugin/tree/main/skills/repl-driven-development
Command: npx skills add https://github.com/pyze/claude-plugin --skill repl-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides you through building software incrementally and interactively using the REPL (Read-Eval-Print Loop) and TDD (Test-Driven Development) methodologies, ensuring features are built with immediate feedback and validated at each step.

Core Features & Use Cases

Interactive Development: Explore code, test assumptions, and debug live state directly in the REPL.
Phased Workflow: Follow a structured 13-phase methodology for comprehensive development, from specification to code quality checks.
Use Case: When developing a new API endpoint, you'll use the REPL to explore data structures, write a failing test for the endpoint, implement the minimal code to pass the test, and then refine the implementation based on REPL feedback.

Quick Start

Use the repl-driven-development skill to build a new feature by exploring at the REPL and writing a failing test first.

Frequently Asked Questions about repl-driven-development

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

FAQPage Schema

How do I build Clojure features incrementally using REPL and TDD?▼

Clojure REPL and TDD incremental development involves a 13-phase methodology from specification to code quality. You explore data structures interactively, write failing tests, implement minimal code to pass, and refine using immediate REPL feedback via hot-reloading.

What is the REPL-driven development workflow for testing assumptions in Clojure?▼

The REPL-driven development workflow allows you to interactively explore live code state, test assumptions, and debug directly. It mandates using the clojure_eval MCP tool for all REPL interactions to validate features with immediate feedback.

Do I need integrant-repl to hot-reload code during TDD development?▼

Yes, this REPL-driven development workflow specifically mandates using integrant-repl for hot-reloading your system components. This ensures your interactive exploration and test-driven changes are immediately reflected in your live application state.

Can I use this incremental development methodology for building new API endpoints?▼

Yes, building new API endpoints is a primary use case. You explore endpoint data structures at the REPL, write a failing test for the expected behavior, implement minimal code to pass the test, and refine the implementation based on REPL feedback.

What's the best way to structure a Clojure development workflow from specification to code quality?▼

The best way to structure this Clojure development workflow is following the provided 13-phase methodology. It comprehensively guides you from initial specification through interactive REPL exploration and TDD implementation, ending with final code quality checks.

When should I not use REPL-driven development for Clojure projects?▼

You should not use REPL-driven development for Clojure projects that lack a clear testing strategy or do not support hot-reloading environments. The methodology relies heavily on interactive exploration and Test-Driven Development validation at each incremental step.