rb-implement-with-tests

Implement bounded software changes with behavioral tests and failure-path analysis.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/richardmbailey/rb-skills --skill rb-implement-with-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rb-implement-with-tests
Source: https://github.com/richardmbailey/rb-skills/tree/main/rb-implement-with-tests
Command: npx skills add https://github.com/richardmbailey/rb-skills --skill rb-implement-with-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent code quality and regression risks during software implementation by enforcing a rigorous, test-first, and review-driven workflow for bounded changes.

Core Features & Use Cases

  • Automated Behavioural Verification: Ensures every change is backed by unit, integration, or contract tests before completion.
  • Failure-Path Coverage: Mandates the inclusion of negative and boundary cases to prevent edge-case regressions.
  • Review-Fix Loop: Integrates a final review and fix cycle to ensure code meets quality standards before the task is marked complete.
  • Use Case: When tasked with fixing a bug in a payment processing module, this skill guides the agent to write a failing regression test, implement the fix, verify the happy path, and ensure no side effects occur in related components.

Quick Start

Use the rb-implement-with-tests skill to implement the requested feature by following the defined test-driven development and review procedure.

Frequently Asked Questions about rb-implement-with-tests

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

FAQPage Schema
How do I implement code changes with automated regression testing?

Implement code changes with automated regression testing by following a structured workflow that enforces test-driven development, failure-path analysis, and a final review cycle to prevent edge-case regressions. This ensures every change is backed by verified tests.

What is the best way to enforce test-driven development for bug fixes?

The best way to enforce test-driven development for bug fixes is to mandate a workflow where a failing regression test is written first, the fix is implemented, and negative boundary cases are verified before marking the task complete.

How does failure-path analysis prevent edge-case regressions?

Failure-path analysis prevents edge-case regressions by mandating the inclusion of negative and boundary test cases during software implementation, ensuring that unexpected inputs and error states are verified before code changes are completed.

Can I use this TDD workflow for ordinary coding tasks and feature additions?

Yes, you can use this TDD workflow for ordinary coding tasks, bug fixes, and feature additions that require verified increments, CI-equivalent validation, and strict adherence to existing repository patterns.

Does this implementation workflow require specific testing frameworks?

No, this implementation workflow does not require specific testing frameworks. It applies behavioural testing, failure-path analysis, and a review-fix loop to ensure automated test coverage regardless of the underlying framework, operating without external dependencies.