@torus-engineering/tas-kit 1.10.0 → 1.11.1

package/.tas/checklists/code-review.md

@@ -1,29 +1,29 @@
 # Code Review Checklist
 
 ## Architecture
-- [ ] Code align với SAD
-- [ ] Không vi phạm ADR nào
-- [ ] Đúng layer separation
+- [ ] Code aligns with SAD
+- [ ] No ADR violations
+- [ ] Correct layer separation
 
 ## Code Quality
-- [ ] Naming theo conventions trong CLAUDE.md
-- [ ] Không có magic numbers/strings
-- [ ] Error handling đầy đủ
-- [ ] Logging có ý nghĩa
-- [ ] Không có code duplication
+- [ ] Naming follows conventions in CLAUDE.md
+- [ ] No magic numbers/strings
+- [ ] Error handling complete
+- [ ] Meaningful logging
+- [ ] No code duplication
 
 ## Security
 - [ ] Input validation
 - [ ] No SQL injection risk
 - [ ] No XSS risk
-- [ ] Sensitive data không log
+- [ ] Sensitive data not logged
 
 ## Testing
 - [ ] Unit tests cover happy path
 - [ ] Unit tests cover edge cases
-- [ ] Tests có assertion rõ ràng
+- [ ] Tests have clear assertions
 
 ## Performance
-- [ ] Không có N+1 query
-- [ ] Async/await đúng cách
-- [ ] Dispose resources properly
+- [ ] No N+1 queries
+- [ ] Async/await used correctly
+- [ ] Resources disposed properly

package/.tas/checklists/security.md

@@ -1,12 +1,12 @@
 # Security Checklist - .NET Specific
 
 ## Authentication & Authorization
-- [ ] JWT validation đúng
+- [ ] JWT validation correct
 - [ ] Role-based authorization
-- [ ] Anti-forgery token cho forms
+- [ ] Anti-forgery token for forms
 
 ## Data Protection
-- [ ] Connection strings trong secrets, không hardcode
+- [ ] Connection strings in secrets, not hardcoded
 - [ ] PII data encrypted at rest
 - [ ] HTTPS enforced
 

package/.tas/checklists/story-done.md

@@ -1,23 +1,23 @@
 # Definition of Done Checklist
 
 ## Code
-- [ ] Code implemented theo acceptance criteria
-- [ ] Tuân thủ conventions trong CLAUDE.md
-- [ ] Mỗi public method có XML doc comment
+- [ ] Code implemented per acceptance criteria
+- [ ] Follows conventions in CLAUDE.md
+- [ ] Each public method has XML doc comment
 
 ## Testing
 - [ ] Unit tests pass (happy path + edge cases + negative cases)
-- [ ] No regression trên existing tests
+- [ ] No regression on existing tests
 
 ## Review
-- [ ] Code review passed (theo code-review checklist)
-- [ ] Nếu auto_review = true, đã qua automated review
+- [ ] Code review passed (per code-review checklist)
+- [ ] If auto_review = true, passed automated review
 
 ## Documentation
-- [ ] Technical notes trong Story cập nhật
-- [ ] Nếu thay đổi API, cập nhật docs tương ứng
+- [ ] Technical notes in Story updated
+- [ ] If API changes, corresponding docs updated
 
 ## Status
-- [ ] Story status cập nhật trong file Story
-- [ ] project-status.yaml cập nhật
-- [ ] Commit message đúng format
+- [ ] Story status updated in Story file
+- [ ] project-status.yaml updated
+- [ ] Commit message follows correct format

package/.tas/project-status-example.yaml

@@ -1,6 +1,6 @@
-# .tas/project-status-example.yaml - Reference template cho root/project-status.yaml
-# /tas-init sẽ tạo file root/project-status.yaml từ template này.
-# Human có thể sửa tay. Chạy /tas-init để đồng bộ lại nếu lệch.
+# .tas/project-status-example.yaml - Reference template for root/project-status.yaml
+# /tas-init will create root/project-status.yaml from this template.
+# Human can edit manually. Run /tas-init to re-sync if drifted.
 last_updated: ""
 
 artifacts:

