sdtk-kit 0.3.2 → 0.3.3

package/README.md

@@ -16,7 +16,7 @@ npm link
 
 ```bash
 # 1. Initialize workspace with runtime adapter
-sdtk init --runtime codex
+sdtk init --runtime claude
 
 # 2. Store GitHub token for entitlement
 sdtk auth --token ghp_xxxxxxxxxxxx
@@ -24,6 +24,9 @@ sdtk auth --verify
 
 # 3. Generate feature documentation (17 files)
 sdtk generate --feature-key USER_PROFILE --feature-name "User Profile"
+# Codex runtime remains available:
+# sdtk init --runtime codex
+
 ```
 
 ## Commands
@@ -41,6 +44,7 @@ Creates:
 - `sdtk.config.json` -- project configuration
 - `sdtk.config.profiles.example.json` -- stack profile examples
 - `CODEX.md` or `CLAUDE.md` -- runtime adapter
+- for `--runtime claude`, local `.claude/skills` and `.claude/skills/references` are installed unless `--skip-skills` is used
 
 ### `sdtk auth`
 
@@ -128,4 +132,3 @@ npm run verify:payload
 # Smoke test npm pack
 npm run pack:smoke
 ```
-

package/assets/manifest/toolkit-bundle.manifest.json

@@ -1,20 +1,20 @@
 {
-    "buildTimestamp":  "2026-03-03T11:32:21Z",
+    "buildTimestamp":  "2026-03-07T00:53:22Z",
     "files":  [
                   {
                       "path":  "toolkit/AGENTS.md",
-                      "sha256":  "c6eeae87c70925803869ae90d0aa033eb12852c174019f373f62382d25b3a7e3",
-                      "size":  5060
+                      "sha256":  "868430474b46e4e8d27ed26b780a794936e84cf4f0278f2cc3d061f54877f498",
+                      "size":  5113
                   },
                   {
                       "path":  "toolkit/install.ps1",
-                      "sha256":  "cc717ae87a0dbcf5aef2204d45211fe59f9506f9d03314eb283eddb3a5997279",
-                      "size":  5519
+                      "sha256":  "531da17e88a05b6946a5012f7b13a2871212df1fe0d052720f9511e02aba7e32",
+                      "size":  8830
                   },
                   {
                       "path":  "toolkit/runtimes/claude/CLAUDE_TEMPLATE.md",
-                      "sha256":  "fdf45036d4c0079cdb03e65efb7b5a84ea130e67a4c82522bb93c2bb73aa6661",
-                      "size":  882
+                      "sha256":  "0f3e0bfe1b5165250f0da4da5790a9e6220023752713088a0076eb7f17fd6397",
+                      "size":  1933
                   },
                   {
                       "path":  "toolkit/runtimes/codex/CODEX_TEMPLATE.md",
@@ -211,6 +211,71 @@
                       "sha256":  "72ca16e07c286910333243954610e116217ca2abb3a5e276cbe91e92eb826ad5",
                       "size":  2652
                   },
+                  {
+                      "path":  "toolkit/skills-claude/api-design-spec/SKILL.md",
+                      "sha256":  "123873681ff65792a9a269b264155c65a5feb68b23e4eeb1e68cb7da1a137d54",
+                      "size":  3252
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/api-doc/SKILL.md",
+                      "sha256":  "57176bb3d74e19ef5feb1a8d59d8c7c1714634f67e1d51bf4667d3f189093319",
+                      "size":  2240
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/arch/SKILL.md",
+                      "sha256":  "5ab03dc8a928c6528d1ccaad427a15c686427e8fd9114421da495d9223652337",
+                      "size":  4108
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/ba/SKILL.md",
+                      "sha256":  "1956fd69ff1a0adb54c8abbf06b37bd5c21b7f0ca597b6d8b94dfed0606cd2e4",
+                      "size":  2551
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/design-layout/SKILL.md",
+                      "sha256":  "9765f229108c5aff27457489707218570ad83dc362353a79c2f5a78607adf4de",
+                      "size":  840
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/dev/SKILL.md",
+                      "sha256":  "cea9f6512bc805d5b22a84a4ef8dbd229b4f7a3f073f9e125e933e6e79a206d5",
+                      "size":  2505
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/dev-backend/SKILL.md",
+                      "sha256":  "142a8fe088a4b0326ca79e00200cb5f562c53728b7adc83e6b749db6e29f1d0d",
+                      "size":  841
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/dev-frontend/SKILL.md",
+                      "sha256":  "1631bd51bc3d0106c18f4c00412f6279626bdce9f0e310822d5dcdff08063a88",
+                      "size":  800
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/orchestrator/SKILL.md",
+                      "sha256":  "c8e8303f1833e71cacdf20b1f398e476b44b3de14fbffad9a404c2a68fa713a3",
+                      "size":  4046
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/pm/SKILL.md",
+                      "sha256":  "b34621fe61957e573c616ad816d591a60a6c8d1333d0bfb71f39f45b93331cb0",
+                      "size":  3043
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/qa/SKILL.md",
+                      "sha256":  "eb0a540d28144855b5026e7b40ce965c4049a9b56f6e7ffd9732964006f63d1a",
+                      "size":  2687
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/screen-design-spec/SKILL.md",
+                      "sha256":  "5686da60872f1a3c6791e9a740897d4a564f40d53d54902a47fbc3165e68a1ec",
+                      "size":  3261
+                  },
+                  {
+                      "path":  "toolkit/skills-claude/test-case-spec/SKILL.md",
+                      "sha256":  "efd43e2087961f4e30177144c42e06b6c9b3d73f9533dad34f9ce1284fcdf126",
+                      "size":  2625
+                  },
                   {
                       "path":  "toolkit/templates/docs/api/API_DESIGN_CREATION_RULES.md",
                       "sha256":  "9adf1e46833411a861fb7426c37baac69689b9e3120a8ed1e4a3224de44a8dd2",
@@ -332,7 +397,7 @@
                       "size":  3255
                   }
               ],
-    "sourceCommit":  "bf9a10e9ccde3a1c4809836b2da20fc6e3ad07df",
-    "version":  "0.3.2",
-    "fileCount":  66
+    "sourceCommit":  "4437ad41659a38e9e80dcbf32cb03f9b6df64e0d",
+    "version":  "0.3.3",
+    "fileCount":  79
 }

package/assets/manifest/toolkit-bundle.sha256.txt

@@ -1,6 +1,6 @@
-c6eeae87c70925803869ae90d0aa033eb12852c174019f373f62382d25b3a7e3  toolkit/AGENTS.md
-cc717ae87a0dbcf5aef2204d45211fe59f9506f9d03314eb283eddb3a5997279  toolkit/install.ps1
-fdf45036d4c0079cdb03e65efb7b5a84ea130e67a4c82522bb93c2bb73aa6661  toolkit/runtimes/claude/CLAUDE_TEMPLATE.md
+868430474b46e4e8d27ed26b780a794936e84cf4f0278f2cc3d061f54877f498  toolkit/AGENTS.md
+531da17e88a05b6946a5012f7b13a2871212df1fe0d052720f9511e02aba7e32  toolkit/install.ps1
+0f3e0bfe1b5165250f0da4da5790a9e6220023752713088a0076eb7f17fd6397  toolkit/runtimes/claude/CLAUDE_TEMPLATE.md
 4154c15c71f44d2f2caf07fb41722fa65d4f9ec7e78f798ee084effd12345c62  toolkit/runtimes/codex/CODEX_TEMPLATE.md
 5c1f5442fd3c26b8bf62db4b25e9f1c4207258c7fe52f12ed533968f77dfbf65  toolkit/scripts/init-feature.ps1
 68a82e421d0309e47cdb79e949b1044c17375ad7fd52e2ab9ccdc9dd33f8cdd0  toolkit/scripts/install-codex-skills.ps1
@@ -40,6 +40,19 @@ ae0bc9b120c19a142f10cc79168a8f7d6bf8a37e48341fc16cbc74bbdc2e692c  toolkit/skills
 7c21e74f5eee712c6b65665b4f10483ed008113186a92dc0a4673ce1fcd3ef5c  toolkit/skills/sdtk-test-case-spec/references/TEST_CASE_CREATION_RULES.md
 4d1e813908114f2be68007fb7373973e2c6e0aebc5a6305b8b19443d5ae477d0  toolkit/skills/sdtk-test-case-spec/scripts/validate_test_case_spec.py
 72ca16e07c286910333243954610e116217ca2abb3a5e276cbe91e92eb826ad5  toolkit/skills/sdtk-test-case-spec/SKILL.md
+123873681ff65792a9a269b264155c65a5feb68b23e4eeb1e68cb7da1a137d54  toolkit/skills-claude/api-design-spec/SKILL.md
+57176bb3d74e19ef5feb1a8d59d8c7c1714634f67e1d51bf4667d3f189093319  toolkit/skills-claude/api-doc/SKILL.md
+5ab03dc8a928c6528d1ccaad427a15c686427e8fd9114421da495d9223652337  toolkit/skills-claude/arch/SKILL.md
+1956fd69ff1a0adb54c8abbf06b37bd5c21b7f0ca597b6d8b94dfed0606cd2e4  toolkit/skills-claude/ba/SKILL.md
+9765f229108c5aff27457489707218570ad83dc362353a79c2f5a78607adf4de  toolkit/skills-claude/design-layout/SKILL.md
+cea9f6512bc805d5b22a84a4ef8dbd229b4f7a3f073f9e125e933e6e79a206d5  toolkit/skills-claude/dev/SKILL.md
+142a8fe088a4b0326ca79e00200cb5f562c53728b7adc83e6b749db6e29f1d0d  toolkit/skills-claude/dev-backend/SKILL.md
+1631bd51bc3d0106c18f4c00412f6279626bdce9f0e310822d5dcdff08063a88  toolkit/skills-claude/dev-frontend/SKILL.md
+c8e8303f1833e71cacdf20b1f398e476b44b3de14fbffad9a404c2a68fa713a3  toolkit/skills-claude/orchestrator/SKILL.md
+b34621fe61957e573c616ad816d591a60a6c8d1333d0bfb71f39f45b93331cb0  toolkit/skills-claude/pm/SKILL.md
+eb0a540d28144855b5026e7b40ce965c4049a9b56f6e7ffd9732964006f63d1a  toolkit/skills-claude/qa/SKILL.md
+5686da60872f1a3c6791e9a740897d4a564f40d53d54902a47fbc3165e68a1ec  toolkit/skills-claude/screen-design-spec/SKILL.md
+efd43e2087961f4e30177144c42e06b6c9b3d73f9533dad34f9ce1284fcdf126  toolkit/skills-claude/test-case-spec/SKILL.md
 9adf1e46833411a861fb7426c37baac69689b9e3120a8ed1e4a3224de44a8dd2  toolkit/templates/docs/api/API_DESIGN_CREATION_RULES.md
 d2aa0ee3a7c5351700b3bffb4ba66e8056ed955f55903c744c694624730038cb  toolkit/templates/docs/api/API_DESIGN_DETAIL_TEMPLATE.md
 13f26a3307894b9bfb570d75f6db4ccb61104064d19661ec2a26a1b9984f4c97  toolkit/templates/docs/api/API_DESIGN_FLOWCHART_CREATION_RULES.md

package/assets/toolkit/toolkit/AGENTS.md

@@ -59,9 +59,9 @@ Notes:
 ## 5) Feature Bootstrap
 Run from project root:
 
-`powershell -ExecutionPolicy Bypass -File ".\\toolkit\\scripts\\init-feature.ps1" -FeatureKey YOUR_FEATURE -FeatureName "Your Feature"`
-
-Or create artifacts manually from templates in `toolkit/templates/`.
+```
+sdtk generate --feature-key YOUR_FEATURE --feature-name "Your Feature"
+```
 
 ## 6) ARCH Deliverables (Extended)
 In addition to `ARCH_DESIGN`, ARCH may generate:
@@ -90,16 +90,20 @@ In addition to `ARCH_DESIGN`, ARCH may generate:
   - `off`: skip unless explicitly requested.
 
 ## 7) Mandatory Rule References
-- API YAML docs:
-  - `toolkit/templates/docs/api/YAML_CREATION_RULES.md`
-- API design detail + flow docs:
-  - `toolkit/templates/docs/api/API_DESIGN_FLOWCHART_CREATION_RULES.md`
-- Compatibility notes kept for legacy references:
-  - `toolkit/templates/docs/api/FLOWCHART_CREATION_RULES.md`
-  - `toolkit/templates/docs/api/API_DESIGN_CREATION_RULES.md`
-- Screen flow-action specs:
-  - `toolkit/templates/docs/specs/FLOW_ACTION_SPEC_CREATION_RULES.md`
-- QA test-case specs:
-  - `toolkit/templates/docs/qa/TEST_CASE_CREATION_RULES.md`
-- Flow-action numbering policy:
-  - Use one global numbering mode for the whole document (no per-screen reset).
+Rule files are installed locally by the runtime. Skills resolve these at:
+- Claude Code: `.claude/skills/references/`
+- Codex: `$CODEX_HOME/skills/<skill>/references/`
+
+Available rule files:
+- `YAML_CREATION_RULES.md` — API YAML docs
+- `API_DESIGN_FLOWCHART_CREATION_RULES.md` — API design detail + flow docs
+- `FLOWCHART_CREATION_RULES.md` — Flowchart (legacy compat)
+- `API_DESIGN_CREATION_RULES.md` — API design (legacy compat)
+- `FLOW_ACTION_SPEC_CREATION_RULES.md` — Screen flow-action specs
+- `TEST_CASE_CREATION_RULES.md` — QA test-case specs
+- `numbering-rules.md` — Flow-action numbering policy
+- `figma-mcp.md` — Figma MCP integration
+- `excel-image-export.md` — Excel image export
+
+Flow-action numbering policy:
+- Use one global numbering mode for the whole document (no per-screen reset).

package/assets/toolkit/toolkit/install.ps1

@@ -80,6 +80,94 @@ function Install-RuntimeAdapter {
   throw "Unsupported runtime: $RuntimeName"
 }
 
+function Install-ClaudeSkills {
+  param(
+    [Parameter(Mandatory = $true)][string]$ToolkitRoot,
+    [Parameter(Mandatory = $true)][string]$ProjectRoot,
+    [Parameter(Mandatory = $true)][bool]$Overwrite
+  )
+
+  $skillsSource = Join-Path $ToolkitRoot 'skills-claude'
+  $skillsDest = Join-Path $ProjectRoot '.claude/skills'
+
+  if (-not (Test-Path -LiteralPath $skillsSource)) {
+    throw "Claude skills source not found: $skillsSource"
+  }
+
+  $skillCount = 0
+  foreach ($skillDir in (Get-ChildItem -Path $skillsSource -Directory)) {
+    $srcFile = Join-Path $skillDir.FullName 'SKILL.md'
+    if (-not (Test-Path -LiteralPath $srcFile)) { continue }
+
+    $destFile = Join-Path $skillsDest "$($skillDir.Name)/SKILL.md"
+    Copy-File -SourcePath $srcFile -DestinationPath $destFile -Overwrite $Overwrite
+    $skillCount++
+  }
+
+  # Install reference files
+  $refDest = Join-Path $skillsDest 'references'
+  if (-not (Test-Path -LiteralPath $refDest)) {
+    New-Item -ItemType Directory -Force -Path $refDest | Out-Null
+  }
+
+  $refCount = 0
+  $missingRefs = @()
+
+  # 6 files from toolkit/templates/docs/
+  $templateRefs = @(
+    @{ Src = 'templates/docs/api/YAML_CREATION_RULES.md' },
+    @{ Src = 'templates/docs/api/API_DESIGN_FLOWCHART_CREATION_RULES.md' },
+    @{ Src = 'templates/docs/api/FLOWCHART_CREATION_RULES.md' },
+    @{ Src = 'templates/docs/api/API_DESIGN_CREATION_RULES.md' },
+    @{ Src = 'templates/docs/specs/FLOW_ACTION_SPEC_CREATION_RULES.md' },
+    @{ Src = 'templates/docs/qa/TEST_CASE_CREATION_RULES.md' }
+  )
+
+  foreach ($ref in $templateRefs) {
+    $srcPath = Join-Path $ToolkitRoot $ref.Src
+    $fileName = Split-Path -Leaf $srcPath
+    $destPath = Join-Path $refDest $fileName
+    if (Test-Path -LiteralPath $srcPath) {
+      Copy-File -SourcePath $srcPath -DestinationPath $destPath -Overwrite $Overwrite
+      $refCount++
+    } else {
+      $missingRefs += $srcPath
+    }
+  }
+
+  # 3 files from toolkit/skills/sdtk-screen-design-spec/references/
+  $screenRefs = @('numbering-rules.md', 'figma-mcp.md', 'excel-image-export.md')
+  foreach ($fileName in $screenRefs) {
+    $srcPath = Join-Path $ToolkitRoot "skills/sdtk-screen-design-spec/references/$fileName"
+    $destPath = Join-Path $refDest $fileName
+    if (Test-Path -LiteralPath $srcPath) {
+      Copy-File -SourcePath $srcPath -DestinationPath $destPath -Overwrite $Overwrite
+      $refCount++
+    } else {
+      $missingRefs += $srcPath
+    }
+  }
+
+  # Fail-fast: abort if any reference files are missing
+  if ($missingRefs.Count -gt 0) {
+    $list = ($missingRefs | ForEach-Object { "  - $_" }) -join "`n"
+    throw "Claude install failed. Missing reference files:`n$list"
+  }
+
+  # Strict count assertions
+  $expectedSkills = 13
+  $expectedRefs = 9
+  if ($skillCount -ne $expectedSkills) {
+    throw "Claude install failed. Expected $expectedSkills skills but installed $skillCount."
+  }
+  if ($refCount -ne $expectedRefs) {
+    throw "Claude install failed. Expected $expectedRefs reference files but installed $refCount."
+  }
+
+  Write-Host "  Skills installed: $skillCount"
+  Write-Host "  Reference files : $refCount"
+}
+
 $toolkitRoot = Resolve-Path $PSScriptRoot
 $canonicalRulesPath = Join-Path $toolkitRoot 'templates/docs/api/FLOWCHART_CREATION_RULES.md'
 $canonicalRulesHash = Get-FileSha256 -Path $canonicalRulesPath
