create-yss-spec 1.1.3 → 2.0.0

package/template/.agents/skills/yss-cache/references/troubleshooting.md

@@ -0,0 +1,33 @@
+# 证据化排障
+
+## 缓存未命中
+
+1. 检查 starter/后端依赖和 `@EnableYssCloudCache`。
+2. 检查 `active-type` 与实际 Provider/CacheManager Bean。
+3. 确认调用经过 Spring 代理，不是同类自调用。
+4. 检查 SpEL 参数名、null、集合顺序和租户维度。
+5. 比较两次调用生成的 cache name/key，并检查 Redis 实际 key。
+6. 检查 `condition`、`unless`、TTL 和序列化异常。
+
+## 更新后仍读旧值
+
+1. 列出所有写、删、状态变更入口，确认每条路径都更新或清理相同 cache/key。
+2. 检查事务是否尚未提交；YSS 写/删/清理可能在 `afterCommit` 执行。
+3. 检查是否误用了 Caffeine、fallback 或 JetCache local cache。
+4. 检查 `allEntries`、`beforeInvocation` 和空 key 产生的 `SimpleKey.EMPTY`。
+
+## Redis 启动或连接失败
+
+1. 判定 Standalone/Sentinel/Cluster，检查拓扑互斥和 Cluster DB 0。
+2. 分别核对 Redis 数据节点与 Sentinel 认证。
+3. 检查 SSL、DNS、端口、connect/read timeout 和 Jedis pool。
+4. 检查用户自定义连接工厂是否使默认配置回退。
+
+## Redis 故障后行为异常
+
+1. 检查 fallback 是否明确开启、目标 Provider 是否存在且 available。
+2. 区分只读回退与脏写回退。
+3. 查看恢复时 Redis 清理失败日志；失败时框架应保持降级并重试。
+4. 多节点差异优先按 fallback 一致性窗口分析，不要误判为 Redis 广播失效。
+
+可先运行 `scripts/inspect-cache-usage.sh <project-root>` 取得静态证据，再进入源码路径。

package/template/.agents/skills/yss-cache/references/verification.md

@@ -0,0 +1,34 @@
+# 验证与完成标准
+
+## 组件
+
+```bash
+./mvnw -f yss-microservice-components/yss-component-cache-parent/pom.xml verify
+```
+
+跨模块测试使用父 reactor 的 `-pl <module> -am`，避免解析本地旧 SNAPSHOT。也可运行：
+
+```bash
+scripts/verify-cache-component.sh --source-root /path/to/yss-cloud-microservice
+```
+
+## 消费项目
+
+```bash
+./mvnw -pl <starter-module> -am -DskipTests package
+```
+
+完整启动依赖数据库、注册中心等外部服务时，构建验证与启动验证分开报告。
+
+## 验收矩阵
+
+- 首次调用执行业务，第二次相同 key 命中缓存。
+- 不同租户/业务 key 不串值。
+- 更新、删除、状态变更后旧值失效。
+- `condition`、`unless` 和异常返回行为符合预期。
+- 默认 TTL 和枚举覆盖 TTL 在后端物理存在。
+- Redis 停止后行为符合 fallback 配置；恢复后旧 Redis 值不会重新出现。
+- Sentinel/Cluster 创建正确连接工厂，Cluster 使用 DB 0。
+- Docker 可用时真实 Redis 认证、JSON template、JDK cache serialization 和 TTL 测试实际执行。
+- Java 8 组件 class major version 为 52。
+- `git diff --check` 通过，消费 starter 构建通过。

package/template/.agents/skills/yss-cache/scripts/check-skill-freshness.sh

