implement

Orchestrate the RED-GREEN-REFACTOR TDD loop for a single @id.

11|2|Updated Apr 7, 2022

Search Tags:#testing #tdd #quality-gates #feature-development #beehave

Ready to run

npx skills add https://github.com/nullhack/temple8 --skill implement-nullhack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/nullhack/temple8/tree/main/.opencode/skills/implement
Command: npx skills add https://github.com/nullhack/temple8 --skill implement-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Step 3 in the feature lifecycle ensures code is developed via a disciplined TDD cycle, explicitly guiding engineers through RED → GREEN → REFACTOR for a single @id at a time to prevent scope drift.

Core Features & Use Cases

Orchestrates the Step 3 TDD loop with one @id focus per feature.
Enforces the prior-step prerequisites (architecture stubs from Step 2) and a strict test-first workflow.
Supports end-to-end handoff readiness by aligning with lint, static-check, and test-coverage gates before merging.

Quick Start

Load this skill to continue Step 3 and execute the RED, GREEN, REFACTOR cycle for the next @id.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I enforce a strict test-first TDD workflow for a single feature component?▼

You need architecture stubs from Step 2 inside your package directory. These pre-existing stubs are required prerequisites to load the skill and execute the test-first workflow on a single @id.

What quality gates must pass before merging TDD feature code?▼

Quality gates for lint, static-check, and test-coverage must pass prior to handoff. The workflow aligns these checks to ensure end-to-end readiness before code merging.

How do I execute the RED GREEN REFACTOR loop for in-progress feature development?▼

Load the skill to continue Step 3 and execute the RED, GREEN, REFACTOR cycle for the next @id. It orchestrates the sequence explicitly for architectures with pre-existing stubs.

Why does TDD loop execution require architecture stubs before starting?▼

Architecture stubs are required because the TDD loop applies to architectures with pre-existing stubs from Step 2. This ensures the test-first workflow targets established structures within your package.