gormes-tdd-slice

Prove a single Gormes behavior with red-green-refactor tests.

9|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-tdd-slice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gormes-tdd-slice
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/gormes-tdd-slice
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-tdd-slice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to drive reliable software changes by focusing on a single Gormes behavior and validating it through a red-green-refactor loop, preventing scope creep and flaky releases.

Core Features & Use Cases

  • Narrow-behavior TDD cycles that bound changes to a single feature surface.
  • Structured workflow aligning tests with public interfaces, Hermes parity references, and iterative refinement.
  • Use Case: when validating a small UI or tool behavior in Gormes, ensuring it meets observable contracts before broader integration.

Quick Start

Select one Gormes behavior, write a failing test, and iterate until the test passes.

Frequently Asked Questions about gormes-tdd-slice

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

FAQPage Schema
How do I use TDD to validate a single behavior and prevent scope creep?

Test-driven development validates a single behavior by bounding changes to a focused feature surface. You write a failing test demonstrating the target behavior, run focused tests, and refactor until green to lock in the observable contract.

What is the best way to align tests with public interfaces during a red-green-refactor cycle?

The best way to align tests with public interfaces during a red-green-refactor cycle is to operate on a focused behavior scope. This structured workflow verifies expected outcomes against parity references before broader integration.

When do I need focused TDD cycles for UI or tool behavior validation?

You need focused TDD cycles for UI or tool behavior validation when ensuring a small feature surface meets observable contracts. This process prevents flaky releases by bounding changes to a single behavior before broader integration.

How do I prove a single behavior contract using red-green-refactor testing?

Prove a single behavior contract by defining a RED test that demonstrates the target behavior. Run focused tests against parity references and iteratively refactor the implementation until the test passes green.

Does TDD workflow require parity references to verify expected outcomes?

TDD workflow requires parity references to verify expected outcomes and validate public interfaces. These references ensure the focused test path accurately aligns with the observable contract during the red-green-refactor loop.