npm - @ngocsangairvds/vsaf - Versions diffs - 3.2.16 → 4.0.1 - Mend

@ngocsangairvds/vsaf 3.2.16 → 4.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2337) hide show

package/tools/bmad/bmm/1-analysis/bmad-document-project/templates/srs-system-template.md DELETED Viewed

@@ -1,430 +0,0 @@
-# Software Requirements Specification (SRS)
-## {{TÊN HỆ THỐNG}}
-| Thông tin | Chi tiết |
-|---|---|
-| **Dự án** | {{Tên dự án đầy đủ}} |
-| **Phiên bản** | {{X.Y}} |
-| **Trạng thái** | Draft |
-| **Ngày tạo** | {{YYYY-MM-DD}} |
-| **Người soạn** | {{Tên / Team}} |
-| **Nguồn** | {{Danh sách tài liệu nguồn: PRD, Architecture, BRD, Epics,...}} |
-### Lịch sử phiên bản
-| Phiên bản | Ngày | Người thực hiện | Nội dung thay đổi |
-|---|---|---|---|
-| {{X.Y}} | {{YYYY-MM-DD}} | {{Tên}} | {{Mô tả thay đổi}} |
-### Bảng phê duyệt
-| Vai trò | Họ tên | Chữ ký | Ngày |
-|---|---|---|---|
-| BA Lead | | | |
-| Product Owner | | | |
-| CTO / Tech Lead | | | |
-| Legal / Compliance | | | |
-| UX Lead | | | |
----
-## 1. Giới thiệu
-### 1.1 Mục đích tài liệu
-{{Mô tả mục đích SRS — tài liệu này phục vụ ai, dùng để làm gì}}
-Tài liệu phục vụ:
-- Làm cơ sở cho thiết kế kỹ thuật (Architecture, SDD)
-- Cơ sở viết test plan và test cases
-- Xác nhận scope và chức năng với stakeholders
-- {{Thêm mục đích khác nếu cần}}
-### 1.2 Đối tượng đọc
-| Đối tượng | Mục đích sử dụng |
-|---|---|
-| BA Team | Tài liệu gốc để phát triển và kiểm soát thay đổi |
-| Dev Team | Hiểu yêu cầu để thiết kế và lập trình |
-| Test Lead | Cơ sở viết test plan và test case |
-| Product Owner | Xác nhận scope, phân kỳ |
-| {{Thêm đối tượng khác}} | {{Mục đích}} |
-### 1.3 Phạm vi hệ thống
-**In-scope (MVP — Phase 1):**
-- {{Module/Feature 1}} (FR range)
-- {{Module/Feature 2}} (FR range)
-- ...
-**Out-of-scope (Phase 2/3):**
-- {{Feature}} — Phase X
-- ...
-### 1.4 Định nghĩa & Từ viết tắt
-| Thuật ngữ / Viết tắt | Giải thích |
-|---|---|
-| SRS | Software Requirements Specification |
-| UC | Use Case |
-| FR | Functional Requirement |
-| NFR | Non-Functional Requirement |
-| BR | Business Rule |
-| RTM | Requirements Traceability Matrix |
-| {{Thêm thuật ngữ domain}} | {{Giải thích}} |
-### 1.5 Tài liệu tham chiếu
-| Tài liệu | Phiên bản | Vị trí |
-|---|---|---|
-| {{Tên tài liệu}} | {{vX.Y}} | {{Đường dẫn}} |
-| ... | | |
----
-## 2. Tổng quan hệ thống
-### 2.1 Mô tả sản phẩm
-{{Mô tả tổng quan hệ thống: giải quyết vấn đề gì, mô hình hoạt động, MVP scope}}
-### 2.2 Sơ đồ ngữ cảnh hệ thống (System Context Diagram)
-```mermaid
-graph LR
-    actor1([Actor 1]) --> system[Hệ thống]
-    actor2([Actor 2]) --> system
-    system --> ext1[External System 1]
-    system --> ext2[External System 2]
-```
-### 2.3 Môi trường vận hành
-| Hạng mục | Chi tiết |
-|---|---|
-| Nền tảng | {{Web / Mobile / WebView / API}} |
-| Trình duyệt hỗ trợ | {{Chrome X+, Safari X+,...}} |
-| Hạ tầng | {{Cloud provider, deployment model}} |
-| Backend | {{Tech stack}} |
-| Database | {{DB technologies}} |
-| Message Broker | {{Nếu có}} |
-| API Gateway | {{Nếu có}} |
-| Auth | {{Auth solution}} |
-### 2.4 Actors và đặc điểm người dùng
-| Actor | Mô tả | Tần suất | Kênh | Mức kỹ thuật |
-|---|---|---|---|---|
-| **{{Persona 1}}** | {{Mô tả}} | {{Tần suất}} | {{Kênh}} | {{Mức}} |
-| **{{Persona 2}}** | {{Mô tả}} | {{Tần suất}} | {{Kênh}} | {{Mức}} |
-### 2.5 Module Map
-```mermaid
-graph LR
-    actor1([Actor]) --> m1[Module 1]
-    actor1 --> m2[Module 2]
-    actor2([Actor 2]) --> m3[Module 3]
-```
-| Module | Flows | FRs | Priority |
-|---|---|---|---|
-| **{{M1: Tên module}}** | Flow XX | FR range | Must Have / Should Have |
-| **{{M2: Tên module}}** | Flow XX | FR range | Must Have / Should Have |
-### 2.6 Kiến trúc tích hợp
-| Hệ thống bên ngoài | Loại | Mục đích | Giao thức | Chiều | SLA |
-|---|---|---|---|---|---|
-| {{Tên hệ thống}} | Partner / Third-party | {{Mục đích}} | {{REST/SOAP/File}} | Inbound / Outbound / Bidirectional | {{SLA}} |
-### 2.7 Giả định và phụ thuộc cấp hệ thống
-**Giả định:**
-- A1: {{Giả định 1}}
-- A2: {{Giả định 2}}
-**Phụ thuộc:**
-- D1: {{Phụ thuộc 1 — hậu quả nếu không có}}
-- D2: {{Phụ thuộc 2 — hậu quả nếu không có}}
----
-## 3. Yêu cầu chức năng (Functional Requirements)
-> **ID scheme:** `UC-[MODULE]-[NNN]` | **Business Rule:** `BR-[NNN]` | **Thông báo:** `MSG-[NNN]`
-### 3.X Module X — {{Tên Module}} (Flow XX)
-> **Tài liệu chi tiết:** Xem `srs/SRS-{{code}}-FlowXX-vX.Y.md` (nếu có SRS feature-level riêng)
-**Tóm tắt UCs:**
-| UC ID | Tên | Actor | Priority | FRs |
-|---|---|---|---|---|
-| UC-MX-001 | {{Tên UC}} | {{Actor}} | Must Have | {{FR range}} |
----
-#### UC-MX-001: {{Tên Use Case}}
-| Thông tin | Chi tiết |
-|---|---|
-| **ID** | UC-MX-001 |
-| **Tên** | {{Tên UC}} |
-| **Mô tả** | {{Mô tả ngắn gọn}} |
-| **Ưu tiên** | Must Have / Should Have / Could Have |
-| **Trạng thái** | Draft |
-| **Nguồn** | {{PRD vX FR range}} |
-| **Actor** | {{Actor chính}} |
-| **Kênh** | {{Kênh sử dụng}} |
-| **Đường dẫn chức năng** | {{Navigation path}} |
-| **Trigger** | {{Sự kiện kích hoạt}} |
-| **Tần suất sử dụng** | {{Tần suất}} |
-| **Điều kiện tiên quyết** | {{Preconditions}} |
-**Luồng chính (Main Flow):**
-1. {{Bước 1}}
-2. {{Bước 2}}
-3. ...
-> Khi UC ≥5 bước hoặc ≥2 lần rẽ nhánh, **bắt buộc** kèm sequence diagram và/hoặc activity diagram (PlantUML). Xem mẫu trong `srs-feature-template.md` §3.1, §3.2.
-**Luồng thay thế:**
-- **Alt-1 — {{Tên}}:** {{Mô tả}}
-- **Alt-2 — {{Tên}}:** {{Mô tả}}
-**Luồng ngoại lệ:**
-- **Exc-1 — {{Tên}}:** {{Mô tả}}
-**Hậu điều kiện:**
-- Thành công: {{Kết quả khi thành công}}
-- Thất bại: {{Kết quả khi thất bại}}
-**Yêu cầu dữ liệu:**
-| Trường | Kiểu | Bắt buộc | Validation | Ghi chú |
-|---|---|---|---|---|
-| {{field_name}} | {{String/Integer/Enum/Date/...}} | Có/Không | {{Rule}} | {{Ghi chú}} |
-**Business Rules:**
-| Mã | Nội dung | Tham chiếu |
-|---|---|---|
-| BR-XXX | {{Nội dung rule}} | {{PRD/FR/NFR reference}} |
-**Các thông báo hệ thống:**
-| Mã | Loại | Nội dung | Điều kiện |
-|---|---|---|---|
-| MSG-XXX | Success/Error/Info/Push | {{Nội dung thông báo}} | {{Điều kiện hiển thị}} |
-**Phương pháp kiểm thử:** {{Manual / API test / E2E automation / Integration test / Load test}}
----
-> **Lặp lại section 3.X cho mỗi Module. Lặp lại UC block cho mỗi Use Case trong module.**
----
-## 4. Yêu cầu phi chức năng (Non-Functional Requirements)
-### 4.1 Hiệu năng (Performance)
-| ID | Yêu cầu | Tiêu chí chấp nhận |
-|---|---|---|
-| NFR-PERF-001 | {{Yêu cầu}} | {{p95 / p99 / SLA}} |
-### 4.2 Bảo mật (Security)
-| ID | Yêu cầu | Tiêu chí chấp nhận |
-|---|---|---|
-| NFR-SEC-001 | {{Yêu cầu}} | {{Tiêu chí}} |
-### 4.3 Khả dụng & Độ tin cậy (Availability)
-| ID | Yêu cầu | Tiêu chí chấp nhận |
-|---|---|---|
-| NFR-AVAIL-001 | {{Yêu cầu}} | {{% uptime}} |
-| NFR-REL-001 | RPO | {{< X minutes}} |
-| NFR-REL-002 | RTO | {{< X hours}} |
-### 4.4 Khả dụng với người dùng (Usability)
-| ID | Yêu cầu | Tiêu chí chấp nhận |
-|---|---|---|
-| NFR-USAB-001 | {{Accessibility — WCAG level}} | {{VD: WCAG 2.1 Level AA cho contrast, font size}} |
-| NFR-USAB-002 | {{Learnability — thời gian onboarding}} | {{VD: User hoàn thành task chính trong ≤X phút lần đầu}} |
-| NFR-USAB-003 | {{Error recovery — khả năng phục hồi}} | {{VD: Mọi lỗi có hướng dẫn sửa, undo trong ≤X bước}} |
-| NFR-USAB-004 | {{Đa ngôn ngữ / Localization}} | {{VD: Hỗ trợ vi-VN, en-US}} |
-### 4.5 Khả năng mở rộng (Scalability)
-| ID | Yêu cầu | MVP | Year 1 |
-|---|---|---|---|
-| NFR-SCALE-001 | {{Yêu cầu}} | {{MVP target}} | {{Year 1 target}} |
-### 4.7 Tuân thủ quy định (Compliance)
-| ID | Yêu cầu | Quy định | Tiêu chí |
-|---|---|---|---|
-| NFR-COMP-001 | {{Yêu cầu}} | {{Tên quy định}} | {{Tiêu chí}} |
-### 4.8 Audit & Ghi log
-| ID | Yêu cầu | Tiêu chí |
-|---|---|---|
-| NFR-AUDIT-001 | {{Scope}} | {{Chi tiết}} |
-| NFR-AUDIT-002 | Retention | {{>= X years}} |
-### 4.9 Monitoring & Alerting
-| ID | Yêu cầu | Tiêu chí |
-|---|---|---|
-| NFR-MON-001 | {{Dashboard / metric}} | {{Chi tiết}} |
-### 4.10 Khả năng bảo trì (Maintainability)
-| ID | Yêu cầu | Tiêu chí chấp nhận |
-|---|---|---|
-| NFR-MAINT-001 | {{Code quality / test coverage}} | {{VD: Unit test coverage ≥X%, SonarQube quality gate pass}} |
-| NFR-MAINT-002 | {{Documentation}} | {{VD: API docs auto-generated (OpenAPI 3.x), architecture docs up-to-date}} |
-| NFR-MAINT-003 | {{Modular design}} | {{VD: Microservices loosely coupled, thay thế 1 service không ảnh hưởng service khác}} |
-### 4.11 Khả năng di chuyển (Portability)
-| ID | Yêu cầu | Tiêu chí chấp nhận |
-|---|---|---|
-| NFR-PORT-001 | {{Platform independence}} | {{VD: Containerized (Docker/K8s), không vendor-locked}} |
-| NFR-PORT-002 | {{Database portability}} | {{VD: Dùng standard SQL, tránh vendor-specific extensions}} |
-| NFR-PORT-003 | {{Multi-channel support}} | {{VD: API-first, hỗ trợ embed vào host app khác ngoài channel hiện tại}} |
----
-## 5. Ràng buộc, Giả định & Phụ thuộc
-### 5.1 Ràng buộc kỹ thuật
-- {{Ràng buộc tech stack}}
-- {{Ràng buộc deployment}}
-- {{Ràng buộc infra}}
-### 5.2 Ràng buộc quy định pháp lý
-- {{Ràng buộc pháp lý 1}}
-- {{Ràng buộc pháp lý 2}}
-### 5.3 Yêu cầu chuyển đổi (Transition Requirements)
-> *(ISO 29148 §6.4 + BABOK v3 §7.4.3 — bắt buộc khi hệ thống thay thế/migrate từ hệ thống cũ)*
-| # | Yêu cầu | Mô tả | Owner | Timeline |
-|---|---|---|---|---|
-| TR-001 | {{Data migration}} | {{VD: Migrate X records từ hệ thống cũ, mapping rules, validation}} | {{Team}} | {{Sprint/Phase}} |
-| TR-002 | {{Parallel-run}} | {{VD: Chạy song song old/new system trong X tuần, so sánh output}} | {{Team}} | {{Period}} |
-| TR-003 | {{Rollback plan}} | {{VD: Nếu migration fail, rollback trong ≤X giờ, data intact}} | {{Team}} | {{Trigger}} |
-| TR-004 | {{User training / communication}} | {{VD: Training cho X users trước go-live, hướng dẫn sử dụng}} | {{Team}} | {{Before go-live}} |
-> Nếu không có migration/chuyển đổi, ghi rõ: "Không áp dụng — hệ thống mới hoàn toàn."
-### 5.4 Rủi ro ảnh hưởng đến yêu cầu
-| Rủi ro | Mức độ | Ảnh hưởng | Biện pháp |
-|---|---|---|---|
-| {{Rủi ro}} | Cao/Trung bình/Thấp | {{Module/Feature bị ảnh hưởng}} | {{Mitigation}} |
----
-## 6. Ma trận truy xuất yêu cầu (RTM)
-| PRD FR | UC ID | Module | Màn hình | Epic/Story |
-|---|---|---|---|---|
-| {{FR ID}} | {{UC ID}} | {{Module}} | {{Screen name}} | {{Epic/Story ref}} |
----
-## 7. Phụ lục
-### A. Danh sách màn hình (Screen Inventory)
-| Màn hình | Module | Figma/Screenshot | UC liên quan |
-|---|---|---|---|
-| {{Tên màn hình}} | {{Module}} | {{Đường dẫn}} | {{UC ID}} |
-### B. Business Rules Index
-| Mã | Nội dung | Module | UC |
-|---|---|---|---|
-| BR-XXX→YYY | {{Nhóm rule}} | {{Module}} | {{UC ID}} |
-### C. Open Issues
-| # | Vấn đề | Module | Người phụ trách | Hạn | Trạng thái |
-|---|---|---|---|---|---|
-| OI-X | {{Vấn đề}} | {{Module}} | {{Người}} | {{Deadline}} | Open |
-### D. Danh sách thông báo hệ thống (Message Catalog)
-| Mã | Loại | Nội dung | UC |
-|---|---|---|---|
-| MSG-XXX | Success/Error/Info/Push | {{Nội dung}} | {{UC ID}} |
-### E. Data Dictionary
-> *(ISO 29148 §6.4.3.8 Logical database requirements + BABOK v3 §7.1 Data Models)*
-| Thực thể | Thuộc tính | Kiểu dữ liệu | Ràng buộc | Bắt buộc | Mô tả | Hệ thống nguồn |
-|---|---|---|---|---|---|---|
-| {{Entity}} | {{field_name}} | {{String/Integer/Date/Enum/UUID}} | {{FK, Unique, Check,...}} | Có/Không | {{Mô tả nghiệp vụ}} | {{NTBH / Insurer / Channel}} |
-### F. CRUD Matrix
-| Use Case | {{Entity 1}} | {{Entity 2}} | {{Entity 3}} | {{Entity 4}} |
-|---|---|---|---|---|
-| UC-MX-001 | C | R | — | — |
-| UC-MX-002 | R | U | C | — |
-| UC-MX-003 | — | R | R | D |
-> C=Create, R=Read, U=Update, D=Delete, —=Không tác động
-### G. State Diagrams — Entity Lifecycle
-> *(BABOK v3 §7.1 State Diagrams — bắt buộc cho entities có ≥3 trạng thái)*
-**{{Entity name}} Lifecycle:**
-```mermaid
-stateDiagram-v2
-    [*] --> {{State1}}: {{Trigger}}
-    {{State1}} --> {{State2}}: {{Event/Action}}
-    {{State2}} --> {{State3}}: {{Event/Action}}
-    {{State2}} --> {{State4}}: {{Event/Action}}
-    {{State3}} --> [*]
-    {{State4}} --> [*]
-```
-| Trạng thái | Mô tả | Trigger chuyển trạng thái | Ai thực hiện |
-|---|---|---|---|
-| {{State1}} | {{Mô tả}} | {{Event}} | {{Actor/System}} |
-| {{State2}} | {{Mô tả}} | {{Event}} | {{Actor/System}} |
-> Lặp lại cho mỗi entity có lifecycle phức tạp (VD: Policy, Claim, Transaction, Order, Payment).
-### H. Verification Summary
-> *(ISO 29148 §6.4.4 — cross-reference giữa requirements và phương pháp kiểm thử)*
-| Module | UC ID | Phương pháp kiểm thử | Test Coverage | Ghi chú |
-|---|---|---|---|---|
-| {{Module}} | UC-MX-001 | {{Manual / API / E2E / Integration / Load / Security}} | {{Unit + Integration + E2E}} | {{Ghi chú đặc biệt}} |
-| {{Module}} | UC-MX-002 | {{...}} | {{...}} | |
-**Tổng hợp per module:**
-| Module | Tổng UC | Manual | API Test | E2E | Integration | Load | Security |
-|---|---|---|---|---|---|---|---|
-| {{M1}} | {{X}} | {{X}} | {{X}} | {{X}} | {{X}} | {{X}} | {{X}} |
----
-*Tài liệu cần review bởi: {{Danh sách reviewer roles}} trước khi baseline.*

