sdtk-kit 0.3.8 → 1.0.0

package/assets/toolkit/toolkit/templates/docs/product/PROJECT_INITIATION_TEMPLATE.md

@@ -1,98 +0,0 @@
-# PROJECT INITIATION: {{FEATURE_KEY}}
-
-**Document ID:** PROJECT_INITIATION_{{FEATURE_KEY}}
-**Version:** 1.0.0
-**Date:** {{DATE}}
-**Author:** PM Agent
-**Status:** DRAFT - Ready for BA Analysis
-
----
-
-## 1. EXECUTIVE SUMMARY
-
-**Feature Name:** {{FEATURE_NAME}}
-
-## 2. BUSINESS PROBLEM
-
-### 2.1 Current State
-
-### 2.2 Pain Points
-
-### 2.3 Business Impact
-
----
-
-## 3. HIGH-LEVEL REQUIREMENTS
-
-| Req ID | Requirement | Priority (MUST/SHOULD/COULD) |
-|--------|------------|------------------------------|
-| REQ-01 | TBD | MUST |
-
-### 3.1 User Roles
-
-| Role | Description | Key Capabilities |
-|------|-------------|------------------|
-| Administrator | TBD | TBD |
-
-### 3.2 Key Screens (if UI involved)
-- TBD
-
----
-
-## 4. SUCCESS CRITERIA (Measurable)
-
-| Metric ID | Metric | Target | Measurement Method |
-|-----------|--------|--------|-------------------|
-| SM-01 | TBD | TBD | TBD |
-
----
-
-## 5. RISKS AND DEPENDENCIES
-
-### 5.1 Risks
-| Risk ID | Risk Description | Impact | Probability | Mitigation |
-|---------|------------------|--------|-------------|------------|
-| R-01 | TBD | Medium | Medium | TBD |
-
-### 5.2 Dependencies
-| Dep ID | Dependency | Type | Owner | Status |
-|--------|------------|------|-------|--------|
-| D-01 | TBD | Technical | TBD | TBD |
-
-### 5.3 Open Questions (Clarifications Needed)
-
-| Q-ID | Question | Decision Owner (PM/User) | Needed By (Phase) | Status (OPEN/RESOLVED) | Notes/Options | Resolution |
-|------|----------|---------------------------|-------------------|------------------------|---------------|------------|
-| OQ-01 | TBD | PM | Phase 2 (BA) | OPEN | TBD | TBD |
-
----
-
-## 6. CONSTRAINTS
-
-| Constraint | Description |
-|------------|-------------|
-| Stack | Backend: {{STACK_BACKEND}}; Frontend: {{STACK_FRONTEND}}; DB: {{STACK_DATABASE}} |
-| Auth | {{STACK_AUTH}} |
-
----
-
-## 7. NEXT STEPS
-
-HANDOFF TO BA:
-`@ba please analyze requirements for {{FEATURE_KEY}} and create BA_SPEC_{{FEATURE_KEY}}.md`
-
----
-
-## 8. SOURCE REFERENCES
-
-- Source requirements: `Requirements/...` (if available)
-
----
-
-## APPENDIX A: Original Input (VI/JP) - keep as-is
-
-Paste the original requirement text here without rewriting.
-
-## APPENDIX B: English Translation (of Appendix A)
-
-Provide an English translation of Appendix A (literal, for traceability).

package/assets/toolkit/toolkit/templates/docs/qa/QA_RELEASE_REPORT_TEMPLATE.md

