sdtk-kit 0.3.0

package/assets/toolkit/toolkit/templates/docs/design/DESIGN_LAYOUT_TEMPLATE.md

@@ -0,0 +1,49 @@
+# Screen Layout Design: {{FEATURE_KEY}} ({{FEATURE_NAME}})
+
+**Document ID:** DESIGN_LAYOUT_{{FEATURE_KEY}}
+**Version:** 1.0.0
+**Date:** {{DATE}}
+**Author:** ARCH Agent
+**Status:** DRAFT - Ready for DEV Review
+
+---
+
+## Abbreviations
+
+| No | Abbreviation | Meaning |
+| ---: | --- | --- |
+| 1 | UI | User Interface |
+| 2 | API | Application Programming Interface |
+| 3 | OQ | Open Question |
+
+---
+
+## Screen List
+
+| No | Screen ID | Screen Name | Description |
+| ---: | --- | --- | --- |
+| 1 | A-1 | TBD | TBD |
+
+---
+
+## A-1. TBD
+
+```plantuml
+@startsalt
+{
+  { "① TBD" | [② Action] }
+}
+@endsalt
+```
+
+### API List
+
+| No | API ID | Endpoint |
+| ---: | --- | --- |
+| 1 | API-1 | TBD |
+
+### Items
+
+| No | Item | Type | Required | Notes |
+| ---: | --- | --- | --- | --- |
+| 1 | TBD | text | - | TBD |

package/assets/toolkit/toolkit/templates/docs/dev/FEATURE_IMPL_PLAN_TEMPLATE.md

@@ -0,0 +1,73 @@
+# Feature Implementation Plan: {{FEATURE_KEY}} ({{FEATURE_NAME}})
+
+**Document ID:** FEATURE_IMPL_PLAN_{{FEATURE_KEY}}
+**Version:** 1.0.0
+**Date:** {{DATE}}
+**Author:** DEV Agent
+**Status:** DRAFT
+
+---
+
+## 1. OVERVIEW
+
+### 1.1 Source Documents
+- `docs/architecture/ARCH_DESIGN_{{FEATURE_KEY}}.md`
+- `docs/product/BACKLOG_{{FEATURE_KEY}}.md`
+- (optional) `docs/api/{{FEATURE_PASCAL}}_API.yaml`
+- (optional) `docs/design/DESIGN_LAYOUT_{{FEATURE_KEY}}.md`
+
+### 1.2 Tech Stack (project-level)
+- Backend: {{STACK_BACKEND}}
+- Frontend: {{STACK_FRONTEND}}
+- Mobile: {{STACK_MOBILE}}
+- Database: {{STACK_DATABASE}}
+- Auth: {{STACK_AUTH}}
+
+### 1.3 Local Commands (project-level)
+- Backend tests: `{{CMD_BACKEND_TESTS}}`
+- Backend typecheck: `{{CMD_BACKEND_TYPECHECK}}`
+- Backend lint: `{{CMD_BACKEND_LINT}}`
+- Frontend tests: `{{CMD_FRONTEND_TESTS}}`
+- Frontend lint: `{{CMD_FRONTEND_LINT}}`
+- E2E tests: `{{CMD_E2E_TESTS}}`
+
+---
+
+## 2. IMPLEMENTATION SCOPE
+
+### 2.1 Backend
+- TBD
+
+### 2.2 Frontend
+- TBD
+
+---
+
+## 3. OPEN QUESTIONS / CLARIFICATIONS
+
+| Q-ID | Question | Decision Owner (PM/User) | Status (OPEN/RESOLVED) | Notes/Options | Resolution |
+|------|----------|---------------------------|------------------------|---------------|------------|
+| OQ-01 | TBD | PM | OPEN | TBD | TBD |
+
+---
+
+## 4. TEST PLAN
+
+- Unit tests: target TBD
+- Integration tests: target TBD
+- E2E tests (if applicable): target TBD
+
+---
+
+## 5. CODE REVIEW (MANDATORY)
+
+- [ ] Self review complete
+- [ ] Peer review requested (AI peer review allowed)
+- [ ] Peer comments addressed
+- [ ] Approved
+
+---
+
+## 6. HANDOFF TO QA
+
+`@qa please test {{FEATURE_KEY}} (after Code Review PASS)`

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

