sdlc-workflow 1.0.9 → 1.0.11

package/README.md

@@ -5,10 +5,11 @@ 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 (Docker Compose + K8s)
+User Request → PO → Business BA → Architect → Technical BA → Design (if app/web, PO+BA review loop) → QE (docs) → Dev → QE (testing) → Deploy (Docker Compose + K8s)
 ```
 
 - **Trigger:** When you send an **idea** or **feature request**, the agent should run the **full pipeline** (PO → … → Deploy) in sequence, one sub-agent/role per phase — not handle everything in one go or stop after one phase. See `docs/sdlc/ORCHESTRATION.md`.
+- **Design (optional):** For app/web projects, after Technical BA → invoke **Pencil.dev** (MCP) to design; **PO + Business BA review** until approved; then QE + Dev.
 - **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
@@ -57,6 +58,8 @@ docs/sdlc/
 ├── architecture/             # Architect
 │   ├── adr.template.md
 │   └── README.md
+├── design/                   # Design (optional, app/web): Pencil.dev .pen; PO+BA review until approved
+│   └── README.md
 ├── qe/                       # QE (one folder per epic: qe/{epic-slug}/)
 │   ├── test-case.template.md
 │   ├── README.md

package/bin/cli.js

@@ -163,6 +163,7 @@ async function generateFromInline(cwd) {
     join(base, "qe"),
     join(base, "qe", "qe-lead"),
     join(base, "qe", "senior-qe"),
+    join(base, "design"),
     join(base, "dev", "tech-lead"),
     join(base, "dev", "senior-developer"),
     join(base, "dev", "frontend"),
@@ -197,6 +198,7 @@ async function generateFromInline(cwd) {
     ["qe/README.md", QE_README],
     ["qe/qe-lead/README.md", QE_LEAD_README],
     ["qe/senior-qe/README.md", QE_SENIOR_README],
+    ["design/README.md", DESIGN_README],
     ["dev/tech-lead/README.md", DEV_TECH_LEAD_README],
     ["dev/senior-developer/README.md", DEV_SENIOR_README],
     ["dev/implementation-roles.template.md", DEV_IMPLEMENTATION_ROLES_TEMPLATE],
@@ -235,12 +237,13 @@ globs: docs/sdlc/**/*, **/*.md
 2. **Business BA** — FRS, process flows → docs/sdlc/ba/business/{epic-slug}/ (one folder per epic)
 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/{epic-slug}/ (one folder per epic)
-6. **Dev** — After docs phase → **run implementation immediately**. Tech Lead + implementation roles by project (FE, Backend, Mobile, Embedded, Data/ML, Platform) → docs/sdlc/dev/{role}/
-7. **QE (testing)** — QE Lead (15+ yrs automation: strategy, framework, review) + Senior QE (10+ yrs, automation) → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
-8. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
+5. **Design (if app/web)** — Pencil.dev designs → docs/sdlc/design/{epic-slug}/; **PO + BA review** → loop until approved
+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 + implementation roles → docs/sdlc/dev/{role}/
+8. **QE (testing)** — QE Lead (15+ yrs automation) + Senior QE (10+ yrs) → docs/sdlc/qe/{epic-slug}/
+9. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
 
-**Each role runs as a sub-agent.** See docs/sdlc/agents/
+**Each role runs as a sub-agent.** Design uses Pencil.dev MCP. See docs/sdlc/agents/
 Full workflow: docs/sdlc/SDLC-WORKFLOW.md
 `;
 
@@ -258,7 +261,7 @@ Sequential workflow; **each role runs as a sub-agent**. Each phase produces docs
 **When the user sends an idea, feature request, or new requirement:**
 1. **Trigger the pipeline** and run it **continuously through deployment** (Phase 1 → 2 → … → 7).
 2. **One role per phase.** For each phase, act **only** as that role (e.g. only PO in phase 1, only Business BA in phase 2). Produce that phase's outputs into the correct folder, then **continue to the next phase** without waiting for the user.