@@ -1,61 +0,0 @@
-# QA Release Report: {{FEATURE_KEY}} ({{FEATURE_NAME}})
-
-**Document ID:** QA_RELEASE_REPORT_{{FEATURE_KEY}}
-**Version:** 1.0.0
-**Date:** {{DATE}}
-**Author:** QA Agent
-**Status:** DRAFT
-
----
-
-## 1. SUMMARY
-
-| Item | Value |
-|------|-------|
-| Release Decision | TBD (APPROVED / REJECTED) |
-| Build/Commit | TBD |
-| Environment | TBD |
-| Test Case Spec | `docs/qa/{{FEATURE_KEY}}_TEST_CASE.md` (if used) |
-
----
-
-## 2. TEST EXECUTION
-
-| Test Type | Result | Notes |
-|-----------|--------|------|
-| Unit | TBD | |
-| Integration | TBD | |
-| E2E | TBD | |
-
----
-
-## 3. DEFECTS
-
-| ID | Severity | Description | Status |
-|----|----------|-------------|--------|
-| BUG-01 | MEDIUM | TBD | OPEN |
-
----
-
-## 4. OPEN QUESTIONS / CLARIFICATIONS
-
-Use this section when acceptance criteria, expected behavior, or scope is unclear. Escalate to PM; if PM cannot resolve from docs, PM must confirm with the user.
-
-| Q-ID | Question | Decision Owner (PM/User) | Status (OPEN/RESOLVED) | Notes/Options | Resolution |
-|------|----------|---------------------------|------------------------|---------------|------------|
-| OQ-01 | TBD | PM | OPEN | TBD | TBD |
-
----
-
-## 5. RELEASE GATE
-
-- [ ] 0 HIGH severity open
-- [ ] Coverage meets targets
-- [ ] NFRs met (performance/security)
-
----
-
-## 6. HANDOFF
-
-If APPROVED:
-`@pm please finalize release status for {{FEATURE_KEY}}`

package/assets/toolkit/toolkit/templates/docs/qa/TEST_CASE_CREATION_RULES.md

@@ -1,129 +0,0 @@
-# TEST CASE CREATION RULES
-## Canonical rules for `[FEATURE_KEY]_TEST_CASE.md`
-
-**Version:** 1.0.0  
-**Last Updated:** 2026-02-25
-
----
-
-## 1. Purpose
-- Standardize creation of feature test-case documents in markdown.
-- Mirror Excel-style worksheet layout while keeping output reviewable in `.md`.
-- Keep QA artifacts reusable across projects, domains, and screen sets.
-
----
-
-## 2. Output Contract
-- Primary output file:
-  - `docs/qa/[FEATURE_KEY]_TEST_CASE.md`
-- Optional language/project variant:
-  - `docs/en/qa/[FEATURE_KEY]_TEST_CASE.md` (only when the project explicitly uses `docs/en/**`).
-
----
-
-## 3. Required Section Order
-1. Document metadata (`Document ID`, `Version`, `Date`, `Author`, `Status`)
-2. `Statistic Summary (Excel-aligned)`
-3. `Abbreviations`
-4. `1. Scope`
-5. `2. References`
-6. `3. Test Environment and Common Data`
-7. `4. Feature Coverage Matrix`
-8. `5. Screen-based Test Cases (Excel-aligned)`
-9. `6. Open Questions (for final freeze)`
-10. `7. STC/UAT Note`
-
-Do not reorder these sections unless the user requests a different contract.
-
----
-
-## 4. Statistic Summary Rules
-- Place summary near the top of the file (before detailed UTC/ITC tables).
-- Keep columns aligned with Excel `Statistic` logic:
-  - `Num of Case`
-  - `OK`
-  - `NG`
-  - `Not tested yet`
-  - `Done (%)`
-  - `Updated Date`
-- Compute:
-  - `Not tested yet = Num of Case - (OK + NG)`
-  - `Done (%) = (OK + NG) / Num of Case`
-- Include subtotal rows at minimum:
-  - `Unit Test Total`
-  - `Integration Test Total`
-  - `Grand Total`
-
----
-
-## 5. Screen-Based Worksheet Mapping
-- Use `screen-first` layout to mirror Excel tabs:
-  - Each functional screen has a section (for example `SCH01`, `SCH02`, ...).
-  - Each screen section can have 2 sub-sections:
-    - `UTC` worksheet (name pattern: `[SCREEN_KEY]_UTC`)
-    - `ITC` worksheet (name pattern: `[SCREEN_KEY]_ITC`)
-- Add one mapping table in section 5 that lists:
-  - `Screen`
-  - `Suggested Worksheet Pair`
-  - `UTC Cases`
-  - `ITC Cases`
-  - `Notes`
-
----
-
-## 6. Test Case Table Schema (Mandatory)
-- Use one unified 18-column schema for both UTC and ITC tables:
-  - `No`
-  - `Test Type`
-  - `Test Perspective`
-  - `Test Item`
-  - `Precondition`
-  - `Test Steps`
-  - `Expected Result`
-  - `Browser`
-  - `Test Execution Result`
-  - `Remarks`
-  - `Reviewer`
-  - `Review Date`
-  - `OK/NG`
-  - `Cause`
-  - `Countermeasure`
-  - `Owner`
-  - `Completion Date`
-  - `Confirmation`
-
----
-
-## 7. Numbering and ID Policy
-- Keep a stable `No` for each test case row.
-- Do not renumber existing case IDs only for visual regrouping.
-- In screen-split sections, case IDs may be non-contiguous; this is allowed.
-- Summary/helper tables must keep contiguous `No` (`1,2,3,...`).
-
----
-
-## 8. Open Questions (OQ) Policy
-- If expected behavior is unclear, create `OQ-xx` entries in section 6.
-- Do not assume behavior for:
-  - permission matrix
-  - conflict dialog/action semantics
-  - API contract ambiguities
-  - release-scope boundary
-- When resolved, keep question row and set status/remarks to resolved.
-
----
-
-## 9. Language and Encoding
-- Default artifact language: English.
-- Keep original JP/VI labels when required by business/UI traceability (for example button labels).
-- File encoding must be UTF-8.
-- Avoid mojibake and placeholder tokens (`??`, `?????`) in final output.
-
----
-
-## 10. Final Validation Checklist
-- Required sections exist and are in correct order.
-- Statistic totals equal sum of UTC/ITC rows.
-- Screen mapping table case counts match actual UTC/ITC table counts.
-- Scope explicitly states in-scope and out-of-scope boundaries.
-- Open questions are explicitly tracked with owner and impact.

