refactor-bdd

What problem does it solve?

Over time, BDD scenarios, step definitions, and feature code can accumulate technical debt, reducing clarity and maintainability, even if scenarios still pass.

Core Features & Use Cases

• Multi-Layer Refactoring: Improves quality across Gherkin scenarios, step definitions, and the underlying feature implementation.
• Tech Debt Pruning: Actively removes unused steps, simplifies complex logic, and eliminates duplication, enforcing "No Legacy Baggage."
• Scenario Integrity: Ensures all BDD scenarios continue to pass after refactoring, maintaining behavioral correctness.
• Use Case: After implementing a feature and making all BDD scenarios pass, invoke this skill to refactor the Gherkin files (e.g., using Backgrounds), optimize step definitions for reusability, and clean up the feature code, all while verifying scenarios remain green.

Quick Start

Refactor the BDD implementation for REQ-ID 'UserLogin', including scenarios in 'authentication.feature' and step definitions, ensuring all scenarios still pass.