sdlc-workflow 1.0.2 → 1.0.4

package/README.md

@@ -5,12 +5,14 @@ Scaffold SDLC workflow docs and templates into your project. Works with **Cursor
 ## Flow
 
 ```
-User Request → PO → Business BA → Architect → Technical BA → QE (docs) → Dev → QE (testing) → Deploy
+User Request → PO → Business BA → Architect → Technical BA → QE (docs) → Dev → QE (testing) → Deploy (Docker Compose + K8s)
 ```
 
-- **QE (docs)**: Test plan, test cases — before Dev implements
-- **Dev**: Tech Lead (review, merge) + Senior Dev (implement, Unit Test ≥90%)
-- **QE (testing)**: After Dev unit tests — automation + manual, sign-off
+- **Each role runs as a sub-agent** (see `docs/sdlc/agents/`).
+- **After completion** → deploy immediately with **Docker Compose** (local/staging) and **Kubernetes** (production) — `docs/sdlc/deploy/`.
+- **QE (docs)**: Test plan, test cases
+- **Dev**: After docs phase → **run implementation immediately**. Tech Lead (review, merge) + Senior Dev (implement, Unit Test ≥90%)
+- **QE (testing)**: QE Lead (test framework, review) + Senior QE (10+ yrs, write automation tests)
 
 ## Usage
 
@@ -56,12 +58,25 @@ docs/sdlc/
 │   └── README.md
 ├── qe/                       # QE (docs + testing)
 │   ├── test-case.template.md
+│   ├── README.md
+│   ├── qe-lead/              # QE Lead: test framework, review test code
+│   │   └── README.md
+│   └── senior-qe/            # Senior QE 10+ yrs: write automation tests
+│       └── README.md
+├── dev/                      # Dev team (per role)
+│   ├── tech-lead/            # Tech Lead 15+ yrs: tech stack, review & merge
+│   │   └── README.md
+│   └── senior-developer/     # Senior Dev 10+ yrs: implement, Unit Test ≥90%
+│       └── README.md
+├── agents/                   # Sub-agent specs (each role = sub-agent)
 │   └── README.md
-└── dev/                      # Dev team (per role)
-    ├── tech-lead/            # Tech Lead 15+ yrs: tech stack, review & merge
-    │   └── README.md
-    └── senior-developer/     # Senior Dev 10+ yrs: implement, Unit Test ≥90%
-        └── README.md
+└── deploy/                   # After completion → Docker Compose + K8s
+    ├── README.md
+    ├── docker-compose.yml.template
+    └── k8s/
+        ├── deployment.yaml.template
+        ├── service.yaml.template
+        └── ingress.yaml.template
 
 .cursor/rules/
 └── sdlc-workflow.mdc         # Cursor rule

package/bin/cli.js