package/assets/toolkit/toolkit/templates/docs/qa/TEST_CASE_TEMPLATE.md

@@ -1,104 +0,0 @@
-# {{FEATURE_KEY}} TEST CASE
-
-**Document ID:** TEST_CASE_{{FEATURE_KEY}}  
-**Version:** 1.0.0  
-**Date:** {{DATE}}  
-**Author:** QA Agent  
-**Status:** DRAFT
-
----
-
-## Statistic Summary (Excel-aligned)
-
-| No | Test Group | Worksheet Mapping (Markdown) | Num of Case | OK | NG | Not tested yet | Done (%) | Updated Date |
-| ---: | --- | --- | ---: | ---: | ---: | ---: | ---: | --- |
-| 1 | Unit Test Total | `UT Total` | 0 | 0 | 0 | 0 | 0.00% | {{DATE}} |
-| 2 | Integration Test Total | `IT Total` | 0 | 0 | 0 | 0 | 0.00% | {{DATE}} |
-| 3 | Grand Total | `Total` | 0 | 0 | 0 | 0 | 0.00% | {{DATE}} |
-
----
-
-## Abbreviations
-
-| No | Abbreviation | Meaning |
-| ---: | --- | --- |
-| 1 | UTC | Unit Test Case |
-| 2 | ITC | Integration Test Case |
-| 3 | STC | System Test Case |
-| 4 | UAT | User Acceptance Test |
-| 5 | OQ | Open Question |
-
----
-
-## 1. Scope
-
-- In scope: `TBD`
-- Out of scope: `TBD`
-- Notes: `TBD`
-
----
-
-## 2. References
-
-| No | Document | Usage |
-| ---: | --- | --- |
-| 1 | `docs/specs/BA_SPEC_{{FEATURE_KEY}}.md` | Business rules and acceptance criteria |
-| 2 | `docs/architecture/ARCH_DESIGN_{{FEATURE_KEY}}.md` | Architecture scope and constraints |
-| 3 | `docs/api/{{FEATURE_KEY}}_ENDPOINTS.md` | API contracts and status/error policy |
-| 4 | `docs/specs/{{FEATURE_KEY}}_FLOW_ACTION_SPEC.md` | Screen behavior and flow actions |
-
----
-
-## 3. Test Environment and Common Data
-
-| No | Item | Value |
-| ---: | --- | --- |
-| 1 | Browser | Chrome (latest stable) |
-| 2 | Auth | TBD |
-| 3 | Environment | TBD |
-| 4 | Seed data | TBD |
-| 5 | Error policy | TBD |
-
----
-
-## 4. Feature Coverage Matrix
-
-| No | Feature Block | Screens | Primary APIs |
-| ---: | --- | --- | --- |
-| 1 | TBD | TBD | TBD |
-
----
-
-## 5. Screen-based Test Cases (Excel-aligned)
-
-| No | Screen | Suggested Worksheet Pair | UTC Cases | ITC Cases | Notes |
-| ---: | --- | --- | ---: | ---: | --- |
-| 1 | SCREEN-001 | `SCREEN001_UTC`, `SCREEN001_ITC` | 0 | 0 | TBD |
-
-### 5.1 SCREEN-001
-
-#### 5.1.1 UTC (`SCREEN001_UTC`)
-
-| No | Test Type | Test Perspective | Test Item | Precondition | Test Steps | Expected Result | Browser | Test Execution Result | Remarks | Reviewer | Review Date | OK/NG | Cause | Countermeasure | Owner | Completion Date | Confirmation |
-| ---: | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| 1 | Normal | TBD | TBD | TBD | TBD | TBD | Chrome | TBD |  |  |  |  |  |  |  |  |  |
-
-#### 5.1.2 ITC (`SCREEN001_ITC`)
-
-| No | Test Type | Test Perspective | Test Item | Precondition | Test Steps | Expected Result | Browser | Test Execution Result | Remarks | Reviewer | Review Date | OK/NG | Cause | Countermeasure | Owner | Completion Date | Confirmation |
-| ---: | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| 1 | Normal | TBD | TBD | TBD | TBD | TBD | Chrome | TBD |  |  |  |  |  |  |  |  |  |
-
----
-
-## 6. Open Questions (for final freeze)
-
-| No | Q-ID | Question | Impact | Owner |
-| ---: | --- | --- | --- | --- |
-| 1 | OQ-01 | TBD | TBD | PM / Customer |
-
----
-
-## 7. STC/UAT Note
-
-If STC/UAT template is unavailable, keep STC/UAT as tracked backlog items and map to future release gates.

