tdd-feature-dev

Name: tdd-feature-dev
Availability: InStock
Author: foo-x

Parse Markdown requirements and execute the Red-Green-Refactor cycle.

2|1|Updated Feb 2, 2019

Search Tags:#testing #tdd #markdown #refactoring #feature development #requirements

Ready to run

npx skills add https://github.com/Foo-x/dotfiles --skill tdd-feature-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-feature-dev
Source: https://github.com/Foo-x/dotfiles/tree/main/claude/skills/tdd-feature-dev
Command: npx skills add https://github.com/Foo-x/dotfiles --skill tdd-feature-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates feature development and modification using Test-Driven Development (TDD) directly from Markdown requirement documents, ensuring code quality and adherence to specifications.

Core Features & Use Cases

Automated TDD Workflow: Guides the user through the Red-Green-Refactor cycle.
Requirement Parsing: Extracts functional requirements and acceptance criteria from Markdown files.
Test Scenario Generation: Creates detailed test cases, including edge cases and boundary values.
Use Case: Develop a new user authentication module by providing a user-auth.md requirement document, and let the skill generate tests, implement the code, and ensure all criteria are met.

Quick Start

Use the tdd-feature-dev skill to develop features based on the requirements in docs/requirements/user-auth.md.

Frequently Asked Questions about tdd-feature-dev

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

FAQPage Schema

How do I implement feature development using TDD from Markdown requirements?▼

Feature development using TDD from Markdown requirements involves parsing functional criteria from the document, generating test scenarios, and executing the Red-Green-Refactor cycle. This ensures code adheres strictly to specifications.

Can I automate test scenario generation from Markdown requirement documents?▼

Automating test scenario generation from Markdown requirement documents extracts acceptance criteria to create detailed test cases. This includes edge cases and boundary values to validate feature modifications thoroughly.

What is the best way to refactor existing features following TDD principles?▼

Refactoring existing features following TDD principles utilizes a structured Red-Green-Refactor cycle. This approach ensures modifications meet functional requirements without breaking existing test scenarios.

Does this TDD workflow work for modifying existing code or only new features?▼

This TDD workflow works for both implementing new features and modifying existing ones. It parses Markdown requirements to guide the Red-Green-Refactor cycle regardless of the codebase's current state.

How do I handle edge cases and boundary values in test-driven development?▼

Handling edge cases and boundary values in test-driven development is managed through automated test scenario generation. The workflow parses Markdown requirements to extract these specific criteria for comprehensive coverage.

Why use Markdown documents for TDD requirements and test generation?▼

Using Markdown documents for TDD requirements provides structured parsing of functional criteria and acceptance tests. This ensures the generated test scenarios align directly with the specified feature development goals.