Skill

vcsdd-impl

Implements VCSDD Phase 2b (Green): minimal code via vcsdd-builder to pass failing tests; Phase 2c (Refactor): improves code while keeping tests green; logs npm test evidence. Use after Phase 2a.

Javascript

Node

Bash

testing

code-quality

npx claudepluginhub sc30gsw/vcsdd-claude-code --plugin vcsdd

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Runs the Green phase (Phase 2b) and Refactor phase (Phase 2c). Implements minimal code to pass all failing tests, then refactors while keeping tests green.

SKILL.md

Similar Skills

vcsdd-tdd

Generates failing tests for VCSDD feature spec requirements in Red phase (2a). Invokes builder, runs tests, records failure evidence and regression baseline. Supports vitest/pytest.

vcsdd

test-driven-development

Enforces rigorous Test-Driven Development (TDD) via RED-GREEN-REFACTOR cycle. Requires failing tests before any production code when implementing features or fixing bugs.

rpikit

tdd-process

276

Enforces strict TDD state machine with planning-red-green-refactor-verify cycles. Requires state prefix on every message for test-first development discipline.

1 file

development-skills

Stats

Stars16

Forks0

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

What

Runs the Green phase (Phase 2b) and Refactor phase (Phase 2c). Implements minimal code to pass all failing tests, then refactors while keeping tests green.

When

Run after /vcsdd-tdd completes Phase 2a with red phase evidence. Requires active feature at phase 2a.

How

Phase 2b (Green)

Transition to 2b
Read failing tests: understand what each test requires
Invoke vcsdd-builder agent to implement:
- Minimum code to make each failing test pass
- Follow spec requirements exactly - no extra features
- Stay within the purity boundary defined in Phase 1b
Create implementation beads: one per implemented function, linked to test-case beads

Run tests and verify ALL pass:

npm test 2>&1 | tee .vcsdd/features/<name>/evidence/sprint-N-green-phase.log

Record green phase evidence with explicit markers at the top of the log:
```
target-feature-tests: PASS
regression-baseline: PASS
```
Append the raw passing output after those markers so Phase 3 can prove both signals

Phase 2c (Refactor)

Transition to 2c
Invoke vcsdd-builder agent to refactor:
- Eliminate code duplication
- Improve naming clarity
- Extract functions with clear responsibilities
- Do NOT add features, change behavior, or modify spec
Verify tests still pass after each refactor step
Refresh green evidence after the final refactor run, again including target-feature-tests: PASS and regression-baseline: PASS, so Phase 3 sees post-refactor test results
In strict mode, update the sprint contract in contracts/sprint-N.md so it reflects the final refactored artifact set, then run /vcsdd-contract-review before /vcsdd-adversary

Examples

/vcsdd-impl