@@ -0,0 +1,84 @@
+#!/usr/bin/env bash
+set -u
+
+skill_dir=$(CDPATH= cd -- "$(dirname -- "$0")/.." && pwd)
+
+locate_source() {
+  if [ "$#" -gt 0 ] && [ -n "$1" ]; then
+    if [ -d "$1/yss-microservice-components/yss-component-cache-parent" ]; then
+      echo "$1"
+      return 0
+    fi
+    return 1
+  fi
+  if [ -n "${YSS_SOURCE_ROOT:-}" ] && [ -d "$YSS_SOURCE_ROOT/yss-microservice-components/yss-component-cache-parent" ]; then
+    echo "$YSS_SOURCE_ROOT"
+    return 0
+  fi
+  for candidate in "$PWD" "$PWD/.." "$HOME/Projects/yss-cloud-microservice" "$HOME/Documents/yss-project/yss-cloud-microservice"; do
+    if [ -d "$candidate/yss-microservice-components/yss-component-cache-parent" ]; then
+      (CDPATH= cd -- "$candidate" && pwd)
+      return 0
+    fi
+  done
+  return 1
+}
+
+source_root=$(locate_source "${1:-}") || {
+  echo "ERROR: cannot locate yss-component-cache-parent; pass source root or set YSS_SOURCE_ROOT" >&2
+  exit 2
+}
+
+parent="$source_root/yss-microservice-components/yss-component-cache-parent"
+annotation="$parent/yss-component-spring-cache/src/main/java/com/yss/cloud/cache/annotation/ClearCache.java"
+properties="$parent/yss-component-spring-cache/src/main/java/com/yss/cloud/cache/YssCacheProperties.java"
+connection="$parent/yss-component-redis-cache/src/main/java/com/yss/cloud/cache/redis/config/RedisConnFactoryConfig.java"
+index="$skill_dir/references/source-index.md"
+fail=0
+
+require_text() {
+  file=$1
+  pattern=$2
+  label=$3
+  if ! grep -Eq "$pattern" "$file"; then
+    echo "STALE: $label not found in $file"
+    fail=1
+  fi
+}
+
+require_text "$annotation" 'boolean allEntries\(\)' 'ClearCache.allEntries'
+require_text "$annotation" 'boolean beforeInvocation\(\)' 'ClearCache.beforeInvocation'
+require_text "$properties" 'private Duration defaultTtl' 'yss.cache.default-ttl'
+require_text "$properties" 'private boolean fallbackEnabled' 'Redis fallback-enabled'
+require_text "$properties" 'private String fallbackType' 'Redis fallback-type'
+require_text "$properties" 'private boolean clearFallbackOnRecovery' 'Redis clear-fallback-on-recovery'
+require_text "$connection" 'cannot be configured together' 'Sentinel/Cluster mutual exclusion'
+require_text "$connection" 'database must be 0' 'Cluster database 0 guard'
+
+for module in yss-component-spring-cache yss-component-redis-cache yss-component-caffeine-cache yss-component-cache-starter yss-component-jetcache; do
+  if ! grep -q "$module" "$index"; then
+    echo "STALE: source-index is missing module $module"
+    fail=1
+  fi
+done
+
+generated=$(sed -n 's/^Generated: //p' "$index" | head -1)
+if [ -z "$generated" ]; then
+  echo "STALE: source-index has no Generated timestamp"
+  fail=1
+else
+  echo "INFO: source-index generated at $generated"
+fi
+
+if [ "$annotation" -nt "$index" ] || [ "$properties" -nt "$index" ] || [ "$connection" -nt "$index" ]; then
+  echo "STALE: critical cache source is newer than source-index"
+  fail=1
+fi
+
+if [ "$fail" -ne 0 ]; then
+  echo "RESULT: skill/source contract drift detected; refresh with yss-source-index and review semantic references"
+  exit 1
+fi
+
+echo "RESULT: yss-cache critical contracts match source at $source_root"
+exit 0

package/template/.agents/skills/yss-cache/scripts/inspect-cache-usage.sh