-3. **Run in order:** PO → Business BA → Architect → Technical BA → QE (docs) → Dev → QE (testing) → Deploy. Do not stop after one phase unless the user explicitly asks to stop.
+3. **Run in order:** PO → Business BA → Architect → Technical BA → **Design (if app/web)** → QE (docs) → Dev → QE (testing) → Deploy. If Design: **PO + BA review** design; loop until approved before QE/Dev. Do not stop after one phase unless the user explicitly asks to stop.
 
 **Note:** In Cursor and similar tools there is a single agent per conversation. "Sub-agent" means **one role per phase** — the same agent must adopt exactly one role per phase and run phases in sequence (do not mix roles in one step). If the platform later supports spawning separate agents per phase, use that; otherwise this single agent simulates the pipeline by switching role each phase.
 
@@ -267,7 +270,7 @@ Sequential workflow; **each role runs as a sub-agent**. Each phase produces docs
 ## Flow Overview
 
 \`\`\`
-User Request → PO → Business BA → Architect → Technical BA → QE (docs) → Dev → QE (testing) → Deploy (Docker Compose + K8s)
+User Request → PO → Business BA → Architect → Technical BA → Design (if app/web, PO+BA review loop) → QE (docs) → Dev → QE (testing) → Deploy (Docker Compose + K8s)
 \`\`\`
 
 **Determine current phase** before acting. If user sent an idea, assume Phase 0 and start from Phase 1.
@@ -301,7 +304,20 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 
 **Role**: Translate business + architecture into implementable specs.
 **Deliverables**: API specs, DB schema, team breakdown, acceptance criteria per ticket.
-**Output**: \`docs/sdlc/ba/technical/\` — **Handoff to QE + Dev.**
+**Output**: \`docs/sdlc/ba/technical/\` — **Handoff to Design (if app/web) or QE + Dev.**
+
+## Phase 4b: Design (optional — app/web only)
+
+**When:** Project has UI (web, mobile app). Skip for API-only, library, CLI, data/ML, platform without UI.
+
+**Role**: Invoke **Pencil.dev** sub-agent (MCP) to create UI/UX designs from idea + PO + Business BA + Technical BA docs.
+**Output**: \`docs/sdlc/design/{epic-slug}/\` — .pen designs.
+
+**Review loop:**
+1. **PO review**: Design aligns with epic brief, user stories, acceptance criteria?
+2. **Business BA review**: Design matches functional requirements, process flows?
+3. **If not approved**: Capture feedback → redesign with Pencil.dev → repeat until PO and BA approve.
+4. **If approved** → **Handoff to QE + Dev.**
 
 ## Phase 5a: QE (Docs phase)
 
@@ -353,12 +369,13 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 | 2 | Business BA | FRS, process flows |
 | 3 | Architect | ADRs, system diagrams |
 | 4 | Technical BA | API specs, tech breakdown |
+| 4b | Design (if app/web) | Pencil.dev designs; PO+BA review until approved |
 | 5a | QE (docs) | Test plan, test cases |
 | 5b | Dev | Code, unit tests (≥90%) |
 | 6 | QE (testing) | QE Lead (15+ yrs automation) + Senior QE (10+ yrs), 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/
+**Sub-agents**: Each role = one sub-agent. Design uses Pencil.dev MCP. See docs/sdlc/agents/
 See reference.md for templates.
 `;
 