package/tools/bmad/bmm/config.yaml DELETED Viewed

@@ -1,20 +0,0 @@
-# BMM Module Configuration
-# Generated by BMAD installer
-# Version: 6.3.0
-# Date: 2026-04-16T02:18:17.832Z
-project_name: vsaf
-user_skill_level: intermediate
-planning_artifacts: "{project-root}/_bmad-output/planning-artifacts"
-implementation_artifacts: "{project-root}/_bmad-output/implementation-artifacts"
-project_knowledge: "{project-root}/docs"
-# Core Configuration Values
-user_name: DuongOT
-communication_language: English
-document_output_language: English
-output_folder: "{project-root}/_bmad-output"
-# Confluence Integration (set by /vsaf-push-prd or /vsaf-push-srs on first use)
-confluence_space_key: ""
-confluence_parent_page: ""

package/tools/bmad/bmm/module-help.csv DELETED Viewed

@@ -1,33 +0,0 @@
-module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
-BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
-BMad Method,bmad-document-project,Document Project,DP,Analyze an existing project to produce useful documentation.,,anytime,,,false,project-knowledge,*
-BMad Method,bmad-generate-project-context,Generate Project Context,GPC,Scan existing codebase to generate a lean LLM-optimized project-context.md. Essential for brownfield projects.,,anytime,,,false,output_folder,project context
-BMad Method,bmad-quick-dev,Quick Dev,QQ,Unified intent-in code-out workflow: clarify plan implement review and present.,,anytime,,,false,implementation_artifacts,spec and project implementation
-BMad Method,bmad-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,anytime,,,false,planning_artifacts,change proposal
-BMad Method,bmad-agent-tech-writer,Write Document,WD,"Describe in detail what you want, and the agent will follow documentation best practices. Multi-turn conversation with subprocess for research/review.",write,,anytime,,,false,project-knowledge,document
-BMad Method,bmad-agent-tech-writer,Update Standards,US,Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.,update-standards,,anytime,,,false,_bmad/_memory/tech-writer-sidecar,standards
-BMad Method,bmad-agent-tech-writer,Mermaid Generate,MG,Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.,mermaid,,anytime,,,false,planning_artifacts,mermaid diagram
-BMad Method,bmad-agent-tech-writer,Validate Document,VD,Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.,validate,[path],anytime,,,false,planning_artifacts,validation report
-BMad Method,bmad-agent-tech-writer,Explain Concept,EC,Create clear technical explanations with examples and diagrams for complex concepts.,explain,[topic],anytime,,,false,project_knowledge,explanation
-BMad Method,bmad-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,1-analysis,,,false,planning_artifacts,brainstorming session
-BMad Method,bmad-market-research,Market Research,MR,"Market analysis competitive landscape customer needs and trends.",,1-analysis,,,false,"planning_artifacts|project-knowledge",research documents
-BMad Method,bmad-domain-research,Domain Research,DR,Industry domain deep dive subject matter expertise and terminology.,,1-analysis,,,false,"planning_artifacts|project_knowledge",research documents
-BMad Method,bmad-technical-research,Technical Research,TR,Technical feasibility architecture options and implementation approaches.,,1-analysis,,,false,"planning_artifacts|project_knowledge",research documents
-BMad Method,bmad-product-brief,Create Brief,CB,An expert guided experience to nail down your product idea in a brief. a gentler approach than PRFAQ when you are already sure of your concept and nothing will sway you.,,-A,1-analysis,,,false,planning_artifacts,product brief
-BMad Method,bmad-prfaq,PRFAQ Challenge,WB,Working Backwards guided experience to forge and stress-test your product concept to ensure you have a great product that users will love and need through the PRFAQ gauntlet to determine feasibility and alignment with user needs. alternative to product brief.,,-H,1-analysis,,,false,planning_artifacts,prfaq document
-BMad Method,bmad-create-prd,Create PRD,CP,Expert led facilitation to produce your Product Requirements Document.,,2-planning,,,true,planning_artifacts,prd
-BMad Method,bmad-validate-prd,Validate PRD,VP,,,[path],2-planning,bmad-create-prd,,false,planning_artifacts,prd validation report
-BMad Method,bmad-edit-prd,Edit PRD,EP,,,[path],2-planning,bmad-validate-prd,,false,planning_artifacts,updated prd
-BMad Method,bmad-create-ux-design,Create UX,CU,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project.",,2-planning,bmad-create-prd,,false,planning_artifacts,ux design
-BMad Method,bmad-create-architecture,Create Architecture,CA,Guided workflow to document technical decisions.,,3-solutioning,,,true,planning_artifacts,architecture
-BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,,,3-solutioning,bmad-create-architecture,,true,planning_artifacts,epics and stories
-BMad Method,bmad-check-implementation-readiness,Check Implementation Readiness,IR,Ensure PRD UX Architecture and Epics Stories are aligned.,,3-solutioning,bmad-create-epics-and-stories,,true,planning_artifacts,readiness report
-BMad Method,bmad-sprint-planning,Sprint Planning,SP,Kicks off implementation by producing a plan the implementation agents will follow in sequence for every story.,,4-implementation,,,true,implementation_artifacts,sprint status
-BMad Method,bmad-sprint-status,Sprint Status,SS,Anytime: Summarize sprint status and route to next workflow.,,4-implementation,bmad-sprint-planning,,false,,
-BMad Method,bmad-create-story,Create Story,CS,"Story cycle start: Prepare first found story in the sprint plan that is next or a specific epic/story designation.",create,,4-implementation,bmad-sprint-planning,bmad-create-story:validate,true,implementation_artifacts,story
-BMad Method,bmad-create-story,Validate Story,VS,Validates story readiness and completeness before development work begins.,validate,,4-implementation,bmad-create-story:create,bmad-dev-story,false,implementation_artifacts,story validation report
-BMad Method,bmad-dev-story,Dev Story,DS,Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed.,,4-implementation,bmad-create-story:validate,,true,,
-BMad Method,bmad-code-review,Code Review,CR,Story cycle: If issues back to DS if approved then next CS or ER if epic complete.,,4-implementation,bmad-dev-story,,false,,
-BMad Method,bmad-checkpoint-preview,Checkpoint,CK,Guided walkthrough of a change from purpose and context into details. Use for human review of commits branches or PRs.,,4-implementation,,,false,,
-BMad Method,bmad-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,4-implementation,bmad-dev-story,,false,implementation_artifacts,test suite
-BMad Method,bmad-retrospective,Retrospective,ER,Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC.,,4-implementation,bmad-code-review,,false,implementation_artifacts,retrospective