@@ -0,0 +1,96 @@
+#!/usr/bin/env bash
+set -u
+
+usage() {
+  echo "Usage: $0 <project-root>" >&2
+}
+
+if [ "$#" -ne 1 ]; then
+  usage
+  exit 2
+fi
+
+root=$1
+if [ ! -d "$root" ]; then
+  echo "ERROR: project root does not exist: $root" >&2
+  exit 2
+fi
+
+if command -v rg >/dev/null 2>&1; then
+  search() { rg -n --hidden --glob '!target/**' --glob '!.git/**' --glob '*.java' --glob '*.yml' --glob '*.yaml' --glob '*.properties' --glob 'pom.xml' "$1" "$root" 2>/dev/null || true; }
+  files() { rg --files "$root" -g '*.yml' -g '*.yaml' -g '*.properties' -g '*.java' -g 'pom.xml'; }
+else
+  search() { grep -REn "$1" "$root" --include='*.java' --include='*.yml' --include='*.yaml' --include='*.properties' --include='pom.xml' 2>/dev/null || true; }
+  files() { find "$root" -type f \( -name '*.java' -o -name '*.yml' -o -name '*.yaml' -o -name '*.properties' -o -name 'pom.xml' \); }
+fi
+
+tmp=${TMPDIR:-/tmp}/yss-cache-inspect.$$
+trap 'rm -f "$tmp"' EXIT HUP INT TERM
+files >"$tmp"
+if [ ! -s "$tmp" ]; then
+  echo "ERROR: no Java, Maven, or configuration files found under $root" >&2
+  exit 2
+fi
+
+fail=0
+echo "YSS cache usage inspection: $root"
+
+report() {
+  level=$1
+  title=$2
+  pattern=$3
+  result=$(search "$pattern")
+  if [ -n "$result" ]; then
+    echo
+    echo "[$level] $title"
+    echo "$result" | sed -n '1,20p'
+  fi
+}
+
+report INFO "Cache component dependencies" 'yss-component-(cache-starter|spring-cache|redis-cache|caffeine-cache|hazelcast-cache|jetcache)'
+report INFO "Cache enable annotations" '@EnableYssCloud(Cache|RedisCache)'
+report INFO "YSS cache annotations" '@(QueryCache|UpdateCache|ClearCache)'
+report INFO "Configured backend and TTL" 'yss\.cache\.(active-type|default-ttl)|active-type:|default-ttl:'
+report INFO "Redis fallback configuration" 'fallback-(enabled|type)|clear-fallback-on-recovery'
+report INFO "RedisTemplate injection contracts" 'RedisTemplate[[:space:]]*<'
+
+sentinel=$(search 'spring\.redis\.sentinel|sentinel:')
+cluster=$(search 'spring\.redis\.cluster|cluster:')
+if [ -n "$sentinel" ] && [ -n "$cluster" ]; then
+  echo
+  echo "[ERROR] Both Redis Sentinel and Cluster configuration markers were found. Confirm they are not active in the same profile."
+  fail=1
+fi
+
+if [ -n "$cluster" ]; then
+  nonzero=$(search 'spring\.redis\.database[[:space:]]*=[[:space:]]*[1-9][0-9]*|database:[[:space:]]*[1-9][0-9]*')
+  if [ -n "$nonzero" ]; then
+    echo
+    echo "[ERROR] Redis Cluster requires database 0."
+    echo "$nonzero" | sed -n '1,20p'
+    fail=1
+  fi
+fi
+
+clear_without_key=$(search '@ClearCache[[:space:]]*(\([^)]*\))?')
+if [ -n "$clear_without_key" ]; then
+  echo
+  echo "[REVIEW] ClearCache usages found. Verify each use has a stable key or explicit allEntries=true; no-arg methods produce SimpleKey.EMPTY."
+fi
+
+query=$(search '@QueryCache')
+update=$(search '@(UpdateCache|ClearCache)')
+if [ -n "$query" ] && [ -z "$update" ]; then
+  echo
+  echo "[REVIEW] QueryCache is used but no UpdateCache/ClearCache annotation was found. Inspect explicit invalidation paths."
+fi
+
+if [ "$fail" -ne 0 ]; then
+  echo
+  echo "RESULT: blocking cache configuration defects found"
+  exit 1
+fi
+
+echo
+echo "RESULT: no statically provable blocking cache defect found; REVIEW items still require code inspection"
+exit 0