@@ -366,8 +383,9 @@ const CURSOR_REFERENCE_MD = `# SDLC Workflow — Reference
 
 ## Folder structure: one per epic/feature (PO and Business BA)
 
-- **PO**: \`docs/sdlc/po/{epic-slug}/\` — one folder per epic (e.g. \`job-scheduler-event-bus\`). Files: epic-brief.md, user-stories.md. Do not put all epics in one file.
+- **PO**: \`docs/sdlc/po/{epic-slug}/\` — one folder per epic. Files: epic-brief.md, user-stories.md. Do not put all epics in one file.
 - **Business BA**: \`docs/sdlc/ba/business/{epic-slug}/\` — same slug as PO. Files: functional-requirements.md, process-flows.md. Do not merge all epics into one file.
+- **Design (if app/web)**: \`docs/sdlc/design/{epic-slug}/\` — same slug as PO/BA. Pencil.dev .pen designs; PO+BA review until approved.
 - **QE**: \`docs/sdlc/qe/{epic-slug}/\` — same slug as PO/BA. Files: test-plan.md, test-cases.md, automation artifacts. Do not put all epics in one file.
 
 ## PO: Epic Brief Template
@@ -383,6 +401,9 @@ FR-001: [Title] — Description, Trigger, Process Flow, Output, Constraints
 ## Technical BA: API Spec
 POST /api/v1/[resource] — Purpose, Request, Response, Contract
 
+## Design (if app/web)
+Pencil.dev MCP — create .pen designs from idea + PO + BA + Technical BA. Output: docs/sdlc/design/{epic-slug}/. PO + BA review until approved; loop if not aligned.
+
 ## QE: Test Case
 TC-001: [Scenario] — Precondition, Steps, Expected, Links to AC
 
@@ -412,12 +433,13 @@ When working on requirements, features, or handoffs, follow these phases:
 2. **Business BA** — FRS, process flows → docs/sdlc/ba/business/{epic-slug}/ (one folder per epic)
 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/{epic-slug}/ (one folder per epic)
-6. **Dev** — After docs phase → **run implementation immediately**. Tech Lead + Senior Dev → docs/sdlc/dev/{role}/
-7. **QE (testing)** — QE Lead (15+ yrs automation) + Senior QE (10+ yrs) → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
-8. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
+5. **Design (if app/web)** — Pencil.dev designs → docs/sdlc/design/{epic-slug}/; **PO + BA review** until approved; then QE + Dev
+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 + Senior Dev → docs/sdlc/dev/{role}/
+8. **QE (testing)** — QE Lead (15+ yrs automation) + Senior QE (10+ yrs) → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
+9. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
 
-After the docs phase, the Dev team runs implementation immediately. See docs/sdlc/agents/
+Design: invoke Pencil.dev MCP; PO and BA review design; loop until approved. After the docs phase, the Dev team runs implementation immediately. See docs/sdlc/agents/
 `;
 
 const CLAUDE_SDLC_CONTENT = `## SDLC Workflow
@@ -428,12 +450,13 @@ const CLAUDE_SDLC_CONTENT = `## SDLC Workflow
 2. **Business BA** — FRS, process flows → docs/sdlc/ba/business/{epic-slug}/ (one folder per epic)
 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/{epic-slug}/ (one folder per epic)
-6. **Dev** — After docs phase → **run implementation immediately**. Tech Lead + Senior Dev → docs/sdlc/dev/{role}/
-7. **QE (testing)** — QE Lead (15+ yrs automation) + Senior QE (10+ yrs) → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
-8. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
+5. **Design (if app/web)** — Pencil.dev designs → docs/sdlc/design/{epic-slug}/; **PO + BA review** until approved
+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 + Senior Dev → docs/sdlc/dev/{role}/
+8. **QE (testing)** — QE Lead (15+ yrs automation) + Senior QE (10+ yrs) → docs/sdlc/qe/{epic-slug}/ (same folder per epic)
+9. **Deploy** — Docker Compose + K8s → docs/sdlc/deploy/
 
-After the docs phase (Technical BA + QE docs), the Dev team runs implementation immediately. See docs/sdlc/agents/
+Design: Pencil.dev MCP; PO and BA review; loop until approved. After the docs phase, Dev runs implementation immediately. See docs/sdlc/agents/
 `;
 
 const SDLC_WORKFLOW_MD = `# SDLC Workflow (Multi-Role)
