sdlc-workflow 1.2.3 → 1.2.6

package/bin/cli.js

@@ -263,7 +263,7 @@ globs: docs/sdlc/**/*, **/*.md
 5. **Technical BA** — API specs, team breakdown → docs/sdlc/ba/technical/
 6. **QE (docs)** — Test plan, test cases → docs/sdlc/qe/{epic-slug}/ (one folder per epic)
 7. **Dev** — After docs phase → **run implementation immediately**. Tech Lead (highest model: planning, logic, review) + implementation roles (cost-efficient model: code execution) → docs/sdlc/dev/{role}/
-8. **QE (testing + UAT)** — QE Lead + Senior QE + UAT; **bug-fix loop** (bugs → Dev fix → QE retest) until 0 bugs → docs/sdlc/qe/{epic-slug}/
+8. **QE (testing + UAT)** — QE Lead (highest model: strategy, review) + Senior QE (cost-efficient model: test execution) + UAT; **bug-fix loop** (bugs → Dev fix → QE retest) until 0 bugs → docs/sdlc/qe/{epic-slug}/
 9. **Security** — Audit security risk → docs/sdlc/security/
 10. **Principle Engineer** — Audit logic, architecture → docs/sdlc/principle-engineer/
 11. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/ (after Security + PE sign-off; fix → retest → re-audit loop until 0 issues)
@@ -371,7 +371,7 @@ User Request → PO → Business BA → Design (if app/web) → Architect → Te
 
 **Model optimization**: Tech Lead uses the **highest-tier model** (e.g. Claude Opus) for planning, architecture decisions, logic analysis, and code review. Implementation roles use a **cost-efficient model** (e.g. Claude Haiku) to execute code from Tech Lead's specs. This maximizes quality on critical thinking while reducing cost on execution.
 
-**Requirements**: Unit Test coverage **≥ 90%** (TDD/BDD); Clean Code, SOLID, DRY, KISS, SoC, POLS.
+**Requirements**: Unit Test coverage **100%** (TDD/BDD); Clean Code, SOLID, DRY, KISS, SoC, POLS.
 
 **Output**: Code + unit tests. **Handoff to QE (testing + UAT).**
 
@@ -381,8 +381,8 @@ User Request → PO → Business BA → Design (if app/web) → Architect → Te
 **Role**: Write and run **automation tests** + **UAT**, sign-off.
 
 **Roles**:
-- **QE Lead (15+ yrs automation)**: Test strategy, framework choice, automation architecture, review test code. Output per epic: \`docs/sdlc/qe/{epic-slug}/\`
-- **Senior QE (10+ yrs)**: Write automation tests per QE Lead's strategy. Output per epic: \`docs/sdlc/qe/{epic-slug}/\` (e.g. automation/ or test files there)
+- **QE Lead (15+ yrs automation)** — **highest model** (e.g. Opus): Test strategy, framework choice, automation architecture, review test code. Output per epic: \`docs/sdlc/qe/{epic-slug}/\`
+- **Senior QE (10+ yrs)** — **cost-efficient model** (e.g. Haiku): Write automation tests per QE Lead's strategy. Output per epic: \`docs/sdlc/qe/{epic-slug}/\` (e.g. automation/ or test files there)
 - **UAT**: Verify implementation against original user stories and acceptance criteria from PO.
 
 **Bug-fix loop**: If QE finds bugs or test failures → **Dev fixes** → **QE retests**. **Repeat until all tests pass and UAT approved (0 open bugs).** Only then → **Handoff to Security + Principle Engineer.**
@@ -413,7 +413,7 @@ User Request → PO → Business BA → Design (if app/web) → Architect → Te
 | 4 | Architect | ADRs, system diagrams, security by design |
 | 5 | Technical BA | API specs, tech breakdown |
 | 6 | QE (docs) | Test plan, test cases |
-| 7 | Dev | Code, unit tests (≥90%), security shift-left |
+| 7 | Dev | Code, unit tests (100%), security shift-left |
 | 8 | QE (testing + UAT) | Automation, UAT; **bug-fix loop** (QE finds bugs → Dev fix → QE retest) until 0 open bugs |
 | 9 | Security + PE | Audit; **fix → retest → re-audit loop** (Dev fix → QE retest → re-audit) until 0 issues; sign-off → Deploy |
 | 10 | Deploy | Docker Compose + K8s |
@@ -452,12 +452,12 @@ Design specs (Markdown) + optional HTML wireframes from idea + PO + BA (before A
 TC-001: [Scenario] — Precondition, Steps, Expected, Links to AC
 
 ## QE Team (one folder per epic: qe/{epic-slug}/)
-- QE Lead (15+ yrs automation): test strategy, framework, automation architecture, review → docs/sdlc/qe/{epic-slug}/
-- Senior QE (10+ yrs): write automation tests → docs/sdlc/qe/{epic-slug}/
+- QE Lead (15+ yrs automation) — **highest model** (e.g. Opus): test strategy, framework, automation architecture, review → docs/sdlc/qe/{epic-slug}/
+- Senior QE (10+ yrs) — **cost-efficient model** (e.g. Haiku): write automation tests per QE Lead's strategy → docs/sdlc/qe/{epic-slug}/
 
 ## Dev Team
 - Tech Lead (15+ yrs) — **highest model** (e.g. Opus): planning, logic, architecture decisions, code review → docs/sdlc/dev/tech-lead/
-- Senior Dev (10+ yrs) — **cost-efficient model** (e.g. Haiku): execute code from Tech Lead specs, Unit Test ≥90% → docs/sdlc/dev/senior-developer/
+- Senior Dev (10+ yrs) — **cost-efficient model** (e.g. Haiku): execute code from Tech Lead specs, Unit Test 100% → docs/sdlc/dev/senior-developer/
 - By project (all Senior 10+ yrs, cost-efficient model): Senior Frontend, Backend, Mobile, Embedded, Data/ML, Platform → docs/sdlc/dev/{role}/
 
 ## Security + Principle Engineer (after implementation)
@@ -487,7 +487,7 @@ When working on requirements, features, or handoffs, follow these phases:
 5. **Technical BA** — API specs, team breakdown → docs/sdlc/ba/technical/
 6. **QE (docs)** — Test plan, test cases → docs/sdlc/qe/{epic-slug}/ (one folder per epic)
 7. **Dev** — After docs phase → **run implementation immediately**. Tech Lead (highest model: planning, logic, review) + Senior Dev (cost-efficient model: code execution) → docs/sdlc/dev/{role}/
-8. **QE (testing + UAT)** — QE Lead + Senior QE + UAT; **bug-fix loop** (bugs → Dev fix → QE retest) until 0 bugs → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
+8. **QE (testing + UAT)** — QE Lead (highest model: strategy, review) + Senior QE (cost-efficient model: test execution) + UAT; **bug-fix loop** (bugs → Dev fix → QE retest) until 0 bugs → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
 9. **Security + Principle Engineer** — Security + logic audit; **fix → retest → re-audit loop** (Dev fixes → QE retests → re-audit) until 0 issues; sign-off before Deploy
 10. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
 11. **Maintenance** — Monitoring, bug fixes, patches, dependency updates → docs/sdlc/maintenance/
@@ -508,7 +508,7 @@ const CLAUDE_SDLC_CONTENT = `## SDLC Workflow
 5. **Technical BA** — API specs, team breakdown → docs/sdlc/ba/technical/
 6. **QE (docs)** — Test plan, test cases → docs/sdlc/qe/{epic-slug}/ (one folder per epic)
 7. **Dev** — After docs phase → **run implementation immediately**. Tech Lead (highest model: planning, logic, review) + Senior Dev (cost-efficient model: code execution) → docs/sdlc/dev/{role}/. Clean Code, SOLID, DRY, KISS, TDD/BDD. Security shift-left: OWASP checks, dependency audit in CI
-8. **QE (testing + UAT)** — QE Lead + Senior QE + UAT; **bug-fix loop** (bugs → Dev fix → QE retest) until 0 bugs → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
+8. **QE (testing + UAT)** — QE Lead (highest model: strategy, review) + Senior QE (cost-efficient model: test execution) + UAT; **bug-fix loop** (bugs → Dev fix → QE retest) until 0 bugs → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
 9. **Security + Principle Engineer** — Security + logic audit; **fix → retest → re-audit loop** (Dev fixes → QE retests → re-audit) until 0 issues; sign-off before Deploy
 10. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
 11. **Maintenance** — Monitoring, bug fixes, patches, dependency updates → docs/sdlc/maintenance/
@@ -545,7 +545,7 @@ User Request → PO → Business BA → Design (if app/web) → Architect → Te
 | 4 | Architect | ADRs, system diagrams, security by design |
 | 5 | Technical BA | API specs, tech breakdown |
 | 6 | QE (docs) | Test plan, test cases |
-| 7 | Dev | Code, unit tests (≥90%), security shift-left |
+| 7 | Dev | Code, unit tests (100%), security shift-left |
 | 8 | QE (testing + UAT) | Automation, UAT; **bug-fix loop** (QE finds bugs → Dev fix → QE retest) until 0 open bugs |
 | 9 | Security + PE | Audit; **fix → retest → re-audit loop** (Dev fix → QE retest → re-audit) until 0 issues; sign-off → Deploy |
 | 10 | Deploy | Docker Compose + K8s |
@@ -585,7 +585,7 @@ User Request → PO → Business BA → Design (if app/web) → Architect → Te
 ### Phase 5b: Dev Teams
 - **Tech Lead (15+ yrs)**: Tech stack, review & merge, **security review (Shift Left)**: OWASP check, dependency audit, SAST in CI. Output: \`docs/sdlc/dev/tech-lead/\`
 - **Implementation roles** (all Senior 10+ yrs; use only what applies): Senior Dev, Senior Frontend, Senior Backend, Senior Mobile, Senior Embedded, Senior Data/ML, Senior Platform → \`docs/sdlc/dev/{role}/\`. See \`implementation-roles.template.md\`.
-- **Requirement**: Unit Test coverage **≥ 90%** (TDD/BDD); Clean Code, SOLID, DRY, KISS, SoC, POLS; security practices (input validation, no hardcoded secrets)
+- **Requirement**: Unit Test coverage **100%** (TDD/BDD); Clean Code, SOLID, DRY, KISS, SoC, POLS; security practices (input validation, no hardcoded secrets)
 - **Then**: QE starts testing phase
 
 ### Phase 6: QE (Testing — automation + UAT) → bug-fix loop
@@ -675,7 +675,7 @@ Every role in the SDLC runs as a **sub-agent**. Each phase is assigned to a corr
 | Technical BA | technical-ba | docs/sdlc/architecture/ + design (if any) | docs/sdlc/ba/technical/ |
 | QE (docs) | qe-docs | docs/sdlc/ba/technical/ (+ design if any) | docs/sdlc/qe/{epic-slug}/ (one folder per epic) |
 | Tech Lead | tech-lead | Technical spec | Review, merge, docs/sdlc/dev/tech-lead/ |
-| Senior Dev | senior-dev | Spec + test plan | After docs → run implementation immediately. Code, unit tests (≥90%) |
+| Senior Dev | senior-dev | Spec + test plan | After docs → run implementation immediately. Code, unit tests (100%) |
 | Senior Frontend | frontend | UI spec, API contract | Web UI, docs/sdlc/dev/frontend/ |
 | Senior Backend | backend | API spec, DB schema | API, services, docs/sdlc/dev/backend/ |
 | Senior Mobile | mobile | API contract, design | App (iOS/Android), docs/sdlc/dev/mobile/ |
@@ -1152,6 +1152,8 @@ Use test-case.template.md for test cases.
 
 const QE_LEAD_README = `# QE Lead (15+ years exp in test automation)
 
+> **Model**: Use the **highest-tier model** (e.g. Claude Opus) for this role. QE Lead handles test strategy, framework decisions, automation architecture, and review — tasks that require maximum reasoning capability.
+
 **Profile**: 15+ years of experience in test automation, test strategy, and quality engineering. Owns test automation strategy, framework selection, and quality gates across the project.
 
 **Responsibilities**:
@@ -1175,6 +1177,8 @@ const QE_LEAD_README = `# QE Lead (15+ years exp in test automation)
 
 const QE_SENIOR_README = `# Senior QE (10+ years exp)
 
+> **Model**: Use a **cost-efficient model** (e.g. Claude Haiku). Execute test implementation from QE Lead's strategy and specs.
+
 **Responsibilities**:
 - Write automation tests per test plan
 - Implement E2E, integration, regression tests
@@ -1327,7 +1331,7 @@ const DEV_SENIOR_README = `# Senior Developer (10+ years exp)
 
 **Responsibilities**:
 - Implement features per Tech Lead's implementation plan and Technical BA spec
-- Write code with Unit Test coverage **≥ 90%**
+- Write code with Unit Test coverage **100%**
 - Follow Tech Lead's tech decisions
 
 ## Detailed tasks
@@ -1335,7 +1339,7 @@ const DEV_SENIOR_README = `# Senior Developer (10+ years exp)
 - [ ] **Read Technical BA spec**: API, schema, team breakdown
 - [ ] **Implement feature**: Code per spec; follow Tech Lead stack. Adhere to: Clean Code, SOLID, DRY, KISS, SoC, LoD, CoI, GRASP, POLS
 - [ ] **Security practices (Shift Left)**: Input validation, parameterized queries, no hardcoded secrets, follow Architect's security ADR
-- [ ] **Unit tests (TDD/BDD)**: Coverage **≥ 90%**; TDD (write tests first) or BDD (behavior specs); edge cases, error paths, BSR (Behavior-Structure-Result)
+- [ ] **Unit tests (TDD/BDD)**: Coverage **100%**; TDD (write tests first) or BDD (behavior specs); edge cases, error paths, BSR (Behavior-Structure-Result)
 - [ ] **PR**: Lint, tests, security scan passing; request Tech Lead review
 - [ ] **Output**: Code + implementation notes in \`dev/senior-developer/\`
 `;
@@ -1385,7 +1389,7 @@ const DEV_FRONTEND_README = `# Senior Frontend (10+ years exp) — Web UI
 
 **Responsibilities**:
 - Implement web UI per design and API contract
-- Unit Test coverage **≥ 90%**
+- Unit Test coverage **100%**
 - Follow Tech Lead's stack (e.g. React, Vue, Angular)
 
 ## Detailed tasks
@@ -1393,7 +1397,7 @@ const DEV_FRONTEND_README = `# Senior Frontend (10+ years exp) — Web UI
 - [ ] **Read Technical BA spec**: API contract, design (if any)
 - [ ] **Implement components/screens**: Per spec; responsive, accessible
 - [ ] **API integration**: Fetch, state, error handling
-- [ ] **Unit tests (TDD/BDD)**: Components, hooks, utils — coverage **≥ 90%**; follow Clean Code, SOLID, DRY, KISS
+- [ ] **Unit tests (TDD/BDD)**: Components, hooks, utils — coverage **100%**; follow Clean Code, SOLID, DRY, KISS
 - [ ] **PR**: Lint, tests; Tech Lead review
 - [ ] **Output**: Code + component/integration docs in \`dev/frontend/\`
 `;
@@ -1404,7 +1408,7 @@ const DEV_BACKEND_README = `# Senior Backend (10+ years exp) — API, services
 
 **Responsibilities**:
 - Implement API, services, DB layer per Technical BA spec
-- Unit Test coverage **≥ 90%**
+- Unit Test coverage **100%**
 - Follow Tech Lead's stack
 
 ## Detailed tasks
@@ -1412,7 +1416,7 @@ const DEV_BACKEND_README = `# Senior Backend (10+ years exp) — API, services
 - [ ] **Read Technical BA spec**: API spec, DB schema
 - [ ] **Implement endpoints**: Per spec; validation, auth, error responses
 - [ ] **Implement DB layer**: Migrations, queries, transactions
-- [ ] **Unit tests (TDD/BDD)**: Services, controllers, DB — coverage **≥ 90%**; follow Clean Code, SOLID, DRY, KISS
+- [ ] **Unit tests (TDD/BDD)**: Services, controllers, DB — coverage **100%**; follow Clean Code, SOLID, DRY, KISS
 - [ ] **PR**: Lint, tests; Tech Lead review
 - [ ] **Output**: Code + API/DB implementation notes in \`dev/backend/\`
 `;
@@ -1423,7 +1427,7 @@ const DEV_MOBILE_README = `# Senior Mobile (10+ years exp) — iOS / Android / c
 
 **Responsibilities**:
 - Implement app UI and API integration per spec
-- Unit Test coverage **≥ 90%**
+- Unit Test coverage **100%**
 - Follow Tech Lead's stack (e.g. React Native, Flutter, native)
 
 ## Detailed tasks
@@ -1431,7 +1435,7 @@ const DEV_MOBILE_README = `# Senior Mobile (10+ years exp) — iOS / Android / c
 - [ ] **Read Technical BA spec**: API contract, screen flows
 - [ ] **Implement screens/modules**: Per spec; platform parity (iOS/Android)
 - [ ] **API integration**: Auth, state, offline (if required)
-- [ ] **Unit tests (TDD/BDD)**: Components, logic — coverage **≥ 90%**; follow Clean Code, SOLID, DRY, KISS
+- [ ] **Unit tests (TDD/BDD)**: Components, logic — coverage **100%**; follow Clean Code, SOLID, DRY, KISS
 - [ ] **PR**: Lint, tests; Tech Lead review
 - [ ] **Output**: Code + screen/module docs in \`dev/mobile/\`
 `;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sdlc-workflow",
-  "version": "1.2.3",
+  "version": "1.2.6",
   "description": "Scaffold SDLC workflow docs and templates for Cursor, Claude, and dev teams",
   "type": "module",
   "bin": {