package/template/.agents/skills/yss-cache/scripts/verify-cache-component.sh

@@ -0,0 +1,101 @@
+#!/usr/bin/env bash
+set -u
+
+source_root=""
+consumer_root=""
+consumer_module=""
+
+usage() {
+  echo "Usage: $0 [--source-root PATH] [--consumer-root PATH --consumer-module MODULE]" >&2
+}
+
+while [ "$#" -gt 0 ]; do
+  case "$1" in
+    --source-root) [ "$#" -ge 2 ] || { usage; exit 2; }; source_root=$2; shift 2 ;;
+    --consumer-root) [ "$#" -ge 2 ] || { usage; exit 2; }; consumer_root=$2; shift 2 ;;
+    --consumer-module) [ "$#" -ge 2 ] || { usage; exit 2; }; consumer_module=$2; shift 2 ;;
+    -h|--help) usage; exit 0 ;;
+    *) usage; exit 2 ;;
+  esac
+done
+
+if [ -z "$source_root" ]; then
+  source_root=${YSS_SOURCE_ROOT:-}
+fi
+if [ -z "$source_root" ]; then
+  for candidate in "$PWD" "$PWD/.." "$HOME/Projects/yss-cloud-microservice" "$HOME/Documents/yss-project/yss-cloud-microservice"; do
+    if [ -d "$candidate/yss-microservice-components/yss-component-cache-parent" ]; then
+      source_root=$candidate
+      break
+    fi
+  done
+fi
+
+parent="${source_root%/}/yss-microservice-components/yss-component-cache-parent"
+if [ -z "$source_root" ] || [ ! -f "$parent/pom.xml" ]; then
+  echo "ERROR: cannot locate cache parent; use --source-root or YSS_SOURCE_ROOT" >&2
+  exit 2
+fi
+if [ ! -x "$source_root/mvnw" ]; then
+  echo "ERROR: Maven wrapper is missing or not executable: $source_root/mvnw" >&2
+  exit 2
+fi
+if { [ -n "$consumer_root" ] && [ -z "$consumer_module" ]; } || { [ -z "$consumer_root" ] && [ -n "$consumer_module" ]; }; then
+  echo "ERROR: --consumer-root and --consumer-module must be provided together" >&2
+  exit 2
+fi
+
+echo "== Cache reactor verify =="
+(cd "$source_root" && ./mvnw -f "$parent/pom.xml" verify) || exit 1
+
+echo "== Docker integration status =="
+report="$parent/yss-component-redis-cache/target/surefire-reports/TEST-com.yss.cloud.cache.redis.config.RedisStandaloneIntegrationTest.xml"
+if command -v docker >/dev/null 2>&1 && docker info >/dev/null 2>&1; then
+  if [ ! -f "$report" ]; then
+    echo "ERROR: Docker is available but Redis integration report is missing" >&2
+    exit 1
+  fi
+  if grep -Eq 'skipped="[1-9]' "$report"; then
+    echo "ERROR: Docker is available but Redis integration test was skipped" >&2
+    exit 1
+  fi
+  echo "PASS: real Redis integration test executed"
+else
+  echo "SKIP: Docker is unavailable; Redis integration test may be skipped by assumption"
+fi
+
+echo "== Diff whitespace =="
+if command -v git >/dev/null 2>&1 && git -C "$source_root" rev-parse --is-inside-work-tree >/dev/null 2>&1; then
+  git -C "$source_root" diff --check || exit 1
+else
+  echo "SKIP: source root is not a Git worktree"
+fi
+
+echo "== Java 8 bytecode =="
+classes=$(find "$parent" -path '*/target/classes/*.class' -type f | head -1)
+if [ -z "$classes" ]; then
+  echo "ERROR: no compiled cache class found" >&2
+  exit 1
+fi
+if ! command -v javap >/dev/null 2>&1; then
+  echo "ERROR: javap is required for bytecode verification" >&2
+  exit 2
+fi
+majors=$(find "$parent" -path '*/target/classes/*.class' -type f -exec javap -verbose {} \; 2>/dev/null | sed -n 's/.*major version: *//p' | sort -u)
+if [ "$majors" != "52" ]; then
+  echo "ERROR: expected only Java 8 major version 52, found: $majors" >&2
+  exit 1
+fi
+echo "PASS: all cache classes use major version 52"
+
+if [ -n "$consumer_root" ]; then
+  echo "== Consumer build =="
+  if [ ! -x "$consumer_root/mvnw" ] || [ ! -f "$consumer_root/pom.xml" ]; then
+    echo "ERROR: invalid consumer root: $consumer_root" >&2
+    exit 2
+  fi
+  (cd "$consumer_root" && ./mvnw -pl "$consumer_module" -am -DskipTests package) || exit 1
+fi
+
+echo "RESULT: cache verification passed"
+exit 0