package/tools/bmad/core/config.yaml DELETED Viewed

@@ -1,9 +0,0 @@
-# CORE Module Configuration
-# Generated by BMAD installer
-# Version: 6.3.0
-# Date: 2026-04-16T02:18:17.832Z
-user_name: DuongOT
-communication_language: English
-document_output_language: English
-output_folder: "{project-root}/_bmad-output"

package/tools/bmad/core/module-help.csv DELETED Viewed

@@ -1,12 +0,0 @@
-module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
-Core,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
-Core,bmad-brainstorming,Brainstorming,BSP,Use early in ideation or when stuck generating ideas.,,anytime,,,false,{output_folder}/brainstorming,brainstorming session
-Core,bmad-party-mode,Party Mode,PM,Orchestrate multi-agent discussions when you need multiple perspectives or want agents to collaborate.,,anytime,,,false,,
-Core,bmad-help,BMad Help,BH,,,anytime,,,false,,
-Core,bmad-index-docs,Index Docs,ID,Use when LLM needs to understand available docs without loading everything.,,anytime,,,false,,
-Core,bmad-shard-doc,Shard Document,SD,Use when doc becomes too large (>500 lines) to manage effectively.,[path],anytime,,,false,,
-Core,bmad-editorial-review-prose,Editorial Review - Prose,EP,Use after drafting to polish written content.,[path],anytime,,,false,report located with target document,three-column markdown table with suggested fixes
-Core,bmad-editorial-review-structure,Editorial Review - Structure,ES,Use when doc produced from multiple subprocesses or needs structural improvement.,[path],anytime,,,false,report located with target document,
-Core,bmad-review-adversarial-general,Adversarial Review,AR,"Use for quality assurance or before finalizing deliverables. Code Review in other modules runs this automatically, but also useful for document reviews.",[path],anytime,,,false,,
-Core,bmad-review-edge-case-hunter,Edge Case Hunter Review,ECH,Use alongside adversarial review for orthogonal coverage — method-driven not attitude-driven.,[path],anytime,,,false,,
-Core,bmad-distillator,Distillator,DG,Use when you need token-efficient distillates that preserve all information for downstream LLM consumption.,[path],anytime,,,false,adjacent to source document or specified output_path,distillate markdown file(s)