@@ -450,7 +473,7 @@ For Cursor, see .cursor/rules/sdlc-workflow.mdc
 ## Flow
 
 \`\`\`
-User Request → PO → Business BA → Architect → Technical BA → QE (docs) → Dev → QE (testing) → Deploy
+User Request → PO → Business BA → Architect → Technical BA → Design (if app/web, PO+BA review loop) → QE (docs) → Dev → QE (testing) → Deploy
 \`\`\`
 
 ## Phase Checklist
@@ -462,6 +485,7 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 | 2 | Business BA | FRS, process flows |
 | 3 | Architect | ADRs, system diagrams |
 | 4 | Technical BA | API specs, tech breakdown |
+| 4b | Design (if app/web) | Pencil.dev designs; PO+BA review until approved |
 | 5a | QE (docs) | Test plan, test cases |
 | 5b | Dev | Code, unit tests (≥90%) |
 | 6 | QE (testing) | QE Lead (15+ yrs automation) + Senior QE (10+ yrs), automation, sign-off |
@@ -487,6 +511,12 @@ User Request → PO → Business BA → Architect → Technical BA → QE (docs)
 - API specs, DB schema, team breakdown
 - Output: \`docs/sdlc/ba/technical/\`
 
+### Phase 4b: Design (optional — app/web only)
+- Invoke **Pencil.dev** (MCP) to design based on idea + PO + BA + Technical BA docs
+- Output: \`docs/sdlc/design/{epic-slug}/\` — .pen designs
+- **PO + Business BA review**: Both check design vs epic/FRS; if not aligned → feedback → redesign loop until approved
+- When approved → handoff to QE + Dev
+
 ### Phase 5a: QE (Docs)
 - Test plan, test cases
 - Output: \`docs/sdlc/qe/{epic-slug}/\` — **one folder per epic**; do not put all epics in one file
@@ -529,6 +559,7 @@ There is **one agent** per conversation. It simulates the pipeline by **adopting
 - [ ] Phase 2 Business BA: \`docs/sdlc/ba/business/{epic-slug}/\` (one folder per epic)
 - [ ] Phase 3 Architect: \`docs/sdlc/architecture/\`
 - [ ] Phase 4 Technical BA: \`docs/sdlc/ba/technical/\`
+- [ ] Phase 4b Design (if app/web): Pencil.dev designs in \`docs/sdlc/design/{epic-slug}/\`; PO+BA review until approved
 - [ ] Phase 5a QE docs: \`docs/sdlc/qe/{epic-slug}/\` (one folder per epic)
 - [ ] Phase 5b Dev: code + unit tests, \`docs/sdlc/dev/\`
 - [ ] Phase 6 QE testing: automation, sign-off → \`docs/sdlc/qe/{epic-slug}/\`
@@ -544,8 +575,9 @@ Deploy: docs/sdlc/deploy/ (Docker Compose + K8s)
 
 ## Folder structure: one per epic/feature
 
-- **PO**: \`docs/sdlc/po/{epic-slug}/\` — one folder per epic (e.g. \`job-scheduler-event-bus\`). Files inside: epic-brief.md, user-stories.md, etc. Do not put all epics in one file.
-- **Business BA**: \`docs/sdlc/ba/business/{epic-slug}/\` — same slug as PO. Files: functional-requirements.md, process-flows.md, etc. Do not merge all epics into one file.
+- **PO**: \`docs/sdlc/po/{epic-slug}/\` — one folder per epic. Files: epic-brief.md, user-stories.md. Do not put all epics in one file.
+- **Business BA**: \`docs/sdlc/ba/business/{epic-slug}/\` — same slug as PO. Files: functional-requirements.md, process-flows.md. Do not merge all epics into one file.
+- **Design (if app/web)**: \`docs/sdlc/design/{epic-slug}/\` — Pencil.dev .pen designs; PO+BA review until approved.
 - **QE**: \`docs/sdlc/qe/{epic-slug}/\` — same slug as PO/BA. Files: test-plan.md, test-cases.md, automation. Do not put all epics in one file.
 `;
 
@@ -559,7 +591,8 @@ Every role in the SDLC runs as a **sub-agent**. Each phase is assigned to a corr
 | Business BA | business-ba | docs/sdlc/po/{epic-slug}/ | docs/sdlc/ba/business/{epic-slug}/ (one folder per epic) |
 | 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/{epic-slug}/ (one folder per epic) |