package/template/.claude/skills/ask-matt/SKILL.md

@@ -20,16 +20,16 @@ The route most work travels. You have an idea and want it built.
    - **`/prototype`** to answer the question with throwaway code,
    - **`/handoff`** back what you learned, and reference it from the original idea thread.
 3. **Branch — is this a multi-session build?**
-   - **Yes** → **`/to-prd`** (turn the thread into a PRD) → **`/to-issues`** (split the PRD into independently-grabbable issues). Because the issues are independent, **clear context between each one**: start a fresh session per issue and kick off **`/implement`** by passing it the PRD and the single issue to work on.
+   - **Yes** → **`/to-spec`** (turn the thread into a spec), then **`/to-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. On a local tracker that's one file per ticket under `.scratch/<feature>/tickets/`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed — kick off **`/implement`** per ticket, **clearing context between each one**.
    - **No** → **`/implement`** right here, in the same context window.
 
    Either way, **`/implement`** builds each issue by driving **`/tdd`** internally — one red-green slice at a time — then closes out by running **`/code-review`**, a two-axis review (Standards + Spec) of the diff, before committing. Reach for **`/tdd`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`/code-review`** on its own whenever you want to review a branch or PR against a fixed point.
 
 ### Context hygiene
 
-Keep steps 1–3 in **one unbroken context window** — don't compact or clear until after `/to-issues` — so the grilling, PRD, and issues all build on the same thinking. Each `/implement` then starts fresh, working from the issue.
+Keep steps 1–3 in **one unbroken context window** — don't compact or clear until after `/to-tickets` — so the grilling, spec, and tickets all build on the same thinking. Each `/implement` then starts fresh, working from the ticket.
 
-The limit on this is the **[smart zone](https://www.aihero.dev/ai-coding-dictionary/smart-zone)**: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `/to-issues`, don't push on degraded — `/handoff` and continue in a fresh thread.
+The limit on this is the **[smart zone](https://www.aihero.dev/ai-coding-dictionary/smart-zone)**: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `/to-tickets`, don't push on degraded — `/handoff` and continue in a fresh thread.
 
 ## On-ramps
 
@@ -37,10 +37,14 @@ A starting situation that generates work, then merges onto the main flow.
 
 - **Bugs and requests piling up** → **`/triage`**. It moves issues through triage roles and produces agent-ready issues, which **`/implement`** later picks up.
 
-  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Issues that `/to-issues` produced are already agent-ready, so **don't triage them**.
+  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Tickets that `/to-tickets` produced are already agent-ready, so **don't triage them**.
 
 - **Something's broken** → **`/diagnosing-bugs`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** — one command that already goes red on *this* bug — then fixes with a regression test. Its post-mortem hands off to **`/improve-codebase-architecture`** when the real finding is that there's no good seam to lock the bug down.
 
+- **A huge, foggy effort — a greenfield project or a huge feature build, too big for one session** → **`/wayfinder`**, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a **shared map** of **decision tickets** on the issue tracker and resolves them one at a time — producing **decisions, not deliverables** — until the fog is pushed back and the way is clear. Where **`/grill-with-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't — and it's slower and denser, so save it for exactly that, never a well-scoped feature.
+
+  When the map clears, **it hands off, it doesn't build**: merge onto the main flow at **`/to-spec`**, which collapses the map's linked decisions into a buildable plan, then `/to-tickets` and `/implement` as usual. Looping the map straight into `/implement` skips that collapse and throws the linked detail away — go straight to `/implement` only when the effort turned out genuinely small.
+
 ## Codebase health
 
 Not feature work — upkeep.