package/tools/skills/bmad-agent-architect/SKILL.md DELETED Viewed

@@ -1,54 +0,0 @@
----
-name: bmad-agent-architect
-description: System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.
----
-# Winston
-## Overview
-This skill provides a System Architect who guides users through technical design decisions, distributed systems planning, and scalable architecture. Act as Winston — a senior architect who balances vision with pragmatism, helping users make technology choices that ship successfully while scaling when needed.
-## Identity
-Senior architect with expertise in distributed systems, cloud infrastructure, and API design who specializes in scalable patterns and technology selection.
-## Communication Style
-Speaks in calm, pragmatic tones, balancing "what could be" with "what should be." Grounds every recommendation in real-world trade-offs and practical constraints.
-## Principles
-- Channel expert lean architecture wisdom: draw upon deep knowledge of distributed systems, cloud patterns, scalability trade-offs, and what actually ships successfully.
-- User journeys drive technical decisions. Embrace boring technology for stability.
-- Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact.
-You must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.
-When you are in this persona and the user calls a skill, this persona must carry through and remain active.
-## Capabilities
-| Code | Description | Skill |
-|------|-------------|-------|
-| CA | Guided workflow to document technical decisions to keep implementation on track | bmad-create-architecture |
-| IR | Ensure the PRD, UX, Architecture and Epics and Stories List are all aligned | bmad-check-implementation-readiness |
-## On Activation
-1. Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
-   - Use `{user_name}` for greeting
-   - Use `{communication_language}` for all communications
-   - Use `{document_output_language}` for output documents
-   - Use `{planning_artifacts}` for output location and artifact scanning
-   - Use `{project_knowledge}` for additional context scanning
-2. **Continue with steps below:**
-   - **Load project context** — Search for `**/project-context.md`. If found, load as foundational reference for project standards and conventions. If not found, continue without it.
-   - **Greet and present capabilities** — Greet `{user_name}` warmly by name, always speaking in `{communication_language}` and applying your persona throughout the session.
-3. Remind the user they can invoke the `bmad-help` skill at any time for advice and then present the capabilities table from the Capabilities section above.
-   **STOP and WAIT for user input** — Do NOT execute menu items automatically. Accept number, menu code, or fuzzy command match.
-**CRITICAL Handling:** When user responds with a code, line number or skill, invoke the corresponding skill by its exact registered name from the Capabilities table. DO NOT invent capabilities on the fly.

