refine-requirements

Refining requirements from TDD discoveries automates capturing edge cases, race conditions, and business rules found during implementation. The skill records discovery metadata (phase, discoverer, impact) and generates updated BR-*, C-*, and F-* requirement items with traceability, ensuring developer insights integrate into formal specifications without manual re-documentation.

Document race conditions during the GREEN phase of TDD when you've verified the issue through testing. This skill captures the discovery as a new business rule (e.g., BR-015), updates the requirement baseline, adds corresponding test cases, and modifies code—creating a complete feedback loop that prevents future re-discovery by other teams.

This skill requires an existing requirement baseline as input. It's designed to refine and extend established BR-*, C-*, and F-* specifications with developer-discovered rules rather than create requirements from scratch. Start with documented baseline requirements before applying refinement.

Both TDD and BDD cycles trigger refinement—the skill applies during either testing methodology to capture discoveries. BDD's scenario-driven approach and TDD's unit-level focus both surface edge cases and missing rules; refinement automates documenting these into updated specifications regardless of which testing discipline you use.

The skill produces updated requirement documents with new BR-*, C-*, or F-* items, discovery metadata (phase, discoverer, impact), and traceability mappings to implementation code and tests. Output artifacts are testable and formally integrated into your SDLC baseline for downstream phases.

Yes. The skill integrates into TDD/BDD cycles where test failures or edge-case discoveries trigger refinement. It automates the capture-and-document process, feeding test insights directly into updated BR-*, C-*, and F-* specifications with traceability, closing the feedback loop between testing and requirements management.