tdd-test-writer

Convert user requests into acceptance criteria and RED-phase test plans.

13|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/eng-cc/oasis7 --skill tdd-test-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-test-writer
Source: https://github.com/eng-cc/oasis7/tree/main/.agents/skills/tdd-test-writer
Command: npx skills add https://github.com/eng-cc/oasis7 --skill tdd-test-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams define explicit behavior contracts via tests before implementing code, enabling reliable test-driven development and clearer expectations.

Core Features & Use Cases

  • Define happy-path behavior and edge cases with concrete tests.
  • Delegate RED-phase test authoring to a dedicated subagent when available.
  • Produce a precise implementation handoff with verification criteria and regression coverage.
  • Reuse existing test conventions and integrate with project-specific frameworks.

Quick Start

Provide a user request and let the skill generate a RED-phase test plan and delegate test authoring to the tdd_test_writer subagent.

Frequently Asked Questions about tdd-test-writer

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

FAQPage Schema
How do I define a testable behavior contract before writing implementation code?

A behavior contract defines explicit acceptance criteria covering the happy path, edge cases, and negative expectations before implementation begins. This approach drives comprehensive test coverage and establishes clear expectations for reliable test-driven development.

How to start test-driven development by generating RED-phase tests from a feature request?

Provide a user request to generate a RED-phase test plan that identifies happy path and edge cases. The skill delegates test authoring to a subagent, which writes failing tests and returns a precise implementation handoff with verification commands.

Does test-driven development work with my existing project test conventions and frameworks?

Yes, the skill reuses existing test conventions and integrates with project-specific frameworks. It generates RED-phase tests based on your current testing setup rather than imposing a new framework, ensuring the behavior contract aligns with your established conventions.

What's the best way to identify edge cases and negative expectations for test coverage?

Convert user requests into explicit acceptance criteria that systematically map the happy path, edge cases, and negative expectations. This structured approach ensures comprehensive test coverage by identifying behaviors that need testing before implementation begins.

What implementation handoff do I get after authoring RED-phase tests?

You receive a precise implementation handoff with verification commands and regression coverage details. This handoff connects the failing RED-phase tests to the next development step, ensuring implementation satisfies the defined behavior contract.