my-implement

Execute approved implementation plans with red/green/refactor TDD validation.

4|1|Updated May 31, 2015

Search Tags:#automation #tdd #quality-assurance #software-engineering #test-driven-development #plan-execution

Ready to run

npx skills add https://github.com/samcdavid/dotfiles --skill my-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: my-implement
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/my-implement
Command: npx skills add https://github.com/samcdavid/dotfiles --skill my-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Execute an approved implementation plan using mandatory red/green/refactor TDD to drive development, ensuring tests fail first and production code is added only after verification.

Core Features & Use Cases

Phase-by-phase execution of an approved implementation plan with mandatory TDD, producing failing tests first and minimal production code to pass.
Read plans from the user's local planner path (~/.claude/thoughts/shared/plans) and support resumption from the first unchecked item with loop-detection guards to avoid stalls.
Escalation and guidance when stuck, ensuring forward momentum and auditable progress through the plan.

Quick Start

Provide a plan path or select a plan from ~/.claude/thoughts/shared/plans/ to begin execution.

Frequently Asked Questions about my-implement

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

FAQPage Schema

How do I automate test-driven development execution for an implementation plan?▼

Test-driven development execution automates an approved implementation plan phase-by-phase using red, green, and refactor cycles. It reads plans from a local directory, writes failing tests first, and adds minimal production code to pass them.

What is the red green refactor workflow for software engineering plan execution?▼

The red, green, and refactor workflow is a test-driven development process where tests fail first, production code is added to pass them, and then code is refactored. This automates that cycle across software phases for deterministic verification.

How do I resume an approved implementation plan from the first unchecked item?▼

Resuming an implementation plan involves reading the plan file and restarting from the first unchecked item. Loop-detection guards prevent stalls and escalation guidance ensures forward momentum when progress halts.

What is the best way to enforce test-first validation during phase-by-phase development?▼

Enforcing test-first validation during phase-by-phase development is best achieved by automating the test-driven development cycle with guardrails. Production code is added only after tests verify failure, satisfying deterministic verification and auditable progress.

Why does my automated TDD execution stall and how do I get unstuck?▼

Automated TDD execution stalls when it detects a loop during plan execution. The system provides escalation and guidance mechanisms that intervene when stalling is detected, ensuring forward momentum through the implementation plan.

Do I need a specific plan format to execute TDD automation locally?▼

Yes, TDD automation requires an approved implementation plan stored locally at the designated shared planner path. Provide a plan path or select an existing plan from the local directory to begin phase-by-phase execution with deterministic verification.