implementation-phase

Guide TDD-driven feature implementation with continuous testing and anti-duplication checks.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill implementation-phase-dyai2025
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-phase
Source: https://github.com/DYAI2025/MOD_shark-engine/tree/main/sharkengine/.claude/skills/implementation-phase
Command: npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill implementation-phase-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of delivering high-quality software implementations quickly while preventing code duplication and ensuring ongoing test coverage by guiding teams through a structured TDD workflow.

Core Features & Use Cases

  • TDD-driven task execution: write tests before implementing features to ensure correct behavior.
  • Anti-duplication enforcement: detect and reuse existing utilities to reduce duplication.
  • Continuous testing and type/safety checks: run tests, type checks, and security validations after each task triplet.
  • Use Case: When implementing features from tasks.md during the /implement phase, or when users request TDD-based implementation.

Quick Start

Load tech stack constraints, review task dependencies, generate a test suite, implement with the RED → GREEN → REFACTOR cycle, and commit after each triplet.

Frequently Asked Questions about implementation-phase

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

FAQPage Schema
How do I implement features using a TDD workflow?▼

To implement features using a TDD workflow, you generate a test suite first, then apply the RED, GREEN, REFACTOR cycle to write code, and commit after each task triplet.

How do I prevent code duplication during feature development?▼

Preventing code duplication during feature development requires anti-duplication enforcement, which detects and reuses existing utilities to reduce redundant code across the tech stack.

What is the RED GREEN REFACTOR cycle in TDD?▼

The RED GREEN REFACTOR cycle in TDD is a workflow where you write failing tests first, implement code to pass the tests, and then refactor to improve code quality and reduce duplication.

Do I need a defined tech stack to run continuous testing?▼

Yes, you need a defined tech stack and test frameworks to run continuous testing, validate environments, execute type checks, and produce structured commits during implementation.

When should I run type and safety checks during TDD implementation?▼

You should run type and safety checks after completing each task triplet to enforce continuous testing and validate the environment during the implementation phase.

Can I use anti-duplication checks without test frameworks?▼

No, anti-duplication checks require defined test frameworks and a tech stack to validate environments, run tests, and ensure correct behavior before reusing existing utilities.