@@ -136,8 +224,10 @@ if (($Runtime -eq 'codex') -and (-not $SkipSkills)) {
     & $skillInstaller | Out-Host
   }
 }
-elseif (($Runtime -eq 'claude') -and (-not $SkipSkills) -and (-not $Quiet)) {
-  Write-Warning "Runtime 'claude' does not install Codex skills. Skipping skill installation."
+elseif (($Runtime -eq 'claude') -and (-not $SkipSkills)) {
+  Write-Host ""
+  Write-Host "Installing Claude Code skills..."
+  Install-ClaudeSkills -ToolkitRoot $toolkitRoot -ProjectRoot $projectRoot -Overwrite ([bool]$Force)
 }
 
 if (-not $Quiet) {
@@ -148,7 +238,8 @@ if (-not $Quiet) {
   if ($Runtime -eq 'codex') {
     Write-Host "2) Restart Codex (to load runtime adapter and skills)"
   } else {
-    Write-Host "2) Restart Claude Code (to load CLAUDE.md adapter)"
+    Write-Host "2) Restart Claude Code (to load CLAUDE.md + skills)"
+    Write-Host "   Commands: /orchestrator /pm /ba /arch /dev /qa"
   }
   Write-Host '3) Generate feature docs:'
   Write-Host '   sdtk generate --feature-key YOUR_FEATURE --feature-name "Your Feature"'

package/assets/toolkit/toolkit/runtimes/claude/CLAUDE_TEMPLATE.md

@@ -1,7 +1,7 @@
 # CLAUDE.md
 
-Version: 1.0
-Last Updated: 2026-02-25
+Version: 2.0
+Last Updated: 2026-03-05
 Owner: SDTK Core Team
 
 This file defines runtime guidance for Claude Code sessions in projects using SDTK.
@@ -9,24 +9,46 @@ This file defines runtime guidance for Claude Code sessions in projects using SD
 ## 1) Rule Priority
 1. Explicit user request
 2. `AGENTS.md` (project root)
-3. `toolkit/AGENTS.md`
+3. Installed skill content (`.claude/skills/*/SKILL.md`)
 4. This file (`CLAUDE.md`)
-5. Other supporting docs
+5. `sdtk.config.json`
 
 ## 2) Runtime Model
 - Primary workflow: PM -> BA -> ARCH -> DEV -> QA
-- Role tags: `/pm`, `/ba`, `/arch`, `/dev`, `/qa`
+- Entry point: `/orchestrator` (recommended) or `/pm`
+- Role commands: `/pm`, `/ba`, `/arch`, `/dev`, `/qa`
+- Sub-skill commands: `/api-doc`, `/api-design-spec`, `/screen-design-spec`, `/design-layout`, `/test-case-spec`, `/dev-backend`, `/dev-frontend`
 - Shared state files:
   - `SHARED_PLANNING.md`
   - `QUALITY_CHECKLIST.md`
 
 ## 3) Minimal Session Flow
-1. Start with `/pm` to define feature scope.
+1. Start with `/orchestrator` or `/pm` to define feature scope.
 2. Move phase-by-phase without skipping gates.
 3. Keep traceability from requirements to design, implementation, and tests.
 4. Require code review completion before QA release decision.
 
-## 4) References
-- `toolkit/SDTK_TOOLKIT.md`
-- `toolkit/AGENTS.md`
-- `sdtk.config.json`
+## 4) Installed Skills
+Skills are installed at `.claude/skills/` and provide slash commands:
+
+| Command | Purpose |
+|---------|---------|
+| `/orchestrator` | Full 6-phase SDLC orchestration |
+| `/pm` | PM initiation + planning |
+| `/ba` | Business analysis |
+| `/arch` | Solution architecture |
+| `/dev` | Development + code review |
+| `/qa` | QA testing + release decision |
+| `/api-doc` | OpenAPI YAML + flow diagrams |
+| `/api-design-spec` | API design detail spec |
+| `/screen-design-spec` | Screen flow-action spec |
+| `/design-layout` | UI screen layout wireframes |
+| `/test-case-spec` | QA test-case spec |
+| `/dev-backend` | Backend code conventions |
+| `/dev-frontend` | Frontend code conventions |
+
+Rule reference files are installed at `.claude/skills/references/`.
+
+## 5) References
+- `sdtk.config.json`
+- `.claude/skills/references/` (rule files)

package/assets/toolkit/toolkit/skills-claude/api-design-spec/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: api-design-spec
+description: Generate detailed API design markdown from OpenAPI YAML and API flow list using Excel-style structure rules. Use when you need field-level request/response tables + per-endpoint process flow images for implementation/review handoff.
+---
+
+## Required Inputs (read before proceeding)
+Read the following artifacts for the current feature:
+1. `docs/api/[FeaturePascal]_API.yaml` — API contract
+2. `docs/api/[feature_snake]_api_flow_list.txt` — flow list
+
+## Input
+$ARGUMENTS
+
+# SDTK API Design Detail Spec
+
+## Outputs
+- `docs/api/[FEATURE_KEY]_API_DESIGN_DETAIL.md`
+- Supporting generated assets:
+  - `docs/api/flows/*.puml`
+  - `docs/api/images/*.svg`
+
+## Required Inputs
+- Feature key (`FEATURE_KEY`)
+- API contract YAML:
+  - Preferred: `docs/api/[FeaturePascal]_API.yaml`
+  - Fallback: a specified YAML file path
+- API flow list:
+  - Preferred: `docs/api/[feature_snake]_api_flow_list.txt`
+  - Fallback: a specified flow list path
+
+## Core Rules
+- Apply `.claude/skills/references/API_DESIGN_FLOWCHART_CREATION_RULES.md` first.
+- Keep endpoint contracts consistent with source YAML.
+- Keep process flow source synchronized with flow list (`*_api_flow_list.txt`).
+- Keep one visible flowchart per API section (embed image), avoid duplicate preview rendering.
+- Keep `Process Flow` sections implementation-readable:
+  - include YAML-derived flow summary / notes / login bullets
+  - keep error sections aligned with actual flow exits, not `None`
+
+## Generation Procedure
+1. Resolve input files (`yaml`, `flow_list`, `output`).
+2. Parse YAML endpoints (method, path, request schema, success/error schema).
+3. Parse flow blocks from flow list (`@startuml ... @enduml`) and map by `METHOD + path`.
+4. Generate detailed markdown sections per API:
+   - Flow summary / notes / login bullets from YAML `description`
+   - Process flow source block (`text` fenced block)
+   - Embedded flowchart image
+   - Path parameter table
+   - Request table (hierarchy levels + type + format + required)
+   - Success response table
+   - Error response table (explicit schema if defined, otherwise shared envelope + inferred business statuses from flow)
+5. Generate/update `.puml` per API under `docs/api/flows`.
+6. Render `.svg` images under `docs/api/images`.
+7. Validate:
+   - every API section has one embedded image
+   - every embed path exists
+   - no render error image output
+   - markdown tables keep `No` sequential numbering
+
+## Script
+- `scripts/generate_api_design_detail.py`
+
+### Typical command
+```bash
+python scripts/generate_api_design_detail.py \
+  --feature-key SCHEDULE_WHITEBOARD \
+  --yaml "docs/api/ScheduleWhiteboard_API.yaml" \
+  --flow-list "docs/api/schedule_whiteboard_api_flow_list.txt" \
+  --output "docs/api/SCHEDULE_WHITEBOARD_API_DESIGN_DETAIL.md"
+```
+
+## Orchestrator Integration (Hybrid)
+- `apiDesignDetailMode` in `sdtk.config.json` controls orchestration behavior:
+  - `auto` (default): generate API design detail when ARCH has API scope and YAML/flow sources are available.
+  - `on`: always generate API design detail for API scope (fail if required sources are missing).
+  - `off`: skip unless user explicitly requests.

package/assets/toolkit/toolkit/skills-claude/api-doc/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: api-doc
+description: Generate OpenAPI 3.x YAML and PlantUML flow diagrams for a feature following this toolkit's API conventions. Use when you need to create/update docs/api/* (API spec + flow list) from BA_SPEC/ARCH_DESIGN.
+---
+
+## Required Inputs (read before proceeding)
+Read the following artifacts for the current feature:
+1. `docs/specs/BA_SPEC_*.md` — business rules, use cases
+2. `docs/architecture/ARCH_DESIGN_*.md` — system components, data model
+
+## Input
+$ARGUMENTS
+
+# SDTK API Documentation
+
+## Outputs
+- `docs/api/[FeaturePascal]_API.yaml`
+- `docs/api/[FEATURE_KEY]_ENDPOINTS.md`
+- `docs/api/[feature_snake]_api_flow_list.txt`
+- Optional downstream (via `/api-design-spec`):
+  - `docs/api/[FEATURE_KEY]_API_DESIGN_DETAIL.md`
+
+## Inputs (minimum)
+- Feature name/key
+- Entities + key fields
+- Use cases (UC-xx) + business rules (BR-xx)
+- Auth/permission model
+
+## Process
+1. Read `docs/specs/BA_SPEC_[FEATURE_KEY].md` and/or `docs/architecture/ARCH_DESIGN_[FEATURE_KEY].md`.
+2. Read and apply split API rule sources:
+   - `.claude/skills/references/YAML_CREATION_RULES.md` for YAML contract rules
+   - `.claude/skills/references/API_DESIGN_FLOWCHART_CREATION_RULES.md` for flow list / flowchart rules
+3. Define endpoints mapped to UC-xx; keep path naming consistent across CRUD/search/list/mst patterns.
+4. For each endpoint, document request/response schema and error cases.
+5. Generate/update endpoint markdown (`[FEATURE_KEY]_ENDPOINTS.md`) with summary tables, API type grouping, and screen-logic mapping.
+6. Generate PlantUML flows including: auth, permission check, validation, main logic, error exits.
+7. Ensure traceability notes reference UC/BR where relevant.
+8. Validate English output hygiene when generating English artifacts:
+   - no mixed-language leftovers in narrative text
+   - no mojibake/encoding corruption markers
+   - terminology consistency across endpoint detail, summary tables, and flow labels
+9. If orchestrator mode requires API design detail generation (`apiDesignDetailMode=auto/on`), handoff to `/api-design-spec` after YAML + flow list are updated.
+
+## Reference
+- Deeper analysis: `docs/specs/API_DOC_SKILL_ANALYSIS.md` (if present).

package/assets/toolkit/toolkit/skills-claude/arch/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: arch
+description: Solution Architect workflow for SDTK. Use when you need to convert BA_SPEC + PM backlog into technical architecture, API contracts (OpenAPI), and UI layout docs; update SHARED_PLANNING.md / QUALITY_CHECKLIST.md and handoff to DEV.
+---
+
+## SDTK Pipeline Rules (always apply)
+1. Pipeline: PM Initiation → BA Analysis → PM Planning → Architecture Design → Development + Review → QA Validation
+2. After completing phase work: update SHARED_PLANNING.md + QUALITY_CHECKLIST.md
+3. If unclear: log OQ-xx in artifact, escalate to PM (PM asks user if needed)
+4. Traceability: REQ → BR/UC/AC → design → backlog → code/tests → QA
+5. Code review must be COMPLETE before QA phase can start
+6. Do not skip phases. If inputs missing, ask focused questions.
+
+## Prerequisites (verify before proceeding)
+Read QUALITY_CHECKLIST.md and verify:
+- Phase 2 BA Analysis gate must show all items [x] Done.
+- Phase 2+ PM Planning gate must show all items [x] Done.
+
+If prerequisites NOT met: report which gate is missing, suggest user run the prerequisite phase first.
+
+## Current Context
+- Config: !`node -e "try{process.stdout.write(require('fs').readFileSync('sdtk.config.json','utf8'))}catch{process.stdout.write('{}')}"`
+- Pipeline: !`node -e "try{process.stdout.write(require('fs').readFileSync('SHARED_PLANNING.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- Gates: !`node -e "try{process.stdout.write(require('fs').readFileSync('QUALITY_CHECKLIST.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- State: !`node -e "try{process.stdout.write(require('fs').readFileSync('.sdtk/orchestration-state.json','utf8'))}catch{process.stdout.write('{}')}"`
+
+## Input
+$ARGUMENTS
+
+If no arguments provided, read current feature context from SHARED_PLANNING.md.
+
+# SDTK ARCH (Solution Architecture)
+
+## Outputs
+- `docs/architecture/ARCH_DESIGN_[FEATURE_KEY].md`
+- If applicable:
+  - `docs/api/[FeaturePascal]_API.yaml`
+  - `docs/api/[FEATURE_KEY]_ENDPOINTS.md`
+  - `docs/api/[FEATURE_KEY]_API_DESIGN_DETAIL.md`
+  - `docs/api/[feature_snake]_api_flow_list.txt`
+  - `docs/database/DATABASE_SPEC_[FEATURE_KEY].md`
+  - `docs/design/DESIGN_LAYOUT_[FEATURE_KEY].md`
+  - `docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md`
+
+## Process
+1. Read BA spec + PRD/backlog.
+2. Read `sdtk.config.json` for project stack assumptions (backend/frontend/db/auth).
+3. If architecture output includes API contracts/flows, read and apply the split API rule sources before defining endpoints/flows:
+   - `.claude/skills/references/YAML_CREATION_RULES.md`
+   - `.claude/skills/references/API_DESIGN_FLOWCHART_CREATION_RULES.md`
+4. If architecture output includes screen flow-action specs, read and apply rules from `.claude/skills/references/FLOW_ACTION_SPEC_CREATION_RULES.md` (global numbering policy).
+5. If API detail spec is required, use skill `/api-design-spec` to build/update `docs/api/[FEATURE_KEY]_API_DESIGN_DETAIL.md` using YAML + flow list.
+6. For complex UI flow-action specs, use skill `/screen-design-spec` to build/update `docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md`.
+7. Define:
+   - System components + data model
+   - API endpoints and flows (if backend changes)
+   - Screen layouts (if UI changes)
+   - Security/authz decisions
+8. Create/update:
+   - OpenAPI YAML + API endpoint markdown
+   - API flow list
+   - API design detail spec (when `orchestration.apiDesignDetailMode` is `auto/on`)
+   - Database spec (if DB impact exists)
+   - Flow-action spec and design layout (if UI impact exists)
+9. Ensure mapping UC/BR -> DB/API/screens and run output hygiene checks:
+   - EN artifacts use English narrative text (except clearly marked original-language appendix blocks).
+   - No mojibake/encoding corruption in markdown/yaml/txt outputs.
+10. If anything is unclear: record OQ-xx in ARCH_DESIGN "Open Questions" and escalate to PM (suggest user run `/pm` for a decision if still missing info).
+11. Update shared state + Phase 3 checklist.
+12. Handoff: suggest user run `/dev` to implement the design.

package/assets/toolkit/toolkit/skills-claude/ba/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: ba
+description: Business Analyst workflow for SDTK. Use when you need to turn PM initiation into BA_SPEC with glossary, business rules (BR-xx), use cases (UC-xx), acceptance criteria (AC-xx), NFRs, risks, open questions, and a traceability matrix.
+---
+
+## SDTK Pipeline Rules (always apply)
+1. Pipeline: PM Initiation → BA Analysis → PM Planning → Architecture Design → Development + Review → QA Validation
+2. After completing phase work: update SHARED_PLANNING.md + QUALITY_CHECKLIST.md
+3. If unclear: log OQ-xx in artifact, escalate to PM (PM asks user if needed)
+4. Traceability: REQ → BR/UC/AC → design → backlog → code/tests → QA
+5. Code review must be COMPLETE before QA phase can start
+6. Do not skip phases. If inputs missing, ask focused questions.
+
+## Prerequisites (verify before proceeding)
+Read QUALITY_CHECKLIST.md and verify:
+- Phase 1 PM Init gate must show all items [x] Done.
+
+If prerequisites NOT met: report which gate is missing, suggest user run `/pm` first.
+
+## Current Context
+- Config: !`node -e "try{process.stdout.write(require('fs').readFileSync('sdtk.config.json','utf8'))}catch{process.stdout.write('{}')}"`
+- Pipeline: !`node -e "try{process.stdout.write(require('fs').readFileSync('SHARED_PLANNING.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- Gates: !`node -e "try{process.stdout.write(require('fs').readFileSync('QUALITY_CHECKLIST.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- State: !`node -e "try{process.stdout.write(require('fs').readFileSync('.sdtk/orchestration-state.json','utf8'))}catch{process.stdout.write('{}')}"`
+
+## Input
+$ARGUMENTS
+
+If no arguments provided, read current feature context from SHARED_PLANNING.md.
+
+# SDTK BA (Business Analysis)
+
+## Output
+- `docs/specs/BA_SPEC_[FEATURE_KEY].md`
+
+## Process
+1. Read `docs/product/PROJECT_INITIATION_[FEATURE_KEY].md` (and any source requirements).
+2. Produce:
+   - Glossary
+   - BR-xx (numbered)
+   - UC-xx (cover 100% REQ-xx)
+   - AC-xx (mapped to UC/BR)
+   - NFR-xx
+   - Risks + Open Questions
+   - Traceability summary table (REQ → UC/BR/AC)
+3. If source requirements are VI/JP: preserve the original text and add a literal EN translation in appendices.
+4. If anything is unclear: record OQ-xx in BA_SPEC "Open Questions" and escalate to PM (suggest user run `/pm` for a decision if still missing info).
+5. Update `SHARED_PLANNING.md` + `QUALITY_CHECKLIST.md` Phase 2.
+6. Handoff: suggest user run `/pm` to proceed with PRD planning.

package/assets/toolkit/toolkit/skills-claude/design-layout/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: design-layout
+description: Generate UI screen layout documentation for a feature, including PlantUML @startsalt wireframes and item tables. Use when a feature includes frontend/admin screens and you need docs/design/* deliverables.
+---
+
+## Required Inputs (read before proceeding)
+Read the following artifacts for the current feature:
+1. `docs/specs/BA_SPEC_*.md` — screens + fields
+2. `docs/api/[FEATURE_KEY]_ENDPOINTS.md` — API list
+
+## Input
+$ARGUMENTS
+
+# SDTK Screen Layout Design
+
+## Output
+- `docs/design/DESIGN_LAYOUT_[FEATURE_KEY].md`
+
+## Process
+1. Read BA spec (screens + fields) and API list.
+2. For each screen, include:
+   - PlantUML `@startsalt` wireframe first
+   - API list table
+   - Item table with numbering that matches the wireframe
+3. Keep screen IDs consistent (A-*, B-*, C-*).

package/assets/toolkit/toolkit/skills-claude/dev/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: dev
+description: Developer workflow for SDTK. Use when you need to implement a feature from ARCH_DESIGN + BACKLOG: create an implementation plan, write code + tests, complete mandatory code review gate, and prepare a QA handoff.
+---
+
+## SDTK Pipeline Rules (always apply)
+1. Pipeline: PM Initiation → BA Analysis → PM Planning → Architecture Design → Development + Review → QA Validation
+2. After completing phase work: update SHARED_PLANNING.md + QUALITY_CHECKLIST.md
+3. If unclear: log OQ-xx in artifact, escalate to PM (PM asks user if needed)
+4. Traceability: REQ → BR/UC/AC → design → backlog → code/tests → QA
+5. Code review must be COMPLETE before QA phase can start
+6. Do not skip phases. If inputs missing, ask focused questions.
+
+## Prerequisites (verify before proceeding)
+Read QUALITY_CHECKLIST.md and verify:
+- Phase 3 ARCH Design gate must show all items [x] Done.
+
+If prerequisites NOT met: report which gate is missing, suggest user run `/arch` first.
+
+## Current Context
+- Config: !`node -e "try{process.stdout.write(require('fs').readFileSync('sdtk.config.json','utf8'))}catch{process.stdout.write('{}')}"`
+- Pipeline: !`node -e "try{process.stdout.write(require('fs').readFileSync('SHARED_PLANNING.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- Gates: !`node -e "try{process.stdout.write(require('fs').readFileSync('QUALITY_CHECKLIST.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- State: !`node -e "try{process.stdout.write(require('fs').readFileSync('.sdtk/orchestration-state.json','utf8'))}catch{process.stdout.write('{}')}"`
+
+## Input
+$ARGUMENTS
+
+If no arguments provided, read current feature context from SHARED_PLANNING.md.
+
+# SDTK DEV (Implementation + Code Review)
+
+## Outputs
+- `docs/dev/FEATURE_IMPL_PLAN_[FEATURE_KEY].md`
+- Code + tests (follow repo conventions)
+
+## Process
+1. Read `ARCH_DESIGN_*` + backlog.
+2. Read `sdtk.config.json` for project stack + test/lint commands.
+3. Write `FEATURE_IMPL_PLAN_*` (scope, file list, test plan).
+4. If anything is unclear: record OQ-xx in FEATURE_IMPL_PLAN "Open Questions" and escalate to PM (suggest user run `/pm` for a decision if still missing info).
+5. Implement incrementally with tests.
+6. Complete mandatory code review gate (self + peer checklist; AI peer review allowed).
+7. Update `SHARED_PLANNING.md` + `QUALITY_CHECKLIST.md` Phase 4.
+8. Handoff: suggest user run `/qa` to test (only after code review PASS).

package/assets/toolkit/toolkit/skills-claude/dev-backend/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: dev-backend
+description: Generate/modify Python Django REST Framework backend code following the toolkit conventions (models/views/services/serializers/validation/urls/enums). Use when implementing backend features in that project style.
+---
+
+## Input
+$ARGUMENTS
+
+# SDTK Backend (Toolkit conventions)
+
+## Process
+1. Check whether this repository already has a backend reference module and follow its patterns.
+2. Follow module structure: `src/backend/<module>/{models,view,service,serializers,validation,enum,urls.py}`.
+3. Apply conventions:
+   - Soft delete via `del_flg`
+   - Audit fields (creator/updater/del timestamps)
+   - Permission checks before operations
+   - `transaction.atomic()` for writes
+   - Logging decorator on public endpoints
+4. Add tests for critical business rules and state transitions.

package/assets/toolkit/toolkit/skills-claude/dev-frontend/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: dev-frontend
+description: Generate/modify React frontend code following the toolkit conventions (list/register/edit/detail pages, components, services, React Query hooks, permission checks). Use when implementing frontend features in that project style.
+---
+
+## Input
+$ARGUMENTS
+
+# SDTK Frontend (Toolkit conventions)
+
+## Process
+1. Check whether this repository already has a frontend reference module and follow its patterns.
+2. Follow structure:
+   - `src/frontend/features/{feature}/...`
+   - `src/frontend/services/{feature}/{feature}Service.js`
+   - `src/frontend/services/apiHook/{feature}.js`
+3. Implement screens based on `docs/design/DESIGN_LAYOUT_[FEATURE_KEY].md`.
+4. Preserve patterns: React Query hooks, loading states, permission checks, consistent labels.

package/assets/toolkit/toolkit/skills-claude/orchestrator/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: orchestrator
+description: Orchestrate a full 6-phase SDLC multi-agent workflow (PM/BA/ARCH/DEV/QA) using this repo's conventions: SHARED_PLANNING.md + QUALITY_CHECKLIST.md + docs/* artifacts + phase handoffs.
+---
+
+## SDTK Pipeline Rules (always apply)
+1. Pipeline: PM Initiation → BA Analysis → PM Planning → Architecture Design → Development + Review → QA Validation
+2. After completing phase work: update SHARED_PLANNING.md + QUALITY_CHECKLIST.md
+3. If unclear: log OQ-xx in artifact, escalate to PM (PM asks user if needed)
+4. Traceability: REQ → BR/UC/AC → design → backlog → code/tests → QA
+5. Code review must be COMPLETE before QA phase can start
+6. Do not skip phases. If inputs missing, ask focused questions.
+
+## Current Context
+- Config: !`node -e "try{process.stdout.write(require('fs').readFileSync('sdtk.config.json','utf8'))}catch{process.stdout.write('{}')}"`
+- Pipeline: !`node -e "try{process.stdout.write(require('fs').readFileSync('SHARED_PLANNING.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- Gates: !`node -e "try{process.stdout.write(require('fs').readFileSync('QUALITY_CHECKLIST.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- State: !`node -e "try{process.stdout.write(require('fs').readFileSync('.sdtk/orchestration-state.json','utf8'))}catch{process.stdout.write('{}')}"`
+
+## Input
+$ARGUMENTS
+
+If no arguments provided, read current feature context from SHARED_PLANNING.md.
+
+# SDTK Orchestrator (multi-agent workflow)
+
+## Initialize
+- Ensure feature key + feature name exist (ask if missing).
+- Read `sdtk.config.json` (project stack + commands) if present.
+- Run `sdtk generate --feature-key <KEY> --feature-name "<NAME>"` to create skeleton artifacts.
+
+## Execute pipeline (one phase per turn)
+- Default role: PM (entry point) if user did not specify.
+- Respect role tags: `/pm`, `/ba`, `/arch`, `/dev`, `/qa`.
+- For each phase:
+  - Create/update the phase artifact(s) in `docs/`.
+  - If phase is ARCH and API contract/flow is in scope, invoke `/api-doc` to produce/update `docs/api/[FeaturePascal]_API.yaml`, `docs/api/[FEATURE_KEY]_ENDPOINTS.md`, and `docs/api/[feature_snake]_api_flow_list.txt`.
+  - If phase is ARCH and API detail spec is in scope, invoke `/api-design-spec` to produce/update `docs/api/[FEATURE_KEY]_API_DESIGN_DETAIL.md`.
+  - If phase is ARCH and UI flow behavior is in scope, invoke `/screen-design-spec` to produce/update `docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md`.
+  - If phase is QA and test-case specification is in scope, invoke `/test-case-spec` to produce/update `docs/qa/[FEATURE_KEY]_TEST_CASE.md`.
+  - Update `SHARED_PLANNING.md` (phase row + activity log).
+  - Update `QUALITY_CHECKLIST.md` (mark items PASS/Pending).
+  - Produce one clear handoff message to the next role.
+
+## API design detail mode (Hybrid)
+- Read `sdtk.config.json` key: `orchestration.apiDesignDetailMode`.
+- Supported values:
+  - `auto` (default): run `/api-design-spec` when ARCH has API scope and YAML + flow list are available.
+  - `on`: always run `/api-design-spec` for API scope (fail fast if required inputs are missing).
+  - `off`: skip API design detail generation unless user explicitly requests it.
+
+## Test-case spec mode (Hybrid)
+- Read `sdtk.config.json` key: `orchestration.testCaseSpecMode`.
+- Supported values:
+  - `auto` (default): run `/test-case-spec` when QA phase requires reusable test-case artifact.
+  - `on`: always run `/test-case-spec` for QA phase (fail fast if required inputs are missing).
+  - `off`: skip test-case spec generation unless user explicitly requests it.
+
+## Guardrails
+- Do not skip phases; if prerequisites are missing, ask focused questions.
+- Keep traceability: REQ -> BR/UC/AC -> design -> backlog -> code/tests -> QA report.
+- Require code review completion before QA handoff.
+- If input requirements are VI/JP: preserve original text + add EN translation in appendix for traceability (at least in Project Initiation and BA spec).

package/assets/toolkit/toolkit/skills-claude/pm/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: pm
+description: Product Manager + meta-orchestrator workflow for SDTK. Use when you need to start a new feature (Phase 1) or produce PM planning artifacts (PRD + BACKLOG) and update SHARED_PLANNING.md / QUALITY_CHECKLIST.md with correct phase handoffs.
+---
+
+## SDTK Pipeline Rules (always apply)
+1. Pipeline: PM Initiation → BA Analysis → PM Planning → Architecture Design → Development + Review → QA Validation
+2. After completing phase work: update SHARED_PLANNING.md + QUALITY_CHECKLIST.md
+3. If unclear: log OQ-xx in artifact, escalate to PM (PM asks user if needed)
+4. Traceability: REQ → BR/UC/AC → design → backlog → code/tests → QA
+5. Code review must be COMPLETE before QA phase can start
+6. Do not skip phases. If inputs missing, ask focused questions.
+
+## Prerequisites (verify before proceeding)
+Read QUALITY_CHECKLIST.md and verify:
+- Phase 1 (PM Init): No prerequisites required.
+- Phase 2+ (PM Planning): BA Analysis gate must show all items [x] Done.
+
+If prerequisites NOT met: report which gate is missing, suggest user run the prerequisite phase first.
+
+## Current Context
+- Config: !`node -e "try{process.stdout.write(require('fs').readFileSync('sdtk.config.json','utf8'))}catch{process.stdout.write('{}')}"`
+- Pipeline: !`node -e "try{process.stdout.write(require('fs').readFileSync('SHARED_PLANNING.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- Gates: !`node -e "try{process.stdout.write(require('fs').readFileSync('QUALITY_CHECKLIST.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- State: !`node -e "try{process.stdout.write(require('fs').readFileSync('.sdtk/orchestration-state.json','utf8'))}catch{process.stdout.write('{}')}"`
+
+## Input
+$ARGUMENTS
+
+If no arguments provided, read current feature context from SHARED_PLANNING.md.
+
+# SDTK PM (Entry Point + Planning)
+
+## Outputs
+- Phase 1: `docs/product/PROJECT_INITIATION_[FEATURE_KEY].md`
+- Phase 2+ (after BA spec): `docs/product/PRD_[FEATURE_KEY].md` + `docs/product/BACKLOG_[FEATURE_KEY].md`
+
+## Process
+1. Confirm `FEATURE_KEY` + `FEATURE_NAME` + Phase-1 scope in/out.
+2. Create/update PM artifact(s).
+3. Ensure REQ-xx list is clear and testable.
+4. If requirements are provided in VI/JP: keep the original text in an appendix and add an EN translation (literal) for traceability.
+5. Update `SHARED_PLANNING.md` + `QUALITY_CHECKLIST.md`.
+6. Handoff:
+   - After Project Initiation -> suggest user run `/ba` to analyze requirements
+   - After PRD/Backlog -> suggest user run `/arch` to design architecture
+
+## Clarification And Decisions (PM responsibility)
+- Collect OQ-xx items raised by BA/ARCH/DEV/QA in their respective artifacts.
+- Try to resolve OQ-xx using existing docs and reasonable product/tech decisions.
+- If still missing information from the original input: ask the user (final stakeholder) and record the answer as the resolution.
+- Record decisions in PRD `Decision Log` and update OQ-xx `Resolution` fields in the originating docs.

package/assets/toolkit/toolkit/skills-claude/qa/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: qa
+description: QA workflow for SDTK. Use when you need to validate an implemented feature against BA/PRD/Backlog, run quality gates, document defects, and produce a QA_RELEASE_REPORT with a release decision.
+---
+
+## SDTK Pipeline Rules (always apply)
+1. Pipeline: PM Initiation → BA Analysis → PM Planning → Architecture Design → Development + Review → QA Validation
+2. After completing phase work: update SHARED_PLANNING.md + QUALITY_CHECKLIST.md
+3. If unclear: log OQ-xx in artifact, escalate to PM (PM asks user if needed)
+4. Traceability: REQ → BR/UC/AC → design → backlog → code/tests → QA
+5. Code review must be COMPLETE before QA phase can start
+6. Do not skip phases. If inputs missing, ask focused questions.
+
+## Prerequisites (verify before proceeding)
+Read QUALITY_CHECKLIST.md and verify:
+- Phase 4 DEV gate must show all items [x] Done (including code review completion).
+
+If prerequisites NOT met: report which gate is missing, suggest user run `/dev` first to complete code review.
+
+## Current Context
+- Config: !`node -e "try{process.stdout.write(require('fs').readFileSync('sdtk.config.json','utf8'))}catch{process.stdout.write('{}')}"`
+- Pipeline: !`node -e "try{process.stdout.write(require('fs').readFileSync('SHARED_PLANNING.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- Gates: !`node -e "try{process.stdout.write(require('fs').readFileSync('QUALITY_CHECKLIST.md','utf8'))}catch{process.stdout.write('Not initialized')}"`
+- State: !`node -e "try{process.stdout.write(require('fs').readFileSync('.sdtk/orchestration-state.json','utf8'))}catch{process.stdout.write('{}')}"`
+
+## Input
+$ARGUMENTS
+
+If no arguments provided, read current feature context from SHARED_PLANNING.md.
+
+# SDTK QA (Testing + Release Decision)
+
+## Output
+- `docs/qa/QA_RELEASE_REPORT_[FEATURE_KEY].md`
+- Optional (when detailed test design spec is requested):
+  - `docs/qa/[FEATURE_KEY]_TEST_CASE.md` via `/test-case-spec`
+
+## Process
+1. Validate prerequisites: DEV phase completed + code review PASS.
+2. Create test strategy mapped to UC/AC.
+3. If test-case specification artifact is required, invoke `/test-case-spec` and align counts/coverage with release testing scope.
+4. If acceptance criteria / expected behavior is unclear: record OQ-xx in QA report and escalate to PM (suggest user run `/pm` if still missing info).
+5. Execute/record results (unit/integration/e2e as applicable).
+6. Record defects with severity and status.
+7. Decide: APPROVED vs REJECTED (with reasons).
+8. Update shared state + Phase 5 checklist.
+9. Handoff: suggest user run `/pm` to finalize release status if approved.

package/assets/toolkit/toolkit/skills-claude/screen-design-spec/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: screen-design-spec
+description: Create/update screen flow-action specifications from requirement sources (Excel/Figma/spec docs), including screen flow PlantUML, UI item/action tables, API mapping tables, and screen-to-API traceability.
+---
+
+## Required Inputs (read before proceeding)
+Read the following artifacts for the current feature:
+1. `docs/specs/BA_SPEC_*.md` — business rules, use cases
+2. `docs/architecture/ARCH_DESIGN_*.md` — system components
+3. `docs/api/[FEATURE_KEY]_ENDPOINTS.md` — API endpoints (when available)
+
+## Input
+$ARGUMENTS
+
+# SDTK Screen Flow Action Spec
+
+## Outputs
+- `docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md`
+- Optional supporting docs:
+  - `docs/specs/[FEATURE_KEY]_FIGMA_LAYOUT.md`
+  - `docs/specs/[FEATURE_KEY]_DESIGN_SPEC_FROM_EXCEL.md`
+  - `docs/specs/assets/[feature_snake]/screens/*`
+
+## Required Inputs
+- Feature key/name
+- Primary requirement sources (BA spec, architecture, customer design docs)
+- Screen source references (Figma URLs and/or requirement screenshots)
+- API endpoint source (`docs/api/[FEATURE_KEY]_ENDPOINTS.md`) when available
+
+## Process
+1. Read requirement sources and identify in-scope screens, dialogs, and transitions.
+2. Read and apply rules from `.claude/skills/references/FLOW_ACTION_SPEC_CREATION_RULES.md`.
+3. Build/update section `Feature overview` and `Screen flow action` (PlantUML).
+4. For each screen/dialog:
+   - Add metadata (screen ID, source link)
+   - Add screen image reference
+   - Add UI item/action table with `No` column
+   - Add API mapping table (trigger -> API -> data usage)
+5. Build/update `System processing flow` from use-case and process sources.
+6. Build/update `Open questions` for unresolved behavior/API/data points.
+7. Build/update `Screen - API Mapping` summary section.
+8. Validate:
+   - global numbering consistency (no screen-level reset)
+   - no broken image paths
+   - PlantUML renderability
+   - consistency with API endpoints spec
+   - EN artifact hygiene (no VI leftovers, no mojibake, no merged heading lines)
+   - for legacy specs with per-screen reset numbering: run renumber migration first
+9. Update document history and handoff to ARCH/DEV.
+
+## Rule References
+- Core rules: `.claude/skills/references/FLOW_ACTION_SPEC_CREATION_RULES.md`
+- Numbering reference: `.claude/skills/references/numbering-rules.md`
+- Figma reference: `.claude/skills/references/figma-mcp.md`
+- Excel image export reference: `.claude/skills/references/excel-image-export.md`
+
+## Validation Script
+- `scripts/validate_flow_action_spec_numbering.py`
+  - Checks duplicate/resetted numbering in action tables.
+  - Checks encoding/markdown hygiene.
+  - For EN artifacts, run with `--en-check`:
+    - `python scripts/validate_flow_action_spec_numbering.py --spec "docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md" --en-check`
+- `scripts/renumber_flow_action_spec_global.py`
+  - Auto-migrates action table `No` fields to global numbering.
+  - Dry-run:
+    - `python scripts/renumber_flow_action_spec_global.py --spec "docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md"`
+  - Apply:
+    - `python scripts/renumber_flow_action_spec_global.py --spec "docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md" --write`

package/assets/toolkit/toolkit/skills-claude/test-case-spec/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: test-case-spec
+description: Generate screen-based QA test-case markdown in Excel-aligned layout (Statistic + per-screen UTC/ITC worksheets). Use when QA needs reusable test design artifacts before or during execution.
+---
+
+## Required Inputs (read before proceeding)
+Read the following artifacts for the current feature:
+1. `docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md` — screen/flow references
+2. `docs/specs/BA_SPEC_[FEATURE_KEY].md` — business rules, use cases
+3. `docs/api/[FEATURE_KEY]_ENDPOINTS.md` — API reference
+4. `docs/specs/Q&A.md` or `docs/en/specs/Q&A.md` — clarification source (when available)
+
+## Input
+$ARGUMENTS
+
+# SDTK Test Case Spec
+
+## Outputs
+- `docs/qa/[FEATURE_KEY]_TEST_CASE.md`
+- Optional project variant:
+  - `docs/en/qa/[FEATURE_KEY]_TEST_CASE.md` (only when project uses `docs/en/**`)
+
+## Core Rules
+1. Apply `.claude/skills/references/TEST_CASE_CREATION_RULES.md` first.
+2. Keep section order fixed (Statistic -> Abbreviations -> Scope -> References -> Environment -> Coverage -> Screen-based UTC/ITC -> OQ -> STC/UAT note).
+3. Use screen-first layout to mirror worksheet structure:
+   - each screen can have `[SCREEN_KEY]_UTC` and `[SCREEN_KEY]_ITC`.
+4. Keep one unified 18-column schema for UTC/ITC rows.
+5. Keep stable case IDs; do not renumber only because of regrouping.
+6. Track unresolved decisions via `OQ-xx`.
+
+## Procedure
+1. Resolve output path:
+   - default `docs/qa/[FEATURE_KEY]_TEST_CASE.md`
+   - use `docs/en/qa/...` only if the repo already follows `docs/en/**`.
+2. Build/refresh `Statistic Summary (Excel-aligned)`:
+   - include UT total, IT total, grand total.
+3. Build `Feature Coverage Matrix` from flow/action and API docs.
+4. Split UTC/ITC by screen sections (`screen-first`), not by test type only.
+5. Fill conflict/permission/error-path cases from Q&A decisions and API contracts.
+6. Record unresolved items in section `Open Questions`.
+7. Validate:
+   - counts in summary match table rows
+   - no placeholder tokens like `??`
+   - out-of-scope boundaries are explicit
+
+## Role Integration
+- Primary owner: `/qa`.
+- `/qa` uses this skill to design/update reusable test-case specs.
+- `/qa` still owns release decision artifact (`QA_RELEASE_REPORT_*`).
+
+## Notes
+- This skill is for test-case specification artifacts, not test execution logs.
+- For release approval and defect triage, continue with `/qa`.
+
+## Validator Script
+- `scripts/validate_test_case_spec.py`
+
+### Typical command
+```bash
+python scripts/validate_test_case_spec.py \
+  --file "docs/qa/[FEATURE_KEY]_TEST_CASE.md"
+```

package/package.json

@@ -1,6 +1,6 @@
 {
     "name":  "sdtk-kit",
-    "version":  "0.3.2",
+    "version":  "0.3.3",
     "description":  "SDTK CLI toolkit for deterministic software documentation workflows",
     "bin":  {
                 "sdtk":  "./bin/sdtk.js"
@@ -36,7 +36,7 @@
                        "url":  "https://github.com/codexsdtk/sdtk-toolkit.git",
                        "directory":  "distribution/sdtk-cli"
                    },
-    "homepage":  "https://sdtk.dev",
+    "homepage":  "https://agenttoolkits.dev",
     "bugs":  {
                  "url":  "https://github.com/codexsdtk/sdtk-toolkit/issues"
              },

package/src/commands/help.js

@@ -16,7 +16,7 @@ function cmdHelp() {
     "  --runtime <codex|claude>   Runtime adapter (default: codex)",
     "  --project-path <path>      Target project directory (default: cwd)",
     "  --force                    Overwrite existing files",
-    "  --skip-skills              Skip Codex skill installation",
+    "  --skip-skills              Skip skill installation (Codex and Claude)",
     "  --verbose                  Show detailed PowerShell script output",
     "",
     "Auth options:",