package/template/.claude/skills/ask-matt/agents/openai.yaml

@@ -0,0 +1,5 @@
+interface:
+  display_name: "Ask Matt"
+  short_description: "Find the right skill or workflow"
+policy:
+  allow_implicit_invocation: false

package/template/.claude/skills/code-review/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: code-review
-description: Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
+description: Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/Spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
 ---
 
 Two-axis review of the diff between `HEAD` and a fixed point the user supplies:
 
 - **Standards** — does the code conform to this repo's documented coding standards?
-- **Spec** — does the code faithfully implement the originating issue / PRD / spec?
+- **Spec** — does the code faithfully implement the originating Ticket / Spec?
 
 Both axes run as **parallel sub-agents** so they don't pollute each other's context, then this skill aggregates their findings.
 
@@ -26,9 +26,9 @@ Before going further, confirm the fixed point resolves (`git rev-parse <fixed-po
 
 Look for the originating spec, in this order:
 
-1. Issue references in the commit messages (`#123`, `Closes #45`, GitLab `!67`, etc.) — fetch via the workflow in `docs/agents/issue-tracker.md`.
+1. Ticket references in the commit messages (`#123`, `Closes #45`, GitLab `!67`, etc.) — fetch via the workflow in `docs/agents/issue-tracker.md`.
 2. A path the user passed as an argument.
-3. A PRD/spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature.
+3. A Spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature.
 4. If nothing is found, ask the user where the spec is. If they say there isn't one, the **Spec** sub-agent will skip and report "no spec available".
 
 ### 3. Identify the standards sources

package/template/.claude/skills/code-review/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Code Review"
+  short_description: "Review a diff on standards and spec"

package/template/.claude/skills/codebase-design/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Codebase Design"
+  short_description: "Vocabulary for deep-module design"

package/template/.claude/skills/competitive-intelligence/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: competitive-intelligence
-description: Use when researching competitors, market positioning, pricing, feature gaps, customer sentiment, or category trends before Discovery, PRD, product strategy, or roadmap decisions.
+description: Use when researching competitors, market positioning, pricing, feature gaps, customer sentiment, or category trends before Discovery, Spec, product strategy, or roadmap decisions.
 ---
 
 # Competitive Intelligence
 
 Source requested for this project: `anthropics/knowledge-work-plugins`, `sales/skills/competitive-intelligence`.
 
-Use this skill when competitive or market facts are needed to shape product Discovery, PRD scope, positioning, differentiation, pricing assumptions, or roadmap tradeoffs.
+Use this skill when competitive or market facts are needed to shape product Discovery, Spec scope, positioning, differentiation, pricing assumptions, or roadmap tradeoffs.
 
 ## Core Rules
 
@@ -43,11 +43,11 @@ Use this skill when competitive or market facts are needed to shape product Disc
    - Differentiators and defensibility.
    - Gaps and underserved jobs-to-be-done.
    - Risks if we copy the competitor too closely.
-   - Product opportunities for PRD or roadmap.
+   - Product opportunities for Spec or roadmap.
 5. Hand off to lifecycle assets:
    - Update Discovery findings in `docs/discovery/`.
    - Create or update a competitor matrix in `docs/discovery/reports/`.
-   - Feed stable user, pain, MVP, non-goal, and success criteria into `grill-with-docs` and `to-prd`.
+   - Feed stable user, pain, MVP, non-goal, and success criteria into `grill-with-docs` and `to-spec`.
    - Record uncertain claims as assumptions, not requirements.
 
 ## Output Shape
@@ -76,7 +76,7 @@ For a quick brief:
 | 维度 | 竞品 A | 竞品 B | 我们的机会 |
 |---|---|---|---|
 
-### PRD 输入
+### Spec 输入
 - 用户 / 痛点：
 - MVP 建议：
 - 非目标范围：

package/template/.claude/skills/diagnosing-bugs/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Diagnosing Bugs"
+  short_description: "Diagnose hard bugs and regressions"

package/template/.claude/skills/domain-modeling/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Domain Modeling"
+  short_description: "Build and sharpen a domain model"

package/template/.claude/skills/excalidraw-diagram-generator/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: excalidraw-diagram-generator
-description: 'Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.'
+description: 'Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "draw business/functional/system/data architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, business flows, system architecture, ER, class, sequence, lineage, and data flow diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.'
 ---
 
 # Excalidraw Diagram Generator
@@ -31,6 +31,27 @@ Use this skill when users request:
 - 🔄 **Sequence Diagrams**: Object interactions over time, message flows
 - 🗃️ **ER Diagrams**: Database entity relationships, data models
 
+## YSS Lifecycle Integration
+
+In YSS projects, this skill is a visualization and review aid. It can clarify lifecycle artifacts, but it must not replace Discovery, Spec, OpenAPI, ADR, Spec Delta design, or tests.
+
+Use it after the relevant source artifact exists:
+
+| Lifecycle artifact | Typical timing | Useful diagrams | Recommended output |
+|--------------------|----------------|-----------------|--------------------|
+| Business architecture | Opportunity exploration / Discovery | user journey, value stream, swimlane, capability map, ecosystem map | `docs/discovery/diagrams/` or `docs/architecture/diagrams/` |
+| Functional architecture | Spec baseline / product design / Spec calibration | feature map, module map, dependency graph, page map | `docs/design/diagrams/` or `docs/architecture/diagrams/` |
+| System architecture | Engineering baseline / Architecture / Spec Delta design | C4/container view, deployment, sequence, DDD boundary, DFD | `docs/architecture/diagrams/` |
+| Data architecture | Detailed design before persistence / repository work | ER, class, meta-model, lineage graph, query/data-flow diagram | `docs/architecture/diagrams/` |
+
+Guardrails:
+
+- Do not invent product requirements or architecture decisions only from the diagram prompt.
+- Reference the source artifact in the Markdown document that links the `.excalidraw` file.
+- If a diagram exposes a missing field, unclear state, dependency, or boundary problem, write that finding back to the source Spec, OpenAPI Draft, architecture document, ADR, Spec Delta design, or issue.
+- Do not require diagrams for small copy, style, configuration, or single-point bug fixes.
+- For data modeling, metadata management, model versioning, or lineage-analysis products, prefer ER, class/meta-model, DFD, and lineage diagrams before persistence implementation.
+
 ## Prerequisites
 
 - Clear description of what should be visualized
@@ -178,7 +199,7 @@ Structure the complete Excalidraw file:
 ### Layout Tips
 
 1. **Start positions**: Center important elements, use consistent spacing
-2. **Spacing**: 
+2. **Spacing**:
    - Horizontal gap: 200-300px between elements
    - Vertical gap: 100-150px between rows
 3. **Colors**: Use consistent color scheme
@@ -315,18 +336,18 @@ For specialized diagrams (e.g., AWS/GCP/Azure architecture diagrams), you can us
 
    ```
    To use [AWS/GCP/Azure/etc.] architecture icons, please follow these steps:
-   
+
    1. Visit https://libraries.excalidraw.com/
    2. Search for "[AWS Architecture Icons/etc.]" and download the .excalidrawlib file
    3. Create directory: skills/excalidraw-diagram-generator/libraries/[icon-set-name]/
    4. Place the downloaded file in that directory
    5. Run the splitter script:
       python skills/excalidraw-diagram-generator/scripts/split-excalidraw-library.py skills/excalidraw-diagram-generator/libraries/[icon-set-name]/
-   
+
    This will split the library into individual icon files for efficient use.
    After setup is complete, I can create your diagram using the actual AWS/cloud icons.
-   
-   Alternatively, I can create the diagram now using simple shapes (rectangles, ellipses) 
+
+   Alternatively, I can create the diagram now using simple shapes (rectangles, ellipses)
    which you can later replace with icons manually in Excalidraw.
    ```
 
@@ -389,15 +410,15 @@ The repository includes Python scripts that handle icon integration automaticall
      <diagram-path> <icon-name> <x> <y> [--label "Text"] [--library-path PATH]
    ```
    - Edit via `.excalidraw.edit` is enabled by default to avoid overwrite issues; pass `--no-use-edit-suffix` to disable.
-   
+
    **Examples**:
    ```bash
    # Add EC2 icon at position (400, 300) with label
    python scripts/add-icon-to-diagram.py diagram.excalidraw EC2 400 300 --label "Web Server"
-   
+
    # Add VPC icon at position (200, 150)
    python scripts/add-icon-to-diagram.py diagram.excalidraw VPC 200 150
-   
+
    # Add icon from different library
    python scripts/add-icon-to-diagram.py diagram.excalidraw Compute-Engine 500 200 \
      --library-path libraries/gcp-icons --label "API Server"
@@ -409,15 +430,15 @@ The repository includes Python scripts that handle icon integration automaticall
      <diagram-path> <from-x> <from-y> <to-x> <to-y> [--label "Text"] [--style solid|dashed|dotted] [--color HEX]
    ```
    - Edit via `.excalidraw.edit` is enabled by default to avoid overwrite issues; pass `--no-use-edit-suffix` to disable.
-   
+
    **Examples**:
    ```bash
    # Simple arrow from (300, 250) to (500, 300)
    python scripts/add-arrow.py diagram.excalidraw 300 250 500 300
-   
+
    # Arrow with label
    python scripts/add-arrow.py diagram.excalidraw 300 250 500 300 --label "HTTPS"
-   
+
    # Dashed arrow with custom color
    python scripts/add-arrow.py diagram.excalidraw 400 350 600 400 --style dashed --color "#7950f2"
    ```
@@ -426,14 +447,14 @@ The repository includes Python scripts that handle icon integration automaticall
    ```bash
    # Step 1: Create base diagram with title and structure
    # (Create .excalidraw file with initial elements)
-   
+
    # Step 2: Add icons with labels
    python scripts/add-icon-to-diagram.py my-diagram.excalidraw "Internet-gateway" 200 150 --label "Internet Gateway"
    python scripts/add-icon-to-diagram.py my-diagram.excalidraw VPC 250 250
    python scripts/add-icon-to-diagram.py my-diagram.excalidraw ELB 350 300 --label "Load Balancer"
    python scripts/add-icon-to-diagram.py my-diagram.excalidraw EC2 450 350 --label "EC2 Instance"
    python scripts/add-icon-to-diagram.py my-diagram.excalidraw RDS 550 400 --label "Database"
-   
+
    # Step 3: Add connecting arrows
    python scripts/add-arrow.py my-diagram.excalidraw 250 200 300 250  # Internet → VPC
    python scripts/add-arrow.py my-diagram.excalidraw 300 300 400 300  # VPC → ELB
@@ -453,7 +474,7 @@ The repository includes Python scripts that handle icon integration automaticall
 
 Only use this if Python scripts are unavailable:
 
-1. **Check for libraries**: 
+1. **Check for libraries**:
    ```
    List directory: skills/excalidraw-diagram-generator/libraries/
    Look for subdirectories containing reference.md files
@@ -549,7 +570,7 @@ python scripts/add-arrow.py my-aws-diagram.excalidraw 565 330 650 350 --label "S
    - `icons/Internet-gateway.json` (298 lines)
    - `icons/VPC.json` (550 lines)
    - `icons/ELB.json` (363 lines)
-   - `icons/EC2.json` (231 lines) 
+   - `icons/EC2.json` (231 lines)
    - `icons/RDS.json` (similar size)
    **Total: ~2000+ lines of JSON to process**
 4. Extract elements from each JSON