dev-playbooks 1.0.13 → 1.0.15

package/README.md

@@ -178,7 +178,6 @@ Run devbooks-spec-gardener skill for change add-oauth2
 | devbooks-proposal-debate-workflow | Triangle debate (Author/Challenger/Judge) |
 | devbooks-design-doc | Create a design doc |
 | devbooks-spec-contract | Define specs & contracts |
-| devbooks-c4-map | Generate a C4 map |
 | devbooks-implementation-plan | Create an implementation plan |
 
 ### Apply stage

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-playbooks",
-  "version": "1.0.13",
+  "version": "1.0.15",
   "description": "AI-powered spec-driven development workflow",
   "keywords": [
     "devbooks",

package/skills/Skills-Usage-Guide.md

@@ -171,28 +171,6 @@ If you are not using DevBooks, replace `dev-playbooks/specs` / `dev-playbooks/ch
 
 ---
 
-## `devbooks-c4-map` (C4 Map Maintainer)
-
-- Purpose: maintain/update the authoritative C4 architecture map (truth) and produce a C4 Delta per change.
-- When to use:
-  - Proposal stage: describe boundary/dependency direction changes in `design.md` (C4 Delta only; do not modify current truth)
-  - Review/archive stage: change is implemented; update the authoritative map at `(<truth-root>/architecture/c4.md)`
-- Copy-paste prompts:
-  - Proposal stage (C4 Delta only; do not edit current truth):
-    ```text
-    You are C4 Map Maintainer. Explicitly use `devbooks-c4-map`, but during proposal stage do NOT modify `dev-playbooks/specs/architecture/c4.md` (current truth).
-    First read: `dev-playbooks/specs/architecture/c4.md` (if present) + `dev-playbooks/changes/<change-id>/proposal.md` + `dev-playbooks/changes/<change-id>/design.md`.
-    Output: a **C4 Delta** section that I can paste into `dev-playbooks/changes/<change-id>/design.md` (C1/C2/C3 add/modify/remove + dependency direction changes + suggested architecture guardrails/fitness tests).
-    ```
-  - Review/archive stage (update current truth map):
-    ```text
-    You are C4 Map Maintainer. Explicitly use `devbooks-c4-map`.
-    First read: `dev-playbooks/specs/architecture/c4.md` (if present) + `dev-playbooks/changes/<change-id>/design.md` + relevant code changes (to confirm the change is real).
-    Update (or create a minimal skeleton with TODOs): `dev-playbooks/specs/architecture/c4.md`.
-    ```
-
----
-
 ## `devbooks-implementation-plan` (Planner / tasks.md)
 
 - Purpose: derive an implementation plan `tasks.md` from `design.md` (critical path / side quests / checkpoints), tied to verification anchors (must not reference `tests/`).

package/skills/_shared/mcp-enhancement-template.md

@@ -91,7 +91,6 @@ The following Skills depend on MCP and require the full MCP Enhancement section:
 | devbooks-index-bootstrap | mcp__ckb__getStatus | Index status detection |
 | devbooks-federation | mcp__ckb__*, mcp__github__* | Cross-repo analysis |
 | devbooks-router | mcp__ckb__getStatus | Index availability detection |
-| devbooks-c4-map | mcp__ckb__getArchitecture | Module dependency graph |
 | devbooks-spec-contract | mcp__ckb__findReferences | Reference detection |
 | devbooks-entropy-monitor | mcp__ckb__getHotspots | Hotspot trend analysis |
 | devbooks-delivery-workflow | mcp__ckb__getStatus | Index detection |

package/skills/devbooks-brownfield-bootstrap/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devbooks-brownfield-bootstrap
-description: devbooks-brownfield-bootstrap：存量项目初始化：在当前真理目录为空时生成项目画像、术语表、基线规格与最小验证锚点，避免"边补 specs 边改行为"。用户说"存量初始化/基线 specs/项目画像/建立 glossary/把老项目接入上下文协议"等时使用。
+description: "devbooks-brownfield-bootstrap: Brownfield project initialization. When the truth directory is empty, generate project profile, glossary, baseline specs, and minimum verification anchors to avoid 'patching specs while changing behavior'. Use when user says 'brownfield init/baseline specs/project profile/establish glossary/onboard legacy project to context protocol' etc."
 tools:
   - Glob
   - Grep
@@ -15,217 +15,262 @@ tools:
   - mcp__ckb__getModuleOverview
 ---
 
-# DevBooks：存量项目初始化（Brownfield Bootstrap）
+# DevBooks: Brownfield Bootstrap
 
-## 前置：配置发现（协议无关）
+## Prerequisites: Configuration Discovery (Protocol Agnostic)
 
-- `<truth-root>`：当前真理目录根
-- `<change-root>`：变更包目录根
-- `<devbooks-root>`：DevBooks 管理目录（通常是 `dev-playbooks/`）
+- `<truth-root>`: Current truth directory root
+- `<change-root>`: Change package directory root
+- `<devbooks-root>`: DevBooks management directory (usually `dev-playbooks/`)
 
-执行前**必须**按以下顺序查找配置（找到后停止）：
-1. `.devbooks/config.yaml`（如存在）→ 解析并使用其中的映射
-2. `dev-playbooks/project.md`（如存在）→ DevBooks 2.0 协议，使用默认映射
-4. `project.md`（如存在）→ template 协议，使用默认映射
-5. 若仍无法确定 → **创建 DevBooks 目录结构并初始化基础配置**
+Before execution, **must** search for configuration in the following order (stop when found):
+1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
+2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+3. `project.md` (if exists) → Template protocol, use default mappings
+5. If still unable to determine → **Create DevBooks directory structure and initialize basic configuration**
 
-**关键约束**：
-- 如果配置中指定了 `agents_doc`（规则文档），**必须先阅读该文档**再执行任何操作
-- 禁止猜测目录根
-- 禁止跳过规则文档阅读
+**Key Constraints**:
+- If configuration specifies `agents_doc` (rules document), **must read that document first** before executing any operations
+- Do not guess directory roots
+- Do not skip reading rules document
 
 ---
 
-## 核心职责
+## Core Responsibilities
 
-存量项目初始化包含以下职责：
+Brownfield project initialization includes the following responsibilities:
 
-### 1. 基础配置文件初始化（新增）
+### 1. Basic Configuration File Initialization
 
-在 `<devbooks-root>/`（通常是 `dev-playbooks/`）下检查并创建：
+Check and create in `<devbooks-root>/` (usually `dev-playbooks/`):
 
-| 文件 | 用途 | 创建条件 |
-|------|------|----------|
-| `constitution.md` | 项目宪法（GIP 原则） | 文件不存在时 |
-| `project.md` | 项目上下文（技术栈/约定） | 文件不存在时 |
+| File | Purpose | Creation Condition |
+|------|---------|-------------------|
+| `constitution.md` | Project constitution (GIP principles) | When file doesn't exist |
+| `project.md` | Project context (tech stack/conventions) | When file doesn't exist |
 
-**创建方式**：
-- **不是简单复制模板**，而是根据代码分析结果定制内容
-- `constitution.md`：基于默认 GIP 原则，可根据项目特性调整
-- `project.md`：根据代码分析结果填充：
-  - 技术栈（语言/框架/数据库）
-  - 开发约定（代码风格/测试策略/Git 工作流）
-  - 领域上下文（核心概念/角色定义）
-  - 目录根映射
+**Creation Method**:
+- **Not simple template copying**, but customized content based on code analysis results
+- `constitution.md`: Based on default GIP principles, can be adjusted according to project characteristics
+- `project.md`: Filled based on code analysis results:
+  - Tech stack (language/framework/database)
+  - Development conventions (code style/testing strategy/Git workflow)
+  - Domain context (core concepts/role definitions)
+  - Directory root mappings
 
-### 2. 项目画像与元数据
+### 2. Project Profile and Metadata
 
-在 `<truth-root>/_meta/` 下生成：
+Generate in `<truth-root>/_meta/`:
 
-| 产物 | 路径 | 说明 |
-|------|------|------|
-| 项目画像 | `_meta/project-profile.md` | 三层架构的详细技术画像 |
-| 术语表 | `_meta/glossary.md` | 统一语言表（可选但推荐） |
-| 领域概念 | `_meta/key-concepts.md` | CKB 提取的概念（增强模式） |
+| Artifact | Path | Description |
+|----------|------|-------------|
+| Project profile | `_meta/project-profile.md` | Detailed technical profile with three-layer architecture |
+| Glossary | `_meta/glossary.md` | Unified language table (optional but recommended) |
+| Domain concepts | `_meta/key-concepts.md` | Concepts extracted by CKB (enhanced mode) |
 
-### 3. 架构分析产物
+### 3. Architecture Analysis Artifacts
 
-在 `<truth-root>/architecture/` 下生成：
+Generate in `<truth-root>/architecture/`:
 
-| 产物 | 路径 | 数据来源 |
-|------|------|----------|
-| 模块依赖图 | `architecture/module-graph.md` | `mcp__ckb__getArchitecture` |
-| 技术债热点 | `architecture/hotspots.md` | `mcp__ckb__getHotspots` |
+| Artifact | Path | Data Source |
+|----------|------|-------------|
+| **C4 Architecture Map** | `architecture/c4.md` | Comprehensive analysis + CKB (enhanced mode) |
+| Module dependency graph | `architecture/module-graph.md` | `mcp__ckb__getArchitecture` |
+| Technical debt hotspots | `architecture/hotspots.md` | `mcp__ckb__getHotspots` |
+| Layering constraints | `architecture/layering-constraints.md` | Code analysis (optional) |
 
-### 4. 基线变更包
+> **Design Decision**: C4 architecture map is now generated by brownfield-bootstrap during initialization. Subsequent architecture changes are recorded in design.md's Architecture Impact section and merged by spec-gardener during archiving.
 
-在 `<change-root>/<baseline-id>/` 下生成：
+### 4. Baseline Change Package
 
-| 产物 | 说明 |
-|------|------|
-| `proposal.md` | 基线范围、In/Out、风险 |
-| `design.md` | 现状盘点（capability inventory） |
-| `specs/<cap>/spec.md` | 基线 spec deltas（ADDED 为主） |
-| `verification.md` | 最小验证锚点计划 |
+Generate in `<change-root>/<baseline-id>/`:
+
+| Artifact | Description |
+|----------|-------------|
+| `proposal.md` | Baseline scope, In/Out, risks |
+| `design.md` | Current state inventory (capability inventory) |
+| `specs/<cap>/spec.md` | Baseline spec deltas (mainly ADDED) |
+| `verification.md` | Minimum verification anchor plan |
 
 ---
 
-## COD 模型生成（Code Overview & Dependencies）
+## COD Model Generation (Code Overview & Dependencies)
+
+Automatically generate project's "code map" during initialization (requires CKB MCP Server available, otherwise skip):
+
+### Auto-generated Artifacts
+
+| Artifact | Path | Data Source |
+|----------|------|-------------|
+| **C4 Architecture Map** | `<truth-root>/architecture/c4.md` | Comprehensive analysis |
+| Module dependency graph | `<truth-root>/architecture/module-graph.md` | `mcp__ckb__getArchitecture` |
+| Technical debt hotspots | `<truth-root>/architecture/hotspots.md` | `mcp__ckb__getHotspots` |
+| Domain concepts | `<truth-root>/_meta/key-concepts.md` | `mcp__ckb__listKeyConcepts` |
+| Project profile | `<truth-root>/_meta/project-profile.md` | Comprehensive analysis |
+
+### C4 Architecture Map Generation Rules
+
+C4 map generated during initialization should include:
+
+1. **Context Level**: System's relationship with external actors (users, external systems)
+2. **Container Level**: Containers within the system (applications, databases, services)
+3. **Component Level**: Components within main containers (modules, classes)
+
+**Output Format**:
+
+```markdown
+# C4 Architecture Map
 
-在初始化时自动生成项目的"代码地图"（需要 CKB MCP Server 可用，否则跳过）：
+## System Context
 
-### 自动生成产物
+[Describe system boundaries and external interactions]
 
-| 产物 | 路径 | 数据来源 |
-|------|------|----------|
-| 模块依赖图 | `<truth-root>/architecture/module-graph.md` | `mcp__ckb__getArchitecture` |
-| 技术债热点 | `<truth-root>/architecture/hotspots.md` | `mcp__ckb__getHotspots` |
-| 领域概念 | `<truth-root>/_meta/key-concepts.md` | `mcp__ckb__listKeyConcepts` |
-| 项目画像 | `<truth-root>/_meta/project-profile.md` | 综合分析 |
+## Container Diagram
+
+| Container | Tech Stack | Responsibility |
+|-----------|------------|----------------|
+| <name> | <tech> | <responsibility> |
+
+## Component Diagram
+
+### <Container Name>
+
+| Component | Responsibility | Dependencies |
+|-----------|----------------|--------------|
+| <name> | <responsibility> | <dependencies> |
+
+## Architecture Guardrails
+
+### Layering Constraints
+
+| Layer | Can Depend On | Cannot Depend On |
+|-------|---------------|------------------|
+| <layer> | <allowed> | <forbidden> |
+```
 
-### 热点计算公式
+### Hotspot Calculation Formula
 
 ```
-热点分数 = 变更频率 × 圈复杂度
+Hotspot Score = Change Frequency × Cyclomatic Complexity
 ```
 
-- **高热点**（分数 > 阈值）：频繁修改 + 高复杂度 = Bug 密集区
-- **休眠债务**（高复杂度 + 低频率）：暂时安全但需关注
-- **活跃健康**（高频率 + 低复杂度）：正常维护区域
+- **High Hotspot** (score > threshold): Frequent changes + high complexity = Bug-dense area
+- **Dormant Debt** (high complexity + low frequency): Temporarily safe but needs attention
+- **Active Healthy** (high frequency + low complexity): Normal maintenance area
 
-### 边界识别
+### Boundary Identification
 
-自动区分：
-- **用户代码**：`src/`、`lib/`、`app/` 等（可修改）
-- **库代码**：`node_modules/`、`vendor/`、`.venv/` 等（不可变接口）
-- **生成代码**：`dist/`、`build/`、`*.generated.*` 等（禁止手动修改）
+Automatically distinguish:
+- **User Code**: `src/`, `lib/`, `app/` etc. (modifiable)
+- **Library Code**: `node_modules/`, `vendor/`, `.venv/` etc. (immutable interface)
+- **Generated Code**: `dist/`, `build/`, `*.generated.*` etc. (manual modification prohibited)
 
-### 执行流程
+### Execution Flow
 
-1) **检查图索引**：调用 `mcp__ckb__getStatus`
-   - 若 SCIP 可用 → 使用图基分析
-   - 若不可用 → 提示生成索引或使用 Git 历史分析
+1) **Check Graph Index**: Call `mcp__ckb__getStatus`
+   - If SCIP available → Use graph-based analysis
+   - If unavailable → Prompt to generate index or use Git history analysis
 
-2) **生成 COD 产物**：
+2) **Generate COD Artifacts**:
    ```bash
-   # 获取模块架构
+   # Get module architecture
    mcp__ckb__getArchitecture(depth=2, includeExternalDeps=false)
 
-   # 获取热点（近 30 天）
+   # Get hotspots (last 30 days)
    mcp__ckb__getHotspots(limit=20)
 
-   # 获取领域概念
+   # Get domain concepts
    mcp__ckb__listKeyConcepts(limit=12)
    ```
 
-3) **生成项目画像**：整合以上数据 + 传统分析
+3) **Generate Project Profile**: Integrate above data + traditional analysis
 
-## 参考骨架与模板
+## Reference Scaffolds and Templates
 
-- 工作流：`references/存量项目初始化.md`
-- 代码导航策略：`references/代码导航策略.md`
-- **项目画像模板（三层架构）**：`templates/project-profile-template.md`
-- 一次性提示词：`references/存量项目初始化提示词.md`
-- 模板（按需）：`references/术语表模板.md`
+- Workflow: `references/brownfield-bootstrap.md`
+- Code navigation strategy: `references/code-navigation-strategy.md`
+- **Project profile template (three-layer architecture)**: `templates/project-profile-template.md`
+- One-time prompt: `references/brownfield-bootstrap-prompt.md`
+- Template (as needed): `references/glossary-template.md`
 
 ---
 
-## 上下文感知
+## Context Awareness
 
-本 Skill 在执行前自动检测上下文，选择合适的初始化范围。
+This Skill automatically detects context before execution and selects the appropriate initialization scope.
 
-检测规则参考：`skills/_shared/context-detection-template.md`
+Detection rules reference: `skills/_shared/context-detection-template.md`
 
-### 检测流程
+### Detection Flow
 
-1. 检测 `<devbooks-root>/constitution.md` 是否存在
-2. 检测 `<devbooks-root>/project.md` 是否存在
-3. 检测 `<truth-root>/` 是否为空或基本为空
-4. 检测 CKB 索引是否可用
-5. 检测项目规模和语言栈
+1. Detect if `<devbooks-root>/constitution.md` exists
+2. Detect if `<devbooks-root>/project.md` exists
+3. Detect if `<truth-root>/` is empty or basically empty
+4. Detect if CKB index is available
+5. Detect project scale and language stack
 
-### 本 Skill 支持的模式
+### Modes Supported by This Skill
 
-| 模式 | 触发条件 | 行为 |
-|------|----------|------|
-| **全新初始化** | devbooks-root 不存在或为空 | 创建完整目录结构 + constitution + project + 画像 |
-| **补充配置** | constitution/project 缺失 | 只补充缺失的配置文件 |
-| **完整初始化** | truth-root 为空 | 生成所有基础产物（画像/基线/验证） |
-| **增量初始化** | truth-root 部分存在 | 只补充缺失产物 |
-| **增强模式** | CKB 索引可用 | 使用图分析生成更精确的画像 |
-| **基础模式** | CKB 索引不可用 | 使用传统分析方法 |
+| Mode | Trigger Condition | Behavior |
+|------|-------------------|----------|
+| **Full New Init** | devbooks-root doesn't exist or is empty | Create complete directory structure + constitution + project + profile |
+| **Supplement Config** | constitution/project missing | Only supplement missing configuration files |
+| **Complete Init** | truth-root is empty | Generate all basic artifacts (profile/baseline/verification) |
+| **Incremental Init** | truth-root partially exists | Only supplement missing artifacts |
+| **Enhanced Mode** | CKB index available | Use graph analysis to generate more precise profile |
+| **Basic Mode** | CKB index unavailable | Use traditional analysis methods |
 
-### 检测输出示例
+### Detection Output Example
 
 ```
-检测结果：
-- devbooks-root：存在
-- constitution.md：不存在 → 将创建
-- project.md：不存在 → 将创建
-- truth-root：为空
-- CKB 索引：可用
-- 项目规模：中型（~50K LOC）
-- 运行模式：补充配置 + 完整初始化 + 增强模式
+Detection Results:
+- devbooks-root: Exists
+- constitution.md: Doesn't exist → Will create
+- project.md: Doesn't exist → Will create
+- truth-root: Empty
+- CKB index: Available
+- Project scale: Medium (~50K LOC)
+- Running mode: Supplement Config + Complete Init + Enhanced Mode
 ```
 
 ---
 
-## MCP 增强
+## MCP Enhancement
 
-本 Skill 支持 MCP 运行时增强，自动检测并启用高级功能。
+This Skill supports MCP runtime enhancement, automatically detecting and enabling advanced features.
 
-MCP 增强规则参考：`skills/_shared/mcp-enhancement-template.md`
+MCP enhancement rules reference: `skills/_shared/mcp-enhancement-template.md`
 
-### 依赖的 MCP 服务
+### Required MCP Services
 
-| 服务 | 用途 | 超时 |
-|------|------|------|
-| `mcp__ckb__getStatus` | 检测 CKB 索引可用性 | 2s |
-| `mcp__ckb__getArchitecture` | 获取模块依赖图 | 2s |
-| `mcp__ckb__getHotspots` | 获取技术债热点 | 2s |
-| `mcp__ckb__listKeyConcepts` | 获取领域概念 | 2s |
-| `mcp__ckb__getModuleOverview` | 获取模块概览 | 2s |
+| Service | Purpose | Timeout |
+|---------|---------|---------|
+| `mcp__ckb__getStatus` | Detect CKB index availability | 2s |
+| `mcp__ckb__getArchitecture` | Get module dependency graph | 2s |
+| `mcp__ckb__getHotspots` | Get technical debt hotspots | 2s |
+| `mcp__ckb__listKeyConcepts` | Get domain concepts | 2s |
+| `mcp__ckb__getModuleOverview` | Get module overview | 2s |
 
-### 检测流程
+### Detection Flow
 
-1. 调用 `mcp__ckb__getStatus`（2s 超时）
-2. 若 CKB 可用 → 使用图基分析生成 COD 产物
-3. 若超时或失败 → 降级到传统分析（Git 历史 + 文件统计）
+1. Call `mcp__ckb__getStatus` (2s timeout)
+2. If CKB available → Use graph-based analysis to generate COD artifacts
+3. If timeout or failure → Degrade to traditional analysis (Git history + file statistics)
 
-### 增强模式 vs 基础模式
+### Enhanced Mode vs Basic Mode
 
-| 功能 | 增强模式 | 基础模式 |
-|------|----------|----------|
-| 模块依赖图 | CKB getArchitecture | 目录结构推断 |
-| 技术债热点 | CKB getHotspots | Git log 统计 |
-| 领域概念 | CKB listKeyConcepts | 命名分析 |
-| 边界识别 | 精确模块边界 | 目录约定 |
+| Feature | Enhanced Mode | Basic Mode |
+|---------|---------------|------------|
+| Module dependency graph | CKB getArchitecture | Directory structure inference |
+| Technical debt hotspots | CKB getHotspots | Git log statistics |
+| Domain concepts | CKB listKeyConcepts | Naming analysis |
+| Boundary identification | Precise module boundaries | Directory conventions |
 
-### 降级提示
+### Degradation Notice
 
-当 MCP 不可用时，输出以下提示：
+When MCP is unavailable, output the following notice:
 
 ```
-⚠️ CKB 不可用，使用传统分析方法生成项目画像。
-如需更精确的架构分析，请运行 devbooks-index-bootstrap skill 生成索引。
+Warning: CKB unavailable, using traditional analysis methods to generate project profile.
+For more precise architecture analysis, run devbooks-index-bootstrap skill to generate index.
 ```

package/skills/devbooks-brownfield-bootstrap/references/brownfield-bootstrap.md

@@ -6,7 +6,8 @@ Goal: One-time completion of "project profile and conventions + baseline specs"
 
 Core principles:
 - **Do not try to document the whole system at once**: start with external-facing surfaces (API/CLI/events/config/Schema), then fill internal core later.
-- **Evidence first**: every spec item must point to code/tests/logs/runtime behavior; if unsure, write `TBD` + a verification plan.
+- **Evidence first**: every spec item must point to code/tests/logs/runtime behavior.
+- **TBD policy**: `spec.md` forbids TBD/TODO (gates will reject); unknown items must go into `verification.md` Open Questions or MANUAL verification tasks with a specific verification plan.
 - **Stabilize current behavior before refactoring**: the baseline phase should avoid behavioral change; do not "patch specs while changing behavior" and drift the truth source.
 
 ---
@@ -60,7 +61,7 @@ In `<change-root>/<baseline-id>/specs/<capability>/spec.md`, write **current-sta
 - Requirements/Scenarios must be observable (inputs/outputs/error semantics/invariants)
 
 Notes:
-- If uncertain, write `TBD` and add a verification action to the plan section of `verification.md` (do not guess).
+- If uncertain: **do not write TBD in spec.md**; add a verification action to `verification.md` Open Questions or MANUAL verification tasks (with a verification plan).
 - If you find obvious bugs, do not fix them during baseline; create a separate change for fixes (avoid mixing behavior changes into baseline).
 
 ---

package/skills/devbooks-code-review/SKILL.md

@@ -18,8 +18,8 @@ tools:
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
 2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
-4. `project.md` (if exists) -> template protocol, use default mappings
-5. If still undetermined -> **Stop and ask user**
+3. `project.md` (if exists) -> template protocol, use default mappings
+4. If still undetermined -> **Stop and ask user**
 
 **Key Constraints**:
 - If configuration specifies `agents_doc` (rules document), **must read that document first** before executing any operations
@@ -35,7 +35,7 @@ Before execution, **must** search for configuration in the following order (stop
 - Code formatting
 
 ### 2. Dependency Health Review
-- Layer constraint compliance (see devbooks-c4-map)
+- Layer constraint compliance (see `<truth-root>/architecture/c4.md`)
 - Circular dependency detection
 - Internal module encapsulation (prohibit deep imports of *Internal files)
 - Dependency direction correctness

package/skills/devbooks-code-review/references/code-review-prompt.md

@@ -98,3 +98,8 @@ Output format:
 2) Maintainability risks (recommended)
 3) Style & consistency suggestions (optional)
 4) If new quality gates are needed (lint/complexity/dependency rules), propose them concretely
+5) **Provide an explicit verdict**:
+   - ✅ **APPROVED**: Code quality meets standards, ready to merge
+   - ⚠️ **APPROVED WITH COMMENTS**: Can merge but recommend follow-up improvements (list specific items)
+   - 🔄 **REQUEST CHANGES**: Requires fixes before re-review (list must-fix items)
+   - ❌ **REJECTED**: Serious issues or design flaws, needs to return to design phase

package/skills/devbooks-code-review/references/pr-template-and-guidelines.md

@@ -83,6 +83,8 @@ Inspired by VS Code’s `.github/pull_request_template.md`, this document define
 | L | 500–1000 | 2+ hours | Consider splitting |
 | XL | > 1000 | half day+ | **Must split** |
 
+**Note**: Line count is a **review cost signal**, not a hard structural splitting rule. When splitting would harm module cohesion, distort boundaries, or create duplication, exceeding is allowed but should be explained.
+
 Principle: one PR does one thing; keep it atomic.
 
 ---

package/skills/devbooks-coder/SKILL.md

@@ -20,7 +20,7 @@ tools:
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
 2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
-4. `project.md` (if exists) -> template protocol, use default mappings
+3. `project.md` (if exists) -> template protocol, use default mappings
 5. If still unable to determine -> **Stop and ask the user**
 
 **Key Constraints**:

package/skills/devbooks-coder/references/code-implementation-prompt.md

@@ -23,7 +23,7 @@ Hard constraints (must follow):
 
 Quality gates (must execute):
 - Run tests/static checks related to the change; retain failure outputs as fix evidence.
-- Fix in small steps: each change focuses on one plan item, **single commit < 200 lines**.
+- Fix in small steps: each change focuses on one plan item, **default target: single commit ≤200 lines**; if structural integrity requires exceeding, explain in commit message or PR, and ensure acceptance anchors cover the change and commit sequence is rollbackable.
 - Avoid smells: long functions (P95 < 50 lines), deep nesting, duplicate logic, implicit dependencies, cycles, excessive coupling, cross-layer calls.
 - If lint/complexity/dependency rules exist, comply; if not, state "recommended quality gates to add."
 

package/skills/devbooks-delivery-workflow/SKILL.md

@@ -20,8 +20,8 @@ tools:
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
 2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
-4. `project.md` (if exists) -> template protocol, use default mappings
-5. If still undetermined -> **Stop and ask the user**
+3. `project.md` (if exists) -> template protocol, use default mappings
+4. If still undetermined -> **Stop and ask the user**
 
 **Key Constraints**:
 - If `agents_doc` (rules document) is specified in configuration, **must read that document first** before executing any operations

package/skills/devbooks-design-backport/SKILL.md

@@ -19,8 +19,8 @@ tools:
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
 2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
-4. `project.md` (if exists) → Template protocol, use default mappings
-5. If still undetermined → **Stop and ask the user**
+3. `project.md` (if exists) → Template protocol, use default mappings
+4. If still undetermined → **Stop and ask the user**
 
 **Key Constraints**:
 - If `agents_doc` (rules document) is specified in configuration, **you must read that document first** before executing any operations