+| Design (if app/web) | pencil-dev | docs/sdlc/po + ba + technical | docs/sdlc/design/{epic-slug}/; PO+BA review until approved |
+| 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 Frontend | frontend | UI spec, API contract | Web UI, docs/sdlc/dev/frontend/ |
@@ -703,16 +736,16 @@ const PO_README = `# PO (Product Owner)
 - Folder name = epic/feature slug (e.g. \`job-scheduler-event-bus\`, \`user-auth\`).
 - Inside that folder: \`epic-brief.md\`, \`user-stories.md\`, \`prd.md\` (or similar) for that epic only.
 
-Example:
-\`\`\`
-docs/sdlc/po/
-  job-scheduler-event-bus/
-    epic-brief.md
-    user-stories.md
-  user-auth/
-    epic-brief.md
-    user-stories.md
-\`\`\`
+## Detailed tasks
+
+- [ ] **Clarify vision**: Capture business problem, goals, success metrics
+- [ ] **Define scope**: Boundaries, in/out of scope, MVP vs later
+- [ ] **Write epic brief**: Problem, success metrics, high-level approach, project type
+- [ ] **Break into user stories**: As a [role], I want [goal] so that [benefit]; acceptance criteria per story
+- [ ] **Prioritize**: Must / Should / Could have; order by value and risk
+- [ ] **Identify dependencies**: External teams, systems, blockers
+- [ ] **Call out risks**: Technical, schedule, compliance
+- [ ] **Handoff to Business BA**: Deliverables in \`po/{epic-slug}/\`
 
 Use epic-brief.template.md as starting point for each epic.
 `;
@@ -755,7 +788,17 @@ docs/sdlc/ba/business/
     functional-requirements.md
 \`\`\`
 
-Use functional-requirement.template.md for FRS items. One file per epic, or one folder per epic with multiple files.
+## Detailed tasks
+
+- [ ] **Read PO outputs**: Epic brief, user stories, acceptance criteria
+- [ ] **Define functional requirements**: For each requirement: type, description, trigger, process flow, output, constraints (use FR-001, FR-002...)
+- [ ] **Document process flows**: Step-by-step business flows (e.g. BPMN, flowcharts, numbered lists)
+- [ ] **Write use cases**: Actor, goal, preconditions, main/alternate flows, postconditions
+- [ ] **Maintain glossary**: Business terms, definitions, acronyms
+- [ ] **Map to user stories**: Trace FRs to user stories / AC
+- [ ] **Handoff to Architect**: Deliverables in \`ba/business/{epic-slug}/\`
+
+Use functional-requirement.template.md for FRS items.
 `;
 
 const TECH_API_TEMPLATE = `# Interface / contract spec
@@ -856,6 +899,15 @@ const BA_TECH_README = `# Technical BA
 
 API/interface specs, DB schema, team breakdown.
 Templates support: HTTP API, library/SDK, CLI, and all project types (see api-spec and team-breakdown).
