refine-requirements

What problem does it solve?

Requirements are rarely perfect upfront; developers often discover edge cases or missing business rules during implementation, which need to be fed back into the requirements.

Core Features & Use Cases

• Requirements Refinement Loop: Captures discoveries (edge cases, race conditions, missing rules) made during TDD/BDD implementation.
• Automated Documentation Update: Updates requirement documents with new BR-, C-, or F-* specifications, including discovery metadata.
• Knowledge Capture: Ensures developer insights become permanent, preventing re-discovery by future teams.
• Use Case: During the GREEN phase of TDD, a developer discovers a race condition for user registration. This skill documents the new business rule (BR-015), updates the requirement, adds a test, and modifies the code to handle it.

Quick Start

Refine the 'User Registration' requirement (REQ-F-USER-001) by adding a new business rule (BR-015) for concurrent registration prevention, based on a discovery during TDD.