@sandrinio/vbounce 1.3.1 → 1.3.2

package/brains/claude-agents/developer.md

@@ -21,6 +21,11 @@ Implement features and fix bugs as specified in Story documents. You write code
 
 ## During Implementation
 
+**You MUST follow the Test-Driven Development (TDD) Red-Green-Refactor cycle:**
+1. **Red (Write Failing Tests):** Before writing any implementation logic, write an automated test file (e.g., Jest, React Testing Library) that explicitly covers the Gherkin scenarios defined in `§2 The Truth`. Run it to prove it fails.
+2. **Green (Write Implementation):** Write the minimum code required to make your tests pass.
+3. **Refactor:** Clean up the code for readability and architecture without breaking the tests.
+
 - **Follow the Safe Zone.** Do not introduce new patterns, libraries, or architectural changes.
 - **No Gold-Plating.** Implement exactly what the Story specifies. Extra features are defects, not bonuses.
 - **Track your Correction Tax.** Note every point where you needed human intervention or made a wrong turn.
@@ -41,6 +46,7 @@ You MUST include the YAML frontmatter block exactly as shown below:
 ---
 status: "implemented"
 correction_tax: {X}
+tests_written: {number of tests generated}
 files_modified:
   - "path/to/file.ts"
 lessons_flagged: {number of lessons}
@@ -66,6 +72,7 @@ lessons_flagged: {number of lessons}
 
 ## Status
 - [ ] Code compiles without errors
+- [ ] Automated tests were written FIRST (Red) and now pass (Green)
 - [ ] LESSONS.md was read before implementation
 - [ ] ADRs from Roadmap §3 were followed
 - [ ] No new patterns or libraries introduced

package/brains/claude-agents/qa.md

@@ -36,10 +36,12 @@ Analyze the specific changes from the Developer:
   5. **Test Quality** — would tests break if logic changed?
   6. **Coupling** — can you change one thing without breaking five?
 
-### Acceptance Criteria Validation
-Run Story §2.1 Gherkin scenarios against the implementation:
-- Each scenario is a binary pass/fail
-- Document exact failure conditions (input, expected, actual)
+### Test Execution & Fidelity
+Run Story §2.1 Gherkin scenarios against the Developer's automated test suite:
+- **Did the Developer actually write tests?** If `tests_written: 0` in their report, the bounce FAILS automatically. TDD is mandatory.
+- **Do the tests pass?** If the Developer's test suite fails when executed (or if there are compilation errors), the bounce FAILS.
+- Each scenario is a binary pass/fail based on test coverage.
+- Document exact failure conditions (input, expected, actual).
 
 ### Spec Fidelity Check
 After running scenarios, verify:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sandrinio/vbounce",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "description": "V-Bounce OS: Turn your AI coding assistant into a full engineering team through structured SDLC skills.",
   "type": "module",
   "bin": {
@@ -46,4 +46,4 @@
     "js-yaml": "^4.1.1",
     "marked": "^17.0.3"
   }
-}
+}

package/scripts/validate_report.mjs

@@ -14,7 +14,7 @@ import yaml from 'js-yaml';
 
 // Defined schemas for each report type
 const SCHEMAS = {
-    dev: ['status', 'correction_tax', 'files_modified', 'lessons_flagged'],
+    dev: ['status', 'correction_tax', 'tests_written', 'files_modified', 'lessons_flagged'],
     qa: {
         base: ['status', 'bounce_count', 'bugs_found', 'gold_plating_detected'],
         conditional: { 'FAIL': ['failed_scenarios'] }

package/templates/story.md

@@ -109,6 +109,9 @@ Feature: {Story Name}
 > Instructions for the Developer Agent. The "How".
 > Target Audience: Developer Agent (with react-best-practices + lesson skills).
 
+### 3.0 Test Implementation
+- {Identify which test suites need to be created or modified to cover the Acceptance Criteria from §2.1. e.g. "Create `AuthComponent.test.tsx`"}
+
 ### 3.1 Context & Files
 | Item | Value |
 |------|-------|
@@ -142,7 +145,7 @@ POST /api/resource
 
 ## 4. Definition of Done (The Gate)
 - [ ] Code compiles without errors.
-- [ ] New Unit Tests are written and passing.
+- [ ] Unit/Integration Tests were written FIRST (Red), and now pass (Green).
 - [ ] All Acceptance Criteria (§2.1) pass.
 - [ ] Linting rules passed.
 - [ ] LESSONS.md consulted before implementation.