skills.rest
reckerswartz
reckerswartzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tdd-red

Draft failing RSpec specs before code for Rails projects.

Updated Mar 19, 2026
Search Tags:#workflow#testing#tdd#rails#rspec#spec-first
One-click install
npx skills add https://github.com/reckerswartz/resume_builder --skill tdd-red-reckerswartz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-red
Source: https://github.com/reckerswartz/resume_builder/tree/main/.devin/skills/tdd-red
Command: npx skills add https://github.com/reckerswartz/resume_builder --skill tdd-red-reckerswartz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing tests before production code is the cornerstone of TDD. This skill guides practitioners through the RED phase by drafting focused, failing RSpec specs prior to implementation, ensuring a clear spec-driven contract.

Core Features & Use Cases

  • Define and maintain a deterministic RED-Green-Refactor cycle tailored for Rails/RSpec projects.
  • Enforce one-test-at-a-time discipline with explicit naming and targeted failure causes.
  • Include a Git Sync Gate to keep main in a safe, retrievable state and promote disciplined commits.

Quick Start

Draft a failing spec for the feature, then run the rspec suite to observe the failure and drive implementation.

Frequently Asked Questions about tdd-red

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

FAQPage Schema
How do I write failing RSpec specs before implementing Rails code?▼

To write failing RSpec specs before implementation, draft a focused spec defining the expected behavior, then run the RSpec suite to observe the failure and drive implementation. This enforces a spec-first contract and a deterministic RED-Green-Refactor cycle.

What is the RED phase in test-driven development for Rails?▼

The RED phase in test-driven development is drafting focused, failing RSpec specs prior to writing production code. It establishes a clear spec-driven contract, ensuring one-test-at-a-time discipline before moving to the GREEN phase.

Does this TDD workflow enforce one-test-at-a-time discipline with Git?▼

Yes, this TDD workflow enforces one-test-at-a-time discipline through a mandatory Git Sync Gate. This gate keeps the main branch in a safe, retrievable state and promotes disciplined commits after each failing spec is drafted.

Can I use this spec-first workflow with existing Rails RSpec projects?▼

Yes, you can use this spec-first workflow with existing Rails RSpec projects. It applies project-specific patterns to maintain a deterministic RED-Green-Refactor cycle tailored for your current testing conventions.

What's the best way to automate the RED phase of the TDD cycle in RSpec?▼

The best way to automate the RED phase in RSpec is using a guided workflow that drafts targeted failing specs with explicit naming and failure causes. This ensures a deterministic spec-driven contract before implementation begins.

Related Skills

Explore More Software Engineering Skills→
erwaenerwaen

scaffold-model

Generate Rails model scaffolds with migration, validations, associations, scopes, and RSpec specs.

Community
Advanced
kckylechen1kckylechen1

test-driven-development

Enforce failing tests before implementing production code via Red-Green-Refactor.

Community
Intermediate
vonchristianvonchristian

test-driven-development

Enforce red-green-refactor TDD workflows in Rails applications using RSpec.

Community
Intermediate
rhussrhuss
107

implement

Generate implementation plans and TDD cycles from validated specifications.

Community
Basic