package/tools/skills/bmad-agent-architect/bmad-skill-manifest.yaml DELETED Viewed

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-agent-architect
-displayName: Winston
-title: Architect
-icon: "🏗️"
-capabilities: "distributed systems, cloud infrastructure, API design, scalable patterns"
-role: System Architect + Technical Design Leader
-identity: "Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection."
-communicationStyle: "Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.'"
-principles: "Channel expert lean architecture wisdom: draw upon deep knowledge of distributed systems, cloud patterns, scalability trade-offs, and what actually ships successfully. User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact."
-module: bmm

package/tools/skills/bmad-agent-dev/SKILL.md DELETED Viewed

@@ -1,69 +0,0 @@
----
-name: bmad-agent-dev
-description: Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
----
-# Amelia
-## Overview
-This skill provides a Senior Software Engineer who executes approved stories with strict adherence to story details and team standards. Act as Amelia — ultra-precise, test-driven, and relentlessly focused on shipping working code that meets every acceptance criterion.
-## Identity
-Senior software engineer who executes approved stories with strict adherence to story details and team standards and practices.
-## Communication Style
-Ultra-succinct. Speaks in file paths and AC IDs — every statement citable. No fluff, all precision.
-## Principles
-- All existing and new tests must pass 100% before story is ready for review.
-- Every task/subtask must be covered by comprehensive unit tests before marking an item complete.
-## Critical Actions
-- READ the entire story file BEFORE any implementation — tasks/subtasks sequence is your authoritative implementation guide
-- Execute tasks/subtasks IN ORDER as written in story file — no skipping, no reordering
-- Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing
-- Run full test suite after each task — NEVER proceed with failing tests
-- Execute continuously without pausing until all tasks/subtasks are complete
-- Document in story file Dev Agent Record what was implemented, tests created, and any decisions made
-- Update story file File List with ALL changed files after each task completion
-- NEVER lie about tests being written or passing — tests must actually exist and pass 100%
-You must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.
-When you are in this persona and the user calls a skill, this persona must carry through and remain active.
-## Capabilities
-| Code | Description | Skill |
-|------|-------------|-------|
-| DS | Write the next or specified story's tests and code | bmad-dev-story |
-| QD | Unified quick flow — clarify intent, plan, implement, review, present | bmad-quick-dev |
-| QA | Generate API and E2E tests for existing features | bmad-qa-generate-e2e-tests |
-| CR | Initiate a comprehensive code review across multiple quality facets | bmad-code-review |
-| SP | Generate or update the sprint plan that sequences tasks for implementation | bmad-sprint-planning |
-| CS | Prepare a story with all required context for implementation | bmad-create-story |
-| ER | Party mode review of all work completed across an epic | bmad-retrospective |
-## On Activation
-1. Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
-   - Use `{user_name}` for greeting
-   - Use `{communication_language}` for all communications
-   - Use `{document_output_language}` for output documents
-   - Use `{planning_artifacts}` for output location and artifact scanning
-   - Use `{project_knowledge}` for additional context scanning
-2. **Continue with steps below:**
-   - **Load project context** — Search for `**/project-context.md`. If found, load as foundational reference for project standards and conventions. If not found, continue without it.
-   - **Greet and present capabilities** — Greet `{user_name}` warmly by name, always speaking in `{communication_language}` and applying your persona throughout the session.
-3. Remind the user they can invoke the `bmad-help` skill at any time for advice and then present the capabilities table from the Capabilities section above.
-   **STOP and WAIT for user input** — Do NOT execute menu items automatically. Accept number, menu code, or fuzzy command match.
-**CRITICAL Handling:** When user responds with a code, line number or skill, invoke the corresponding skill by its exact registered name from the Capabilities table. DO NOT invent capabilities on the fly.

package/tools/skills/bmad-agent-dev/bmad-skill-manifest.yaml DELETED Viewed

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-agent-dev
-displayName: Amelia
-title: Developer Agent
-icon: "💻"
-capabilities: "story execution, test-driven development, code implementation"
-role: Senior Software Engineer
-identity: "Executes approved stories with strict adherence to story details and team standards and practices."
-communicationStyle: "Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision."
-principles: "All existing and new tests must pass 100% before story is ready for review. Every task/subtask must be covered by comprehensive unit tests before marking an item complete."
-module: bmm