@@ -0,0 +1,50 @@
+# BACKLOG: {{FEATURE_KEY}} ({{FEATURE_NAME}})
+
+**Document ID:** BACKLOG_{{FEATURE_KEY}}
+**Version:** 1.0.0
+**Date:** {{DATE}}
+**Author:** PM Agent
+**Status:** DRAFT - Ready for ARCH Review
+
+---
+
+## BACKLOG SUMMARY
+
+| Priority | Count | Stories |
+|----------|-------|---------|
+| **Must Have** | TBD | US-01... |
+
+---
+
+## EPIC-01: TBD
+
+### US-01: TBD
+
+**Priority:** Must Have | **Effort:** TBD | **Sprint:** TBD
+
+**Story:**
+As a <role>, I want <capability>, so that <benefit>.
+
+**Acceptance Criteria:**
+- [ ] AC-01.1: TBD
+
+**Dependencies:** TBD
+
+**Traceability:** UC-01, BR-01
+
+---
+
+## DEFINITION OF DONE
+
+- [ ] All acceptance criteria verified
+- [ ] Tests added and passing
+- [ ] Code review complete
+- [ ] Docs updated
+
+---
+
+## OPEN QUESTIONS (Backlog Clarifications)
+
+| Q-ID | Question | Related Epic/Story | Decision Owner (PM/User) | Status (OPEN/RESOLVED) | Resolution |
+|------|----------|--------------------|---------------------------|------------------------|------------|
+| OQ-01 | TBD | EPIC-01 / US-01 | PM | OPEN | TBD |

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

@@ -0,0 +1,66 @@
+# PRD: {{FEATURE_KEY}} ({{FEATURE_NAME}})
+
+**Document ID:** PRD_{{FEATURE_KEY}}
+**Version:** 1.0.0
+**Date:** {{DATE}}
+**Author:** PM Agent
+**Status:** DRAFT - Ready for ARCH Review
+**Source:** BA_SPEC_{{FEATURE_KEY}}.md
+
+---
+
+## 1. EXECUTIVE SUMMARY
+
+## 2. GOALS & SUCCESS METRICS
+
+| Goal ID | Goal | Success Metric | Target |
+|---------|------|----------------|--------|
+| G-01 | TBD | TBD | TBD |
+
+---
+
+## 3. PERSONAS / USER ROLES
+
+## 4. FEATURE OVERVIEW
+
+### 4.1 Feature Map (by Use Case)
+| Use Case | Feature | Priority | Epic |
+|----------|---------|----------|------|
+| UC-01 | TBD | Must | EPIC-01 |
+
+---
+
+## 5. RELEASE CRITERIA
+
+| RC ID | Criterion | Verification |
+|-------|----------|--------------|
+| RC-01 | TBD | QA report |
+
+---
+
+## 6. RISKS & OPEN QUESTIONS
+
+### 6.1 Risks
+
+| Risk ID | Risk | Probability | Impact | Mitigation |
+|---------|------|-------------|--------|------------|
+| R-01 | TBD | Medium | Medium | TBD |
+
+### 6.2 Open Questions (Clarifications Needed)
+
+| Q-ID | Question | Decision Owner (PM/User) | Needed By (Phase) | Status (OPEN/RESOLVED) | Notes/Options | Resolution |
+|------|----------|---------------------------|-------------------|------------------------|---------------|------------|
+| OQ-01 | TBD | User | Phase 3 (ARCH) | OPEN | TBD | TBD |
+
+### 6.3 Decision Log (PM)
+
+| D-ID | Decision | Rationale | Decided By (PM/User) | Date | Related Q-ID |
+|------|----------|-----------|----------------------|------|--------------|
+| D-01 | TBD | TBD | PM | {{DATE}} | OQ-01 |
+
+---
+
+## 7. NEXT ACTION
+
+HANDOFF TO ARCH:
+`@arch please design technical solution for {{FEATURE_KEY}} based on BA_SPEC + PRD + BACKLOG`

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

@@ -0,0 +1,98 @@
+# 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

@@ -0,0 +1,61 @@
+# 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

@@ -0,0 +1,129 @@
+# 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

@@ -0,0 +1,104 @@
+# {{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.