package/assets/toolkit/toolkit/templates/docs/specs/BA_SPEC_TEMPLATE.md

@@ -1,139 +0,0 @@
-# BA SPEC: {{FEATURE_KEY}} ({{FEATURE_NAME}})
-
-**Document ID:** BA_SPEC_{{FEATURE_KEY}}
-**Version:** 1.0.0
-**Date:** {{DATE}}
-**Author:** BA Agent
-**Status:** DRAFT - Ready for PM Review
-
----
-
-## Abbreviations
-
-| No | Abbreviation | Meaning |
-| ---: | --- | --- |
-| 1 | API | Application Programming Interface |
-| 2 | DB | Database |
-| 3 | UI | User Interface |
-| 4 | UX | User Experience |
-| 5 | BR | Business Rule |
-| 6 | UC | Use Case |
-| 7 | AC | Acceptance Criteria |
-| 8 | NFR | Non-Functional Requirement |
-| 9 | OQ | Open Question |
-| 10 | REQ | Requirement |
-
----
-
-## 1. DOMAIN ANALYSIS
-
-### 1.1 Domain Glossary
-
-| No | Term | Definition | Example |
-| ---: | --- | --- | --- |
-| 1 | TBD | TBD | TBD |
-
-### 1.2 Business Rules
-
-| No | Rule ID | Rule Description | Type | Related REQ |
-| ---: | --- | --- | --- | --- |
-| 1 | BR-01 | TBD | Mandatory | REQ-01 |
-
-### 1.3 Non-Functional Requirements
-
-| No | NFR ID | Category | Requirement | Target |
-| ---: | --- | --- | --- | --- |
-| 1 | NFR-01 | Performance | TBD | TBD |
-
----
-
-## 2. USE CASES
-
-| No | UC ID | Use Case Name | Primary Actor | Related REQ |
-| ---: | --- | --- | --- | --- |
-| 1 | UC-01 | TBD | TBD | REQ-01 |
-
----
-
-## 3. DATA MODEL (Logical)
-
-| No | Entity | Description | Key Fields |
-| ---: | --- | --- | --- |
-| 1 | TBD | TBD | TBD |
-
----
-
-## 4. CONTRACTS SUMMARY
-
-### 4.1 API Endpoints (High-level)
-
-| No | Endpoint | Method | Purpose | Related UC |
-| ---: | --- | --- | --- | --- |
-| 1 | `/api/v1/...` | GET | TBD | UC-01 |
-
-### 4.2 UI Screens (if applicable)
-
-| No | Screen ID | Screen Name | Purpose | Related UC |
-| ---: | --- | --- | --- | --- |
-| 1 | SCR-01 | TBD | TBD | UC-01 |
-
-### 4.3 Acceptance Criteria (high-level)
-
-| No | AC ID | Acceptance Criteria | Related UC | Related BR |
-| ---: | --- | --- | --- | --- |
-| 1 | AC-01-01 | TBD | UC-01 | BR-01 |
-
----
-
-## 5. RISKS & OPEN QUESTIONS
-
-### 5.1 Risks
-
-| No | Risk ID | Risk | Probability | Impact | Mitigation |
-| ---: | --- | --- | --- | --- | --- |
-| 1 | R-01 | TBD | Medium | Medium | TBD |
-
-### 5.2 Open Questions
-
-| No | Q-ID | Question | Type | Priority | Decision Owner (PM/User) | Status (OPEN/RESOLVED) | Notes/Options | Resolution |
-| ---: | --- | --- | --- | --- | --- | --- | --- | --- |
-| 1 | OQ-01 | TBD | Business | High | PM | OPEN | TBD | TBD |
-
----
-
-## 6. TRACEABILITY SUMMARY
-
-| No | REQ ID | Use Cases | Business Rules | Acceptance Criteria | Status |
-| ---: | --- | --- | --- | --- | --- |
-| 1 | REQ-01 | UC-01 | BR-01 | AC-01-01 | COVERED |
-
----
-
-## 7. HANDOFF
-
-HANDOFF TO PM:
-`@pm BA_SPEC_{{FEATURE_KEY}} is ready. Please create PRD_{{FEATURE_KEY}}.md + BACKLOG_{{FEATURE_KEY}}.md`
-
-Next:
-`@arch please design architecture for {{FEATURE_KEY}} after PM review`
-
-NOTE:
-`@pm please resolve Open Questions (OQ-xx) above; if any cannot be resolved from existing docs, please confirm with the user (final stakeholder).`
-
----
-
-## APPENDIX A: Source Requirements (Original VI/JP) - keep as-is
-
-If the input requirements were provided in Vietnamese/Japanese, paste them here unchanged.
-
-## APPENDIX B: English Translation (of Appendix A)
-
-Provide an English translation of Appendix A (literal, for traceability).
-
----
-
-## Document History
-
-| No | Version | Date | Author | Changes |
-| ---: | --- | --- | --- | --- |
-| 1 | 1.0.0 | {{DATE}} | BA Agent | Initial template-based version |