code-implement

Automate test-first development and plan-driven implementation using TDD.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/rupertsworld/skills --skill code-implement-rupertsworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-implement
Source: https://github.com/rupertsworld/skills/tree/main/code-implement
Command: npx skills add https://github.com/rupertsworld/skills --skill code-implement-rupertsworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers implement features by following a test-driven workflow built around a prepared plan, ensuring tests define behavior before code.

Core Features & Use Cases

  • Write and run tests first to validate acceptance criteria before coding.
  • Implement features with iterative guardrails and code quality reviews.
  • Apply the plan-driven approach to coordinate work across tasks, reviews, and deployment.

Quick Start

Start by reviewing the codebase with the code-review step, then write tests first according to the plan and implement until all tests pass.

Frequently Asked Questions about code-implement

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

FAQPage Schema
How do I implement features using test-driven development from a plan?

Test-driven development from a plan involves writing tests first to validate acceptance criteria before coding. You then implement features iteratively with guardrails and code quality reviews until all tests pass.

What is the TDD workflow for plan-driven software implementation?

The TDD workflow for plan-driven implementation automates test-first development by enforcing test creation before coding. It coordinates work across tasks and reviews using deterministic worktree management to verify against plan criteria.

Do I need a complete plan with acceptance criteria before starting TDD implementation?

Yes, test-driven implementation requires a thorough plan defining acceptance criteria, architecture decisions, and release expectations. The plan provides necessary guardrails to validate behavior through tests before writing code.

How do I manage worktrees when applying test-driven development?

Test-driven development uses deterministic worktree management to isolate feature implementation. This ensures tests define behavior before code within a controlled environment while verifying against plan criteria.

What's the best way to start a code review before writing tests in TDD?

Start by reviewing the codebase with the code-review step to understand existing structure. Then write tests first according to the plan's acceptance criteria and implement until all tests pass.

Can I use TDD implementation without predefined architecture decisions?

TDD implementation relies on a prepared plan with architecture decisions to guide test creation. Without these decisions, the test-first workflow lacks acceptance criteria needed to validate behavior before coding.