@@ -149,8 +149,13 @@ async function generateFromInline(cwd) {
     join(base, "ba", "technical"),
     join(base, "architecture"),
     join(base, "qe"),
+    join(base, "qe", "qe-lead"),
+    join(base, "qe", "senior-qe"),
     join(base, "dev", "tech-lead"),
     join(base, "dev", "senior-developer"),
+    join(base, "agents"),
+    join(base, "deploy"),
+    join(base, "deploy", "k8s"),
   ];
 
   for (const d of dirs) {
@@ -171,8 +176,16 @@ async function generateFromInline(cwd) {
     ["architecture/README.md", ARCH_README],
     ["qe/test-case.template.md", QE_TC_TEMPLATE],
     ["qe/README.md", QE_README],
+    ["qe/qe-lead/README.md", QE_LEAD_README],
+    ["qe/senior-qe/README.md", QE_SENIOR_README],
     ["dev/tech-lead/README.md", DEV_TECH_LEAD_README],
     ["dev/senior-developer/README.md", DEV_SENIOR_README],
+    ["agents/README.md", AGENTS_README],
+    ["deploy/README.md", DEPLOY_README],
+    ["deploy/docker-compose.yml.template", DOCKER_COMPOSE_TEMPLATE],
+    ["deploy/k8s/deployment.yaml.template", K8S_DEPLOYMENT_TEMPLATE],
+    ["deploy/k8s/service.yaml.template", K8S_SERVICE_TEMPLATE],
+    ["deploy/k8s/ingress.yaml.template", K8S_INGRESS_TEMPLATE],
   ];
 
   for (const [rel, content] of files) {
@@ -195,29 +208,31 @@ globs: docs/sdlc/**/*, **/*.md
 3. **Architect** — ADRs, diagrams → docs/sdlc/architecture/
 4. **Technical BA** — API specs, team breakdown → docs/sdlc/ba/technical/
 5. **QE (docs)** — Test plan, test cases → docs/sdlc/qe/
-6. **Dev** — Tech Lead (review, merge) + Senior Dev (implement, ≥90% unit test) → docs/sdlc/dev/{role}/
-7. **QE (testing)** — Automation + manual tests, sign-off
-8. **Deploy** — Release, monitor
+6. **Dev** — After docs phase → **run implementation immediately**. Tech Lead (review, merge) + Senior Dev (implement, ≥90% unit test) → docs/sdlc/dev/{role}/
+7. **QE (testing)** — QE Lead (test framework, review) + Senior QE (10+ yrs, automation) → docs/sdlc/qe/{role}/
+8. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
 
+**Each role runs as a sub-agent.** See docs/sdlc/agents/
 Full workflow: docs/sdlc/SDLC-WORKFLOW.md
 `;
 
 const CURSOR_SKILL_MD = `---
 name: sdlc-workflow
-description: Multi-role SDLC workflow from user requirements through PO, Business BA, Architect, Technical BA, Dev teams, and QE. Use when user mentions SDLC, requirements, PO, BA, Architect, technical spec, phased development, yêu cầu, phân rã, kiến trúc, or handoff between roles.
+description: Multi-role SDLC workflow from user requirements through PO, Business BA, Architect, Technical BA, Dev teams, and QE. Use when user mentions SDLC, requirements, PO, BA, Architect, technical spec, phased development, or handoff between roles.
 ---
 
 # SDLC Workflow (Multi-Role)
 
-Sequential workflow for approaching user requirements. Each phase produces docs/artifacts for the next. Apply when clarifying scope, breaking down features, or handing off between roles.
+Sequential workflow; **each role runs as a sub-agent**. Each phase produces docs/artifacts for the next. After completion → deploy with **Docker Compose** and **K8s** (docs/sdlc/deploy/).
 
 ## Flow Overview
 
 \`\`\`
-User Request → PO → Business BA → Architect → Technical BA → QE (docs) → Dev → QE (testing) → Deploy
+User Request → PO → Business BA → Architect → Technical BA → QE (docs) → Dev → QE (testing) → Deploy (Docker Compose + K8s)
 \`\`\`
 
 **Determine current phase** before acting. If unsure, ask: "Which phase are we in?"
+**Sub-agent specs**: docs/sdlc/agents/
 
 ---
 
@@ -254,11 +269,11 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 
 **Role**: Create test plan, test cases before Dev implements.
 **Deliverables**: Test plan, test cases.
-**Output**: \`docs/sdlc/qe/\` — Ready for Dev to start implementation.
+**Output**: \`docs/sdlc/qe/\` — After docs phase → **Dev team runs implementation immediately** (no extra gate).
 
 ## Phase 5b: Dev Teams
 
-**Trigger**: After QE docs complete. **Start implementation.**
+**Trigger**: After docs are done (Technical BA + QE docs). **Dev runs implementation immediately.**
 
 **Roles**:
 - **Tech Lead (15+ yrs)**: Decide tech stack, libraries; review & merge code. Docs: \`docs/sdlc/dev/tech-lead/\`
@@ -268,15 +283,22 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 
 **Output**: Code + unit tests. **Handoff to QE (testing).**
 
-## Phase 6: QE (Testing phase)
+## Phase 6: QE (Testing phase — automation)
 
 **Trigger**: After Dev completes unit tests.
-**Role**: Run tests, include **automation tests**, sign-off.
-**Output**: Test report. **Handoff to Deploy.**
+**Role**: Write and run **automation tests**, sign-off.
+
+**Roles**:
+- **QE Lead**: Decide test framework; review test code. Docs: \`docs/sdlc/qe/qe-lead/\`
+- **Senior QE (10+ yrs)**: Write automation tests. Docs: \`docs/sdlc/qe/senior-qe/\`
 
-## Phase 7: Deploy & Maintenance
+**Output**: Automation tests, test report. **Handoff to Deploy.**
 
-**Role**: Release, monitor, iterate.
+## Phase 7: Deploy
+
+**Trigger**: After QE sign-off.
+**Role**: Deploy with **Docker Compose** (local/staging) and **Kubernetes** (production).
+**Output**: \`docs/sdlc/deploy/\` — docker-compose.yml, k8s manifests. Deploy right after pipeline completes.
 
 ## Quick Phase Checklist
 
@@ -289,9 +311,10 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 | 4 | Technical BA | API specs, tech breakdown |
 | 5a | QE (docs) | Test plan, test cases |
 | 5b | Dev | Code, unit tests (≥90%) |
-| 6 | QE (testing) | Automation + manual, sign-off |
-| 7 | Ops | Deploy, monitor |
+| 6 | QE (testing) | QE Lead + Senior QE, automation, sign-off |
+| 7 | Deploy | Docker Compose + K8s |
 
+**Sub-agents**: Each role = one sub-agent (PO, Business BA, Architect, Technical BA, QE Lead, Senior QE, Tech Lead, Senior Dev). See docs/sdlc/agents/
 See reference.md for templates.
 `;
 
@@ -313,9 +336,19 @@ POST /api/v1/[resource] — Purpose, Request, Response, Contract
 ## QE: Test Case
 TC-001: [Scenario] — Precondition, Steps, Expected, Links to AC
 
+## QE Team
+- QE Lead: test framework decision, review test code → docs/sdlc/qe/qe-lead/
+- Senior QE (10+ yrs): write automation tests → docs/sdlc/qe/senior-qe/
+
 ## Dev Team
 - Tech Lead (15+ yrs): tech stack, libraries, review & merge → docs/sdlc/dev/tech-lead/
 - Senior Dev (10+ yrs): implement, Unit Test ≥90% → docs/sdlc/dev/senior-developer/
+
+## Sub-agents
+Each role = sub-agent. See docs/sdlc/agents/
+
+## Deploy
+After completion → Docker Compose + K8s. See docs/sdlc/deploy/
 `;
 
 const AGENTS_MD_CONTENT = `## SDLC Workflow
@@ -327,12 +360,11 @@ When working on requirements, features, or handoffs, follow these phases:
 3. **Architect** — ADRs, diagrams → docs/sdlc/architecture/
 4. **Technical BA** — API specs, team breakdown → docs/sdlc/ba/technical/
 5. **QE (docs)** — Test plan, test cases → docs/sdlc/qe/
-6. **Dev** — After QE docs: Tech Lead (15+ yrs, tech stack, review & merge) + Senior Dev (10+ yrs, implement, Unit Test ≥90%) → docs/sdlc/dev/{role}/
-7. **QE (testing)** — After Dev unit tests: automation + manual, sign-off
-8. **Deploy** — Release, monitor
+6. **Dev** — After docs phase → **run implementation immediately**. Tech Lead + Senior Dev → docs/sdlc/dev/{role}/
+7. **QE (testing)** — QE Lead + Senior QE (automation)
+8. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
 
-Flow: ... → Technical BA → QE docs → Dev → QE testing → Deploy
-Ask "Which phase are we in?" if unclear.
+After the docs phase, the Dev team runs implementation immediately. See docs/sdlc/agents/
 `;
 
 const CLAUDE_SDLC_CONTENT = `## SDLC Workflow
@@ -342,12 +374,11 @@ const CLAUDE_SDLC_CONTENT = `## SDLC Workflow
 3. **Architect** — ADRs, diagrams → docs/sdlc/architecture/
 4. **Technical BA** — API specs, team breakdown → docs/sdlc/ba/technical/
 5. **QE (docs)** — Test plan, test cases → docs/sdlc/qe/
-6. **Dev** — After QE docs: Tech Lead (15+ yrs, tech stack, review & merge) + Senior Dev (10+ yrs, implement, Unit Test ≥90%) → docs/sdlc/dev/{role}/
-7. **QE (testing)** — After Dev unit tests: automation + manual, sign-off
-8. **Deploy** — Release, monitor
+6. **Dev** — After docs phase → **run implementation immediately**. Tech Lead + Senior Dev → docs/sdlc/dev/{role}/
+7. **QE (testing)** — QE Lead + Senior QE (automation)
+8. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
 
-Flow: ... → Technical BA → QE docs → Dev → QE testing → Deploy
-Ask "Which phase are we in?" if unclear.
+After the docs phase (Technical BA + QE docs), the Dev team runs implementation immediately. See docs/sdlc/agents/
 `;
 
 const SDLC_WORKFLOW_MD = `# SDLC Workflow (Multi-Role)
@@ -372,8 +403,10 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 | 4 | Technical BA | API specs, tech breakdown |
 | 5a | QE (docs) | Test plan, test cases |
 | 5b | Dev | Code, unit tests (≥90%) |
-| 6 | QE (testing) | Automation + manual, sign-off |
-| 7 | Ops | Deploy, monitor |
+| 6 | QE (testing) | QE Lead + Senior QE, automation, sign-off |
+| 7 | Deploy | Docker Compose + K8s |
+
+**Sub-agents**: Each role runs as a sub-agent (PO, Business BA, Architect, Technical BA, QE Lead, Senior QE, Tech Lead, Senior Dev). See docs/sdlc/agents/
 
 ## Phase Details
 
@@ -394,9 +427,9 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 - Output: \`docs/sdlc/ba/technical/\`
 
 ### Phase 5a: QE (Docs)
-- Test plan, test cases — **before Dev implements**
+- Test plan, test cases
 - Output: \`docs/sdlc/qe/\`
-- **Then**: Dev team starts implementation
+- **After docs phase → Dev team runs implementation immediately** (no extra gate)
 
 ### Phase 5b: Dev Teams
 - **Tech Lead (15+ yrs)**: Tech stack, libraries; review & merge. Output: \`docs/sdlc/dev/tech-lead/\`
@@ -404,11 +437,13 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 - **Requirement**: Unit Test coverage **≥ 90%**
 - **Then**: QE starts testing phase
 
-### Phase 6: QE (Testing)
-- After Dev unit tests complete: automation tests + manual tests, sign-off
+### Phase 6: QE (Testing — automation)
+- **QE Lead**: Test framework decision; review test code. Output: \`docs/sdlc/qe/qe-lead/\`
+- **Senior QE (10+ yrs)**: Write automation tests. Output: \`docs/sdlc/qe/senior-qe/\`
 
 ### Phase 7: Deploy
-- Release, monitor
+- After pipeline completes → deploy with **Docker Compose** (local/staging) and **Kubernetes** (production)
+- Output: \`docs/sdlc/deploy/\` — docker-compose.yml, k8s/
 
 See [reference.md](./reference.md) for templates.
 `;
@@ -416,6 +451,111 @@ See [reference.md](./reference.md) for templates.
 const REFERENCE_MD = `# SDLC Workflow — Reference
 
 Templates and examples. Use \`*.template.md\` as starting points.
+Sub-agents: docs/sdlc/agents/
+Deploy: docs/sdlc/deploy/ (Docker Compose + K8s)
+`;
+
+const AGENTS_README = `# Sub-Agents
+
+Every role in the SDLC runs as a **sub-agent**. Each phase is assigned to a corresponding sub-agent.
+
+| Role | Sub-agent | Input | Output |
+|------|-----------|--------|--------|
+| PO | po | User request | docs/sdlc/po/ |
+| Business BA | business-ba | docs/sdlc/po/ | docs/sdlc/ba/business/ |
+| Architect | architect | docs/sdlc/ba/business/ | docs/sdlc/architecture/ |
+| Technical BA | technical-ba | docs/sdlc/architecture/ | docs/sdlc/ba/technical/ |
+| QE (docs) | qe-docs | docs/sdlc/ba/technical/ | docs/sdlc/qe/ (test plan) |
+| 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%) |
+| QE Lead | qe-lead | Test plan | Test framework, review, docs/sdlc/qe/qe-lead/ |
+| Senior QE | senior-qe | Test plan + framework | Automation tests, docs/sdlc/qe/senior-qe/ |
+| Deploy | deploy | QE sign-off | Docker Compose + K8s, docs/sdlc/deploy/ |
+
+Orchestrator: run each sub-agent in order; hand off output → input of the next sub-agent.
+`;
+
+const DEPLOY_README = `# Deploy
+
+After the pipeline completes (QE sign-off), deploy immediately with:
+
+- **Docker Compose** — local / staging: \`docker compose up -d\`
+- **Kubernetes** — production: \`kubectl apply -f k8s/\`
+
+## Files
+
+- \`docker-compose.yml.template\` — copy to \`docker-compose.yml\`, adjust image/env
+- \`k8s/deployment.yaml.template\` — Deployment
+- \`k8s/service.yaml.template\` — Service
+- \`k8s/ingress.yaml.template\` — Ingress (optional)
+`;
+
+const DOCKER_COMPOSE_TEMPLATE = `# Copy to docker-compose.yml and adjust image, env, ports
+services:
+  app:
+    image: your-registry/your-app:latest
+    build: .
+    ports:
+      - "8080:8080"
+    environment:
+      - NODE_ENV=production
+    restart: unless-stopped
+`;
+
+const K8S_DEPLOYMENT_TEMPLATE = `# deployment.yaml - adjust name, image, replicas
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app
+spec:
+  replicas: 2
+  selector:
+    matchLabels:
+      app: app
+  template:
+    metadata:
+      labels:
+        app: app
+    spec:
+      containers:
+        - name: app
+          image: your-registry/your-app:latest
+          ports:
+            - containerPort: 8080
+`;
+
+const K8S_SERVICE_TEMPLATE = `# service.yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: app
+spec:
+  selector:
+    app: app
+  ports:
+    - port: 80
+      targetPort: 8080
+  type: ClusterIP
+`;
+
+const K8S_INGRESS_TEMPLATE = `# ingress.yaml - optional, adjust host
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: app
+spec:
+  ingressClassName: nginx
+  rules:
+    - host: app.example.com
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: app
+                port:
+                  number: 80
 `;
 
 const PO_EPIC_TEMPLATE = `# Epic: [Name]
@@ -537,12 +677,34 @@ const QE_TC_TEMPLATE = `## TC-001: [Scenario]
 const QE_README = `# QE (Quality Engineering)
 
 Two phases:
-1. **Docs phase** — Test plan, test cases (before Dev implements). Output ready for Dev team.
-2. **Testing phase** — After Dev completes unit tests: run tests, include automation tests, sign-off.
+1. **Docs phase** — Test plan, test cases. Done → **Dev runs implementation immediately**.
+2. **Testing phase** — After Dev completes unit tests: QE team writes automation tests.
+   - **QE Lead**: Decide test framework; review test code → docs/sdlc/qe/qe-lead/
+   - **Senior QE (10+ yrs)**: Write automation tests → docs/sdlc/qe/senior-qe/
 
 Use test-case.template.md for test cases.
 `;
 
+const QE_LEAD_README = `# QE Lead
+
+**Responsibilities**:
+- Decide test framework (e.g. Playwright, Cypress, Jest, etc.)
+- Review test code
+- Ensure automation quality and coverage
+
+**Docs**: Test framework ADR, review checklist.
+`;
+
+const QE_SENIOR_README = `# Senior QE (10+ years exp)
+
+**Responsibilities**:
+- Write automation tests per test plan
+- Implement E2E, integration, regression tests
+- Follow QE Lead's framework decisions
+
+**Docs**: Automation test design, framework usage.
+`;
+
 const DEV_TECH_LEAD_README = `# Tech Lead (15+ years exp)
 
 **Responsibilities**:

package/package.json

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