test-driven-dev

Implement test-first development for user-facing behavior with integration and end-to-end tests.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/dformoso/positronic --skill test-driven-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-dev
Source: https://github.com/dformoso/positronic/tree/main/skills/implementing/test-driven-dev
Command: npx skills add https://github.com/dformoso/positronic --skill test-driven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexity and time-consuming nature of Test-Driven Development (TDD) by providing a structured and efficient workflow for developers seeking to implement an already-scoped issue or SPEC slice using TDD.

Core Features & Use Cases

  • Behavior-Driven Testing: Focuses on user-facing behavior rather than implementation details.
  • Vertical Slicing: Ensures a test-first approach without overwhelming the developer.
  • Refactoring and Clean Code: Encourages clean code practices through refactoring and SOLID principles.
  • Use Case: A developer implementing a feature in a software project, looking to follow TDD principles without being bogged down by overly complex test setup.

Quick Start

Implement TDD by executing the 'tdd' command after defining your project requirements.

Frequently Asked Questions about test-driven-dev

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

FAQPage Schema
How do I start test-driven development without getting bogged down by complex test setup?

Test-driven development is streamlined through a structured, test-first workflow that uses vertical slicing to implement already-scoped issues efficiently, removing unnecessary complexity from the setup process.

What is behavior-driven testing in TDD?

Behavior-driven testing in TDD focuses on validating user-facing behavior rather than internal implementation details, ensuring the software functions correctly from the end-user perspective while maintaining clean code practices.

Does this TDD workflow support both automated and manual tests?

Yes, the TDD workflow supports both automated and manual tests, placing a strong emphasis on integration and end-to-end testing to verify user-facing behavior within the test-driven development framework.

Can I use this approach to refactor code and apply SOLID principles?

Yes, you can use this approach to refactor code and apply SOLID principles, as the test-first workflow actively encourages clean code practices through structured refactoring during the development process.

When should I use vertical slicing in test-driven development?

Vertical slicing should be used when implementing an already-scoped issue or SPEC slice using TDD, ensuring a test-first approach without overwhelming the developer during the feature implementation process.