+
+## Detailed tasks
+
+- [ ] **Read Architect outputs**: ADRs, context/container diagrams, tech stack
+- [ ] **API/interface spec**: For each endpoint/class/command: purpose, request/response, contract (OpenAPI, TS types, CLI help)
+- [ ] **DB schema**: Tables, columns, indexes, constraints; migrations approach
+- [ ] **Team breakdown**: Map scope to teams (Backend, Frontend, Mobile, etc.) per project type; dependencies
+- [ ] **Trace to FRs**: Map technical specs to functional requirements
+- [ ] **Handoff to QE + Dev**: API spec, team breakdown in \`ba/technical/\`
 `;
 
 const ARCH_ADR_TEMPLATE = `# ADR-001: [Decision Title]
@@ -877,10 +929,20 @@ const ARCH_ADR_TEMPLATE = `# ADR-001: [Decision Title]
 - Negative: ...
 `;
 
-const ARCH_README = `# Architecture
+const ARCH_README = `# Architect
 
 ADRs, system diagrams, tech stack decisions.
 Use adr.template.md for new ADRs.
+
+## Detailed tasks
+
+- [ ] **Read Business BA outputs**: Functional requirements, process flows, use cases
+- [ ] **Context diagram**: System boundary, external actors, integrations
+- [ ] **Container diagram**: Main components/services and their responsibilities
+- [ ] **Tech stack decisions**: Languages, frameworks, databases; document in ADRs
+- [ ] **ADR per decision**: Context, decision, consequences (scope: backend, frontend, mobile, etc.)
+- [ ] **Non-functional alignment**: Performance, security, scalability, compliance
+- [ ] **Handoff to Technical BA**: Architecture docs, ADRs in \`architecture/\`
 `;
 
 const QE_TC_TEMPLATE = `## TC-001: [Scenario]
@@ -909,6 +971,19 @@ const QE_README = `# QE (Quality Engineering)
 - Use the same epic/feature slug as PO and Business BA: \`docs/sdlc/qe/{epic-slug}/\`
 - Inside that folder: \`test-plan.md\`, \`test-cases.md\` (Phase 5a), and for Phase 6: automation notes, framework decision for that epic, etc.
 
+## Detailed tasks (Docs phase — Phase 5a)
+
+- [ ] **Read Technical BA spec**: API, team breakdown, FRs
+- [ ] **Test plan**: Scope (unit, integration, E2E), coverage goals, risks
+- [ ] **Test cases**: TC-001, TC-002... — precondition, steps, expected, links to AC
+- [ ] **Handoff to Dev**: Test plan + test cases in \`qe/{epic-slug}/\` → Dev runs implementation
+
+## Detailed tasks (Testing phase — Phase 6)
+
+- [ ] **QE Lead**: Test strategy, framework, review test code
+- [ ] **Senior QE**: Write automation tests per test plan
+- [ ] **Sign-off**: Regression, coverage, release readiness in \`qe/{epic-slug}/\`
+
 Example:
 \`\`\`
 docs/sdlc/qe/
@@ -940,6 +1015,15 @@ const QE_LEAD_README = `# QE Lead (15+ years exp in test automation)
 - **Quality gates**: Define and enforce gates (e.g. coverage thresholds, required suites before merge, regression criteria).
 
 **Output**: Test framework ADR, automation strategy doc, review checklist, and per-epic guidance in \`docs/sdlc/qe/{epic-slug}/\`.
+
+## Detailed tasks
+
+- [ ] **Test automation strategy**: Document scope (unit/integration/E2E/API/performance), pyramid, alignment with tech stack
+- [ ] **Framework ADR**: Choose and justify frameworks (Playwright, Cypress, Jest, etc.); document in ADR
+- [ ] **Automation architecture**: Design folder structure, layers, fixtures, reporting, retries, env handling
+- [ ] **Review checklist**: Coverage, maintainability, naming, alignment with framework
+- [ ] **Quality gates**: Define thresholds (coverage, required suites before merge), regression criteria
+- [ ] **Per-epic guidance**: Output to \`qe/{epic-slug}/\` per epic
 `;
 
 const QE_SENIOR_README = `# Senior QE (10+ years exp)
@@ -949,7 +1033,37 @@ const QE_SENIOR_README = `# Senior QE (10+ years exp)
 - Implement E2E, integration, regression tests
 - Follow QE Lead's framework decisions
 
-**Docs**: Automation test design, framework usage.
+## Detailed tasks
+
+- [ ] **Read test plan**: Scope, coverage goals, test case IDs
+- [ ] **Implement E2E tests**: UI flows, critical paths per QE Lead's framework
+- [ ] **Implement API/integration tests**: Request/response, contracts
+- [ ] **Implement regression suite**: Add to CI; ensure stability (retries, waits)
+- [ ] **Report coverage**: Align with QE Lead's quality gates
+- [ ] **Output**: Automation code and docs in \`qe/{epic-slug}/\`
+`;
+
+const DESIGN_README = `# Design (optional — app/web projects only)
+
+**When:** After Technical BA, before QE and Dev. **Skip** for API-only, library, CLI, data/ML, platform projects without UI.
+
+**One folder per epic:** \`docs/sdlc/design/{epic-slug}/\` — same slug as PO/BA. Store .pen files and design notes there.
+
+## Flow
+
+1. **Design sub-agent (Pencil.dev)**: Create UI/UX designs based on idea + PO docs + Business BA FRS + Technical BA spec. Use Pencil MCP tools (\`batch_design\`, \`get_guidelines\`, \`get_style_guide\`, etc.) to produce .pen designs.
+2. **PO + Business BA review**: Both roles review the design against epic brief, user stories, functional requirements.
+3. **Loop until approved**: If design does not match idea/docs → return to step 1 with feedback; redesign. Repeat until PO and BA approve.
+4. **Handoff to QE + Dev**: Once approved → proceed to QE (docs) and Dev.
+
+## Detailed tasks
+
+- [ ] **Invoke Pencil.dev**: Call design sub-agent (Pencil MCP) with PO epic, BA FRS, Technical BA spec as context
+- [ ] **Create designs**: Screens, flows, components in .pen format; output to \`design/{epic-slug}/\`
+- [ ] **PO review**: Check design aligns with epic brief, user stories, acceptance criteria
+- [ ] **Business BA review**: Check design matches functional requirements, process flows
+- [ ] **If not approved**: Capture feedback; loop back to design step with specific changes
+- [ ] **If approved**: Handoff to QE and Dev; design in \`design/{epic-slug}/\`
 `;
 
 const DEV_TECH_LEAD_README = `# Tech Lead (15+ years exp)
@@ -959,7 +1073,15 @@ const DEV_TECH_LEAD_README = `# Tech Lead (15+ years exp)
 - Review and merge code
 - Ensure architecture alignment
 
-**Docs**: ADRs, tech decisions, review checklist.
+## Detailed tasks
+
+- [ ] **Read architecture and Technical BA spec**: ADRs, API spec, team breakdown
+- [ ] **Tech stack decision**: Languages, frameworks, libraries; document in ADR
+- [ ] **Project setup**: Repo structure, tooling, lint, format, CI baseline
+- [ ] **Code review**: Architecture alignment, patterns, test coverage, security
+- [ ] **Merge approval**: Enforce quality gates before merge
+- [ ] **Tech guidance**: Resolve technical disputes; mentor team
+- [ ] **Output**: ADRs, review checklist in \`dev/tech-lead/\`
 `;
 
 const DEV_SENIOR_README = `# Senior Developer (10+ years exp)
@@ -969,7 +1091,13 @@ const DEV_SENIOR_README = `# Senior Developer (10+ years exp)
 - Write code with Unit Test coverage **≥ 90%**
 - Follow Tech Lead's tech decisions
 
-**Docs**: Implementation notes, API usage.
+## Detailed tasks
+
+- [ ] **Read Technical BA spec**: API, schema, team breakdown
+- [ ] **Implement feature**: Code per spec; follow Tech Lead stack
+- [ ] **Unit tests**: Coverage **≥ 90%**; edge cases, error paths
+- [ ] **PR**: Lint, tests passing; request Tech Lead review
+- [ ] **Output**: Code + implementation notes in \`dev/senior-developer/\`
 `;
 
 const DEV_IMPLEMENTATION_ROLES_TEMPLATE = `# Implementation roles by project type
@@ -1009,7 +1137,14 @@ const DEV_FRONTEND_README = `# Senior Frontend (10+ years exp) — Web UI
 - Unit Test coverage **≥ 90%**
 - Follow Tech Lead's stack (e.g. React, Vue, Angular)
 
-**Docs**: Component docs, integration notes.
+## Detailed tasks
+
+- [ ] **Read Technical BA spec**: API contract, design (if any)
+- [ ] **Implement components/screens**: Per spec; responsive, accessible
+- [ ] **API integration**: Fetch, state, error handling
+- [ ] **Unit tests**: Components, hooks, utils — coverage **≥ 90%**
+- [ ] **PR**: Lint, tests; Tech Lead review
+- [ ] **Output**: Code + component/integration docs in \`dev/frontend/\`
 `;
 
 const DEV_BACKEND_README = `# Senior Backend (10+ years exp) — API, services
@@ -1019,7 +1154,14 @@ const DEV_BACKEND_README = `# Senior Backend (10+ years exp) — API, services
 - Unit Test coverage **≥ 90%**
 - Follow Tech Lead's stack
 
-**Docs**: API implementation notes, DB changes.
+## Detailed tasks
+
+- [ ] **Read Technical BA spec**: API spec, DB schema
+- [ ] **Implement endpoints**: Per spec; validation, auth, error responses
+- [ ] **Implement DB layer**: Migrations, queries, transactions
+- [ ] **Unit tests**: Services, controllers, DB — coverage **≥ 90%**
+- [ ] **PR**: Lint, tests; Tech Lead review
+- [ ] **Output**: Code + API/DB implementation notes in \`dev/backend/\`
 `;
 
 const DEV_MOBILE_README = `# Senior Mobile (10+ years exp) — iOS / Android / cross-platform
@@ -1029,7 +1171,14 @@ const DEV_MOBILE_README = `# Senior Mobile (10+ years exp) — iOS / Android / c
 - Unit Test coverage **≥ 90%**
 - Follow Tech Lead's stack (e.g. React Native, Flutter, native)
 
-**Docs**: Screen/module docs, integration notes.
+## Detailed tasks
+
+- [ ] **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**: Components, logic — coverage **≥ 90%**
+- [ ] **PR**: Lint, tests; Tech Lead review
+- [ ] **Output**: Code + screen/module docs in \`dev/mobile/\`
 `;
 
 const DEV_EMBEDDED_README = `# Senior Embedded (10+ years exp) — firmware, IoT
@@ -1039,7 +1188,13 @@ const DEV_EMBEDDED_README = `# Senior Embedded (10+ years exp) — firmware, IoT
 - Tests as appropriate for target (unit, HW-in-loop)
 - Follow Tech Lead's stack and safety constraints
 
-**Docs**: Module design, interface specs.
+## Detailed tasks
+
+- [ ] **Read Technical BA spec**: Interfaces, timing, constraints
+- [ ] **Implement modules/drivers**: Per spec; safety-critical compliance
+- [ ] **Tests**: Unit, HW-in-loop as feasible
+- [ ] **PR**: Lint, tests; Tech Lead review
+- [ ] **Output**: Code + module/interface docs in \`dev/embedded/\`
 `;
 
 const DEV_DATA_ML_README = `# Senior Data/ML (10+ years exp)
@@ -1049,7 +1204,14 @@ const DEV_DATA_ML_README = `# Senior Data/ML (10+ years exp)
 - Tests and validation for data and model quality
 - Follow Tech Lead's stack (e.g. Python, Spark, ML frameworks)
 
-**Docs**: Pipeline design, model cards.
+## Detailed tasks
+
+- [ ] **Read Technical BA spec**: Data spec, API contract
+- [ ] **Implement ETL/pipelines**: Ingestion, transforms, storage
+- [ ] **Implement models**: Training, evaluation; model cards
+- [ ] **Tests**: Data validation, model quality metrics
+- [ ] **PR**: Lint, tests; Tech Lead review
+- [ ] **Output**: Code + pipeline/model docs in \`dev/data-ml/\`
 `;
 
 const DEV_PLATFORM_README = `# Senior Platform (10+ years exp) — infra, CI/CD
@@ -1058,7 +1220,14 @@ const DEV_PLATFORM_README = `# Senior Platform (10+ years exp) — infra, CI/CD
 - Implement CI/CD, infra as code, observability per spec
 - Follow Tech Lead's stack and security requirements
 
-**Docs**: Runbooks, pipeline and infra docs.
+## Detailed tasks
+
+- [ ] **Read Technical BA spec**: Infra, deploy, observability requirements
+- [ ] **Implement CI/CD**: Build, test, deploy pipelines
+- [ ] **Infra as code**: Terraform/Pulumi/CloudFormation per spec
+- [ ] **Observability**: Logging, metrics, traces, alerts
+- [ ] **PR**: Lint; Tech Lead review
+- [ ] **Output**: Pipelines, infra code, runbooks in \`dev/platform/\`
 `;
 
 main();

package/package.json

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