package/.tas/tas-example.yaml

@@ -1,126 +1,126 @@
-# .tas/tas-example.yaml - Reference template cho tas.yaml ở root
-# Copy file này ra root (tas.yaml) và điền thông tin dự án.
-# File này CHỈ chứa flow và logic của TAS.
-# Tech stack, coding conventions, build commands thuộc về CLAUDE.md.
-
-project:
-  name: "My Project"
-  code: "PROJ"              # Prefix for file naming: PROJ-Epic-001, PROJ-Feature-001, etc.
-  type: greenfield          # greenfield | brownfield
-  description: "Mô tả ngắn về dự án"
-
-# Azure DevOps integration
-ado:
-  enabled: true                 # false nếu project không dùng ADO
-  organization: "https://dev.azure.com/torus-bellesoft"
-  project_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
-
-team:
-  - name: "Nguyen Van A"
-    role: pe
-    ado_id: "nguyenvana@torus.vn"
-  - name: "Tran Van B"
-    role: se
-    ado_id: "tranvanb@torus.vn"
-  - name: "Le Van C"
-    role: dse
-    ado_id: "levanc@torus.vn"
-
-# Flow configuration
-workflow:
-  # Phase 0: Discovery & Design (Human-led, AI-powered)
-  discovery:
-    enabled: true
-    lead: pe
-    artifacts:
-      - prd
-      - design_spec
-      - sad
-      - adr
-      - epic
-      - feature
-      - story
-    gate: ready_for_development
-
-  # Phase 1: Develop (Orchestrated Agentic)
-  develop:
-    enabled: true
-    lead: se
-    environment: test
-    use_tdd: true
-    auto_review: true
-
-  # Phase 2: Verify (Agentic + PE Review)
-  verify:
-    enabled: true
-    lead: pe
-    environment: staging
-    auto_integration_test: true
-    gate: pe_approved
-
-  # Phase 3: Deploy with Feature Flag (Agentic)
-  deploy:
-    enabled: true
-    lead: dse
-    environment: production
-    feature_flag: true
-    gate: pe_approved_production
-
-  # Phase 4: Operate (Autonomous)
-  operate:
-    enabled: false
-    lead: dse
-    environment: production
-    security_check: true
-    performance_monitor: true
-
-# Brownfield-specific config
-brownfield:
-  existing_docs_path: "docs/"
-  codebase_scan_on_init: true
-
-# Pre-commit security hook (installed via tas-kit install --security-hook=husky|native)
-# See .tas/hooks/README.md for details
-#
-# 3-tier scan:
-#   Tier 1 (always): built-in regex scan for ~45 secret patterns — blocks
-#   Tier 2 (if on PATH): gitleaks / trufflehog — only runs if installed — blocks
-#   Tier 3 (opt-in, LOCAL ONLY): AI deep scan → writes docs/security-report.md;
-#                                does NOT block. Use a personal Claude Code
-#                                subscription (no API charges). Not for CI.
-security:
-  pre_commit_hook: true                    # master switch; false to disable without uninstalling
-  external_scanner: auto                   # auto | gitleaks | trufflehog | none — tier 2
-  tool: claude                             # claude | codex | gemini | none — tier 3 AI (report-only)
-  deep_scan_on_every_commit: false         # true = opt into tier 3 AI review each local commit
-  block_on: [critical, high]               # severities that block commit (tier 1 & 2 only)
-  allow_bypass: true                       # print hint about SKIP_SECURITY_SCAN / --no-verify
-
-# Template overrides (optional)
-templates:
-  sad: ".tas/templates/SAD.md"
-  adr: ".tas/templates/ADR.md"
-  prd: ".tas/templates/PRD.md"
-  epic: ".tas/templates/Epic.md"
-  feature: ".tas/templates/Feature.md"
-  story: ".tas/templates/Story.md"
-  bug: ".tas/templates/Bug.md"
-
-# Model mapping
-models:
-  default: sonnet
-  commands:
-    tas-prd: sonnet
-    tas-design: sonnet
-    tas-sad: opus
-    tas-adr: opus
-    tas-epic: sonnet
-    tas-feature: sonnet
-    tas-story: sonnet
-    tas-dev: sonnet
-    tas-review-code: opus
-    tas-brainstorm: opus
-    tas-bug: sonnet
-    tas-verify: haiku
-    tas-status: haiku
-    tas-security-check: opus
+# .tas/tas-example.yaml - Reference template for tas.yaml at root
+# Copy this file to root (tas.yaml) and fill in project information.
+# This file ONLY contains TAS flow and logic.
+# Tech stack, coding conventions, build commands belong in CLAUDE.md.
+
+project:
+  name: "My Project"
+  code: "PROJ"              # Prefix for file naming: PROJ-Epic-001, PROJ-Feature-001, etc.
+  type: greenfield          # greenfield | brownfield
+  description: "Brief project description"
+
+# Azure DevOps integration
+ado:
+  enabled: true                 # false if project doesn't use ADO
+  organization: "https://dev.azure.com/torus-engineering"
+  project_id: "f80dac23-9fa5-4b8e-a1db-da4d5aea7b31"
+
+team:
+  - name: "Nguyen Van A"
+    role: pe
+    ado_id: "nguyenvana@torus.vn"
+  - name: "Tran Van B"
+    role: se
+    ado_id: "tranvanb@torus.vn"
+  - name: "Le Van C"
+    role: dse
+    ado_id: "levanc@torus.vn"
+
+# Flow configuration
+workflow:
+  # Phase 0: Discovery & Design (Human-led, AI-powered)
+  discovery:
+    enabled: true
+    lead: pe
+    artifacts:
+      - prd
+      - design_spec
+      - sad
+      - adr
+      - epic
+      - feature
+      - story
+    gate: ready_for_development
+
+  # Phase 1: Develop (Orchestrated Agentic)
+  develop:
+    enabled: true
+    lead: se
+    environment: test
+    use_tdd: true
+    auto_review: true
+
+  # Phase 2: Verify (Agentic + PE Review)
+  verify:
+    enabled: true
+    lead: pe
+    environment: staging
+    auto_integration_test: true
+    gate: pe_approved
+
+  # Phase 3: Deploy with Feature Flag (Agentic)
+  deploy:
+    enabled: true
+    lead: dse
+    environment: production
+    feature_flag: true
+    gate: pe_approved_production
+
+  # Phase 4: Operate (Autonomous)
+  operate:
+    enabled: false
+    lead: dse
+    environment: production
+    security_check: true
+    performance_monitor: true
+
+# Brownfield-specific config
+brownfield:
+  existing_docs_path: "docs/"
+  codebase_scan_on_init: true
+
+# Pre-commit security hook (installed via tas-kit install --security-hook=husky|native)
+# See .tas/hooks/README.md for details
+#
+# 3-tier scan:
+#   Tier 1 (always): built-in regex scan for ~45 secret patterns — blocks
+#   Tier 2 (if on PATH): gitleaks / trufflehog — only runs if installed — blocks
+#   Tier 3 (opt-in, LOCAL ONLY): AI deep scan → writes docs/security-report.md;
+#                                does NOT block. Use a personal Claude Code
+#                                subscription (no API charges). Not for CI.
+security:
+  pre_commit_hook: true                    # master switch; false to disable without uninstalling
+  external_scanner: auto                   # auto | gitleaks | trufflehog | none — tier 2
+  tool: claude                             # claude | codex | gemini | none — tier 3 AI (report-only)
+  deep_scan_on_every_commit: false         # true = opt into tier 3 AI review each local commit
+  block_on: [critical, high]               # severities that block commit (tier 1 & 2 only)
+  allow_bypass: true                       # print hint about SKIP_SECURITY_SCAN / --no-verify
+
+# Template overrides (optional)
+templates:
+  sad: ".tas/templates/SAD.md"
+  adr: ".tas/templates/ADR.md"
+  prd: ".tas/templates/PRD.md"
+  epic: ".tas/templates/Epic.md"
+  feature: ".tas/templates/Feature.md"
+  story: ".tas/templates/Story.md"
+  bug: ".tas/templates/Bug.md"
+
+# Model mapping
+models:
+  default: sonnet
+  commands:
+    tas-prd: sonnet
+    tas-design: sonnet
+    tas-sad: opus
+    tas-adr: opus
+    tas-epic: sonnet
+    tas-feature: sonnet
+    tas-story: sonnet
+    tas-dev: sonnet
+    tas-review-code: opus
+    tas-brainstorm: opus
+    tas-bug: sonnet
+    tas-verify: haiku
+    tas-status: haiku
+    tas-security-check: opus

