specweave 1.0.335 → 1.0.337

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specweave",
-  "version": "1.0.335",
+  "version": "1.0.337",
   "description": "Spec-driven development framework for AI coding agents. Works with Claude Code, Codex, Antigravity, Cursor, Copilot & more. 100+ skills, 49 CLI commands, verified skill certification, autonomous execution, and living documentation.",
   "type": "module",
   "main": "dist/index.js",

package/src/templates/AGENTS.md.template

@@ -51,7 +51,9 @@ See **Task Format** and **User Story Format** sections for templates.
 
 Never mark a task complete without proving it works:
 - Code compiles/builds successfully
-- Tests pass
+- Run tests: `npx vitest run` (unit) + `npx playwright test` (E2E) after every task
+- For critical paths: `/sw:grill` for quality, `/sw:judge-llm` for independent validation
+- Ask user to manually verify: new UI flows, auth, payments, data migrations
 - Acceptance criteria actually satisfied
 - Ask: "Would a staff engineer approve this?"
 
@@ -105,6 +107,12 @@ Good: npm run build → node script.js → Success
 - Verify plan covers all ACs and edge cases before implementation
 - If the plan has gaps, fix the plan first — don't discover them mid-coding
 - Re-read the plan between tasks to stay aligned
+
+### Test Before Ship
+- Tests pass at every step — unit after each task, E2E before close, no exceptions
+- `/sw:test-aware-planner` generates BDD test plans during design — verify they exist before `/sw:do`
+- TDD cycle: `/sw:tdd-red` → `/sw:tdd-green` → `/sw:tdd-refactor`
+- E2E with Playwright CLI (`npx playwright test`) is a blocking closure gate
 <!-- /SECTION -->
 
 ---
@@ -348,17 +356,27 @@ specweave context projects
 4. Create `spec.md` — every US needs `**Project**:` field (see User Story Format)
 5. Create `tasks.md` (task checklist with BDD tests)
 6. Optional: `plan.md` for complex features
+7. **Verify** tasks.md has `**Test Plan**:` for every task with testable ACs
+8. **Verify** E2E scenarios exist for user-facing user stories — re-run `/sw:test-aware-planner` if missing
 
 ### Completing Tasks
 1. Implement the task
-2. Update tasks.md: `[ ] pending` → `[x] completed`
-3. Update spec.md: check off satisfied ACs
-4. Sync to external trackers if enabled
+2. Run unit tests: `npx vitest run`
+3. Run E2E tests (if task touches UI/API): `npx playwright test`
+4. Only mark task `[x]` after tests pass
+5. Update tasks.md: `[ ] pending` → `[x] completed`
+6. Update spec.md: check off satisfied ACs
+7. Sync to external trackers if enabled
+8. If 3 consecutive test failures: STOP, re-plan, ask user
 
 ### Closing Increment
-1. `/sw:done 0001` — PM validates 3 gates (tasks, tests, docs)
-2. Living docs synced automatically
-3. GitHub/Jira issue closed if enabled
+1. Full test suite: `npx vitest run` (all unit + integration)
+2. Full E2E suite: `npx playwright test` (all scenarios)
+3. Coverage check: `npx vitest run --coverage` (must meet targets in config.json)
+4. Ask user for manual acceptance: new UI, auth, payments, data migrations
+5. `/sw:done 0001` — PM validates 3 gates (tasks, tests, docs)
+6. Living docs synced automatically
+7. GitHub/Jira issue closed if enabled
 <!-- /SECTION -->
 
 ---

package/src/templates/CLAUDE.md.template

@@ -77,8 +77,10 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 
 ### 3. Verification Before Done
 - Never mark a task complete without proving it works
+- Run tests: `npx vitest run` (unit) + `npx playwright test` (E2E) after every task
+- For critical paths: `/sw:grill` for quality, `/sw:judge-llm` for independent validation
+- Ask user to manually verify: new UI flows, auth, payments, data migrations
 - Ask yourself: **"Would a staff engineer approve this?"**
-- Run tests, check logs, demonstrate correctness
 
 ### 4. Think-Before-Act (Dependencies)
 **Satisfy dependencies BEFORE dependent operations.**
@@ -184,9 +186,29 @@ Primary: `/sw:progress-sync`. Individual: `/sw-github:push`, `/sw-github:close`.
 <!-- /SECTION -->
 
 <!-- SECTION:testing -->
-## Testing
+## Testing Pipeline (MANDATORY)
 
-BDD in tasks.md | Unit >80% | `.test.ts` (Vitest) | ESM mocking: `vi.hoisted()` + `vi.mock()`
+**Testing is a pipeline step, not an afterthought.**
+
+### During Design (`/sw:increment`)
+- `/sw:test-aware-planner` generates tasks.md with BDD test plans (Given/When/Then) for every AC
+- Every task MUST have a `**Test Plan**:` block before implementation begins
+- E2E test scenarios MUST be specified for user-facing features
+
+### During Implementation (`/sw:do`)
+- TDD cycle: `/sw:tdd-red` → `/sw:tdd-green` → `/sw:tdd-refactor`
+- Run tests after EVERY task: `npx vitest run` (unit) + `npx playwright test` (E2E when applicable)
+- Never mark a task `[x]` until its tests pass
+
+### Before Closing (`/sw:done`)
+- `/sw:grill` + `/sw:validate` — code quality + 130+ rule checks
+- E2E with Playwright CLI: `npx playwright test` (blocking gate)
+- Ask user for manual acceptance testing when: new UI flows, auth changes, payment flows, data migrations
+
+### Test Stack
+- Unit/Integration: Vitest (`.test.ts`), ESM mocking with `vi.hoisted()` + `vi.mock()`
+- E2E: Playwright CLI (`npx playwright test`)
+- Coverage targets: unit 95%, integration 90%, e2e 100% of AC scenarios
 <!-- /SECTION -->
 
 <!-- SECTION:tdd -->
@@ -231,6 +253,7 @@ Plugins load automatically. Manual: `vskill install --repo anton-abyzov/vskill -
 4. **No Laziness**: Root causes, senior standards
 5. **DRY**: Don't Repeat Yourself — flag and eliminate repetitions aggressively
 6. **Plan Review**: Review the plan thoroughly before making any code changes
+7. **Test before ship**: Tests pass at every step — unit after each task, E2E before close, no exceptions
 <!-- /SECTION -->
 
 <!-- SECTION:linking -->