package/.tas/templates/ADR.md

@@ -3,29 +3,29 @@
 > **Status:** Proposed | Accepted | Deprecated | Superseded
 > **Date:** [Date]
 > **Author:** [SE name]
-> **Supersedes:** [ADR-NNN nếu có]
-> **Related:** [ADR-NNN nếu có]
+> **Supersedes:** [ADR-NNN if any]
+> **Related:** [ADR-NNN if any]
 
 ## Context
-[Mô tả bối cảnh dẫn đến quyết định này. Vấn đề cần giải quyết là gì?]
+[Describe context leading to this decision. What problem needs solving?]
 
 ## Decision
-[Mô tả quyết định kiến trúc đã chọn.]
+[Describe the chosen architectural decision.]
 
 ## Rationale
-[Tại sao chọn hướng này? Lý do kỹ thuật và kinh doanh.]
+[Why choose this approach? Technical and business reasons.]
 
 ## Alternatives Considered
 
-### Alternative 1: [Tên]
-- **Pros:** [ưu điểm]
-- **Cons:** [nhược điểm]
-- **Lý do không chọn:** [giải thích]
+### Alternative 1: [Name]
+- **Pros:** [advantages]
+- **Cons:** [disadvantages]
+- **Why not chosen:** [explanation]
 
-### Alternative 2: [Tên]
-- **Pros:** [ưu điểm]
-- **Cons:** [nhược điểm]
-- **Lý do không chọn:** [giải thích]
+### Alternative 2: [Name]
+- **Pros:** [advantages]
+- **Cons:** [disadvantages]
+- **Why not chosen:** [explanation]
 
 ## Consequences
 
@@ -38,9 +38,9 @@
 - [consequence 2]
 
 ### SAD Updates
-*(Liệt kê các thay đổi cần cập nhật vào docs/sad.md - chỉ thêm khi ADR ảnh hưởng đến kiến trúc chung)*
-- [ ] [thay đổi 1]
-- [ ] [thay đổi 2]
+*(List changes needed to update docs/sad.md - only add when ADR affects overall architecture)*
+- [ ] [change 1]
+- [ ] [change 2]
 
 ## Changelog
 | Date | Changes | Author |

package/.tas/templates/API-Test-Spec.md

@@ -28,7 +28,7 @@ framework: xUnit
 
 ## Version History
 
-> Mỗi API version có section riêng biệt. APPEND-ONLY: không sửa version cũ.
+> Each API version has separate section. APPEND-ONLY: don't modify old versions.
 
 | Version | Status | Created | Description |
 |---------|--------|---------|-------------|
@@ -354,7 +354,7 @@ framework: xUnit
 
 ## Story-Specific Test Cases (Optional)
 
-> Nếu spec được generate từ Story, thêm AC mapping ở đây.
+> If spec generated from Story, add AC mapping here.
 
 | AC ID | AC Description | Test Case IDs |
 |-------|----------------|---------------|
@@ -365,7 +365,7 @@ framework: xUnit
 
 ## Regression Tests (Optional)
 
-> Test cases cho bugs đã được tìm thấy và fix.
+> Test cases for bugs that were found and fixed.
 
 | Bug ID | Description | Test Case ID | Date Added |
 |--------|-------------|--------------|------------|

package/.tas/templates/Bug.md

@@ -19,7 +19,7 @@ parent_ado_id:
 > **Created:** {Date}
 
 ## Description
-{Mô tả bug ngắn gọn}
+{Brief bug description}
 
 ## Steps to Reproduce
 1. {Step 1}
@@ -27,22 +27,22 @@ parent_ado_id:
 3. {Step 3}
 
 ## Expected Behavior
-{Kết quả mong đợi}
+{Expected result}
 
 ## Actual Behavior
-{Kết quả thực tế}
+{Actual result}
 
 ## Evidence
 {Screenshots, logs, error messages}
 
 ## Root Cause Analysis
-*SE điền khi phân tích*
-- **Root Cause:** {Mô tả nguyên nhân gốc}
-- **Affected Files:** {Danh sách file liên quan}
-- **Impact Scope:** {Ảnh hưởng đến những chức năng nào khác}
+*SE fills when analyzing*
+- **Root Cause:** {Root cause description}
+- **Affected Files:** {List of related files}
+- **Impact Scope:** {Affected functionality}
 
 ## Regression Test Cases
-*SE thiết kế trước khi fix*
+*SE designs before fixing*
 
 | ID | Description | Input | Expected | Status |
 |----|-------------|-------|----------|--------|
@@ -50,13 +50,13 @@ parent_ado_id:
 | RT-2 | Related regression | {input} | {expected} | - |
 
 ## Fix Notes
-*SE ghi sau khi fix*
-- **Fix Description:** {Mô tả cách fix}
-- **Files Changed:** {Danh sách file đã sửa}
+*SE fills after fixing*
+- **Fix Description:** {Fix description}
+- **Files Changed:** {List of changed files}
 - **Commit:** {commit hash}
 
 ## Verify Notes
-*PE ghi khi verify*
+*PE fills when verifying*
 
 | Date | Environment | Result | Verified by | Notes |
 |------|-------------|--------|-------------|-------|

package/.tas/templates/Design-Spec.md

@@ -8,26 +8,26 @@
 ---
 
 ## 1. Overview
-{Tổng quan design}
+{Design overview}
 
 ## 2. User Flows
-<!-- Dùng Mermaid flowchart, :::mermaid wrapper, không dùng () -->
+<!-- Use Mermaid flowchart, :::mermaid wrapper, no () -->
 
 ## 3. Screen Descriptions
 
 ### Screen 1: {Name}
-- **Purpose:** {mục đích}
-- **Key Elements:** {thành phần chính}
-- **Actions Available:** {hành động người dùng có thể thực hiện}
+- **Purpose:** {purpose}
+- **Key Elements:** {key elements}
+- **Actions Available:** {user actions available}
 
 ## 4. Navigation Structure
-<!-- Dùng Mermaid flowchart -->
+<!-- Use Mermaid flowchart -->
 
 ## 5. Interaction Patterns
-{Mô tả patterns: form submission, search, pagination...}
+{Describe patterns: form submission, search, pagination...}
 
 ## 6. Responsive Behavior
-{Mô tả breakpoints và behavior thay đổi}
+{Describe breakpoints and behavior changes}
 
 ---
 

package/.tas/templates/E2E-Execution-Report.md

@@ -51,7 +51,7 @@ environment: # dev | staging | prod
 ### {Test ID}: {Test Description}
 
 **AC Reference**: AC-{N}
-**Failure Reason**: {Mô tả ngắn gọn LÝ DO fail — ví dụ: "Button 'Submit' không hiển thị sau khi nhập email hợp lệ", "API trả về 401 thay vì 200", "Timeout sau 5s chờ màn hình Home load"}
+**Failure Reason**: {Brief description of WHY it failed — e.g.: "Button 'Submit' not visible after entering valid email", "API returns 401 instead of 200", "Timeout after 5s waiting for Home screen to load"}
 **Error Type**: {Assertion Failure | Timeout | Crash | Element Not Found}
 **Error Message**:
 ```

package/.tas/templates/Epic.md

@@ -15,7 +15,7 @@ last_ado_sync:
 > **PRD Reference:** {link to PRD section}
 
 ## Business Value
-{Mô tả giá trị kinh doanh}
+{Business value description}
 
 ## Scope
 ### In Scope

package/.tas/templates/Feature.md

@@ -14,10 +14,10 @@ parent_ado_id:
 > **Epic:** Epic-{NNN}
 > **Owner:** {PE name}
 > **Created:** {Date}
-> **Verified Date:** {Date khi status = Verified}
+> **Verified Date:** {Date when status = Verified}
 
 ## Description
-{Mô tả chức năng}
+{Feature description}
 
 ## User Stories
 | ID | Story | Priority | Estimate | Status |
@@ -29,26 +29,26 @@ parent_ado_id:
 - [ ] AC-2: {criteria}
 
 ## UI/UX Notes
-{Nếu có, reference đến design-spec.md}
+{If any, reference to design-spec.md}
 
 ## Technical Notes
-{Nếu có, reference đến SAD/ADR}
+{If any, reference to SAD/ADR}
 
 ## Integration Test Cases
-PE thiết kế khi tạo Feature. SE implement trong code.
+PE designs when creating Feature. SE implements in code.
 
 | ID | AC Ref | Scenario | Expected Result | Status |
 |----|--------|----------|-----------------|--------|
-| IT-1 | AC-1 | {Mô tả flow liên kết} | {Kết quả mong đợi} | - |
-| IT-2 | AC-2 | {Mô tả flow liên kết} | {Kết quả mong đợi} | - |
+| IT-1 | AC-1 | {Integration flow description} | {Expected result} | - |
+| IT-2 | AC-2 | {Integration flow description} | {Expected result} | - |
 
 ## E2E / Acceptance Test Cases
-PE thiết kế khi tạo Feature. PE verify trên Staging ở Phase 2 bằng /tas-verify.
+PE designs when creating Feature. PE verifies on Staging in Phase 2 using /tas-verify.
 
 | ID | AC Ref | User Scenario | Steps | Expected Result | Status | Verified Date |
 |----|--------|---------------|-------|-----------------|--------|---------------|
-| E2E-1 | AC-1 | {Scenario} | {Bước thực hiện} | {Kết quả mong đợi} | - | - |
-| E2E-2 | AC-2 | {Scenario} | {Bước thực hiện} | {Kết quả mong đợi} | - | - |
+| E2E-1 | AC-1 | {Scenario} | {Execution steps} | {Expected result} | - | - |
+| E2E-2 | AC-2 | {Scenario} | {Execution steps} | {Expected result} | - | - |
 
 ## Changelog
 | Date | Changes | Author |

package/.tas/templates/Func-Test-Spec.md

@@ -23,7 +23,7 @@ platform: # mobile | web | backend
 
 ## Test Case Naming Convention
 
-> Functional Tests dung type code **FT** theo format chuẩn TAS
+> Functional Tests use type code **FT** following TAS standard format
 
 ### Format
 ```
@@ -60,8 +60,8 @@ AL_E002_F002_S001_FT_003_E  - Functional Test Edge case
 
 ## AC to Functional Test Mapping
 
-> QUAN TRONG: Moi FT case PHAI reference AC-ID de dam bao traceability.
-> Khi AC thay doi, grep theo AC-ID de biet FT nao can update.
+> IMPORTANT: Every FT case MUST reference AC-ID to ensure traceability.
+> When AC changes, grep by AC-ID to know which FTs need update.
 
 | AC ID | AC Description (Given/When/Then) | FT Test ID | Test Scenario | Modifier | Priority | Status |
 |-------|----------------------------------|------------|---------------|----------|----------|--------|