cc-devflow 4.5.15 → 4.5.17

package/.claude/skills/cc-roadmap/scripts/lib/roadmap-tracking/schema.js

@@ -51,6 +51,9 @@ const DEFAULT_BACKLOG = {
 
 const DEFAULT_TRACKING = {
   version: 2,
+  outputPolicy: {
+    documentLanguage: 'en'
+  },
   lastSyncedAt: '',
   backlogMeta: {
     roadmapVersion: '',
@@ -115,7 +118,7 @@ function normalizeHeader(value) {
   return String(value || '')
     .trim()
     .toLowerCase()
-    .replace(/[^a-z0-9]+/g, ' ');
+    .replace(/[^\p{L}\p{N}]+/gu, ' ');
 }
 
 function normalizeCell(value) {
@@ -159,7 +162,7 @@ function formatInlineCode(value) {
 
 function normalizeBoolean(value) {
   const normalized = normalizeCell(value).toLowerCase();
-  return normalized === 'yes' || normalized === 'true';
+  return normalized === 'yes' || normalized === 'true' || normalized === '是';
 }
 
 function emptyBacklog() {
@@ -219,6 +222,10 @@ function normalizeTracking(raw) {
 
   return {
     version: 2,
+    outputPolicy: {
+      ...DEFAULT_TRACKING.outputPolicy,
+      ...(raw.outputPolicy || {})
+    },
     lastSyncedAt: String(raw.lastSyncedAt || '').trim(),
     backlogMeta: {
       roadmapVersion: String(backlogMeta.roadmapVersion || '').trim(),
@@ -268,6 +275,14 @@ function normalizeRoadmapState(raw = {}) {
   const context = raw.context || {};
   const route = raw.route || {};
   const architecture = raw.architecture || {};
+  const normalizedMeta = {
+    ...DEFAULT_ROADMAP_STATE.meta,
+    roadmapVersion: String(meta.roadmapVersion || tracking.backlogMeta.roadmapVersion).trim(),
+    skillVersion: String(meta.skillVersion || tracking.backlogMeta.skillVersion).trim(),
+    status: String(meta.status || DEFAULT_ROADMAP_STATE.meta.status).trim(),
+    lastUpdated: String(meta.lastUpdated || tracking.lastSyncedAt).trim(),
+    currentFocusStage: String(meta.currentFocusStage || tracking.backlogMeta.currentFocusStage).trim()
+  };
 
   return {
     ...DEFAULT_ROADMAP_STATE,
@@ -276,14 +291,7 @@ function normalizeRoadmapState(raw = {}) {
       ...DEFAULT_ROADMAP_STATE.outputPolicy,
       ...(raw.outputPolicy || {})
     },
-    meta: {
-      ...DEFAULT_ROADMAP_STATE.meta,
-      roadmapVersion: String(meta.roadmapVersion || tracking.backlogMeta.roadmapVersion).trim(),
-      skillVersion: String(meta.skillVersion || tracking.backlogMeta.skillVersion).trim(),
-      status: String(meta.status || DEFAULT_ROADMAP_STATE.meta.status).trim(),
-      lastUpdated: String(meta.lastUpdated || tracking.lastSyncedAt).trim(),
-      currentFocusStage: String(meta.currentFocusStage || tracking.backlogMeta.currentFocusStage).trim()
-    },
+    meta: normalizedMeta,
     context: {
       ...DEFAULT_ROADMAP_STATE.context,
       ...context,
@@ -301,7 +309,11 @@ function normalizeRoadmapState(raw = {}) {
     },
     stages: Array.isArray(raw.stages) ? raw.stages : [],
     items: tracking.items,
-    backlogMeta: tracking.backlogMeta,
+    backlogMeta: {
+      roadmapVersion: normalizedMeta.roadmapVersion,
+      skillVersion: normalizedMeta.skillVersion,
+      currentFocusStage: normalizedMeta.currentFocusStage
+    },
     dependencyHandoff: tracking.dependencyHandoff,
     lastSyncedAt: tracking.lastSyncedAt,
     handoff: buildRoadmapHandoff(tracking, raw.handoff || {}),
@@ -315,36 +327,78 @@ function normalizeRoadmapState(raw = {}) {
 }
 
 const ROADMAP_HEADER_TO_KEY = new Map(
-  ROADMAP_COLUMNS.map(([header, key]) => [normalizeHeader(header), key])
+  [
+    ...ROADMAP_COLUMNS,
+    ['事项', 'item'],
+    ['阶段', 'stage'],
+    ['优先级', 'priority'],
+    ['主能力', 'primaryCapability'],
+    ['次能力', 'secondaryCapabilities'],
+    ['预期规格变化', 'expectedSpecDelta'],
+    ['依赖', 'dependsOn'],
+    ['状态', 'status'],
+    ['进度', 'progress']
+  ].map(([header, key]) => [normalizeHeader(header), key])
 );
 
 const BACKLOG_QUEUE_HEADER_TO_KEY = new Map(
-  BACKLOG_QUEUE_COLUMNS.map(([header, key]) => [normalizeHeader(header), key])
+  [
+    ...BACKLOG_QUEUE_COLUMNS,
+    ['标题', 'item'],
+    ['来源阶段', 'stage'],
+    ['优先级', 'priority'],
+    ['主能力', 'primaryCapability'],
+    ['次能力', 'secondaryCapabilities'],
+    ['能力缺口', 'capabilityGap'],
+    ['预期规格变化', 'expectedSpecDelta'],
+    ['证据', 'evidence'],
+    ['依赖', 'dependsOn'],
+    ['可并行', 'parallelWith'],
+    ['未知项', 'unknowns'],
+    ['下一决策', 'nextDecision'],
+    ['就绪', 'ready']
+  ].map(([header, key]) => [normalizeHeader(header), key])
 );
 
 const READY_FIELD_MAP = new Map(
   [
     ['Primary Capability', 'primaryCapability'],
+    ['主能力', 'primaryCapability'],
     ['Secondary Capabilities', 'secondaryCapabilities'],
+    ['次能力', 'secondaryCapabilities'],
     ['Why now', 'whyNow'],
+    ['为什么现在做', 'whyNow'],
     ['Success signal', 'successSignal'],
+    ['成功信号', 'successSignal'],
     ['Entry constraints', 'entryConstraints'],
+    ['进入约束', 'entryConstraints'],
     ['Capability gap', 'capabilityGap'],
+    ['能力缺口', 'capabilityGap'],
     ['Expected spec delta', 'expectedSpecDelta'],
+    ['预期规格变化', 'expectedSpecDelta'],
     ['Open risks', 'openRisks'],
+    ['未决风险', 'openRisks'],
     ['First planning question', 'firstPlanningQuestion'],
+    ['首个规划问题', 'firstPlanningQuestion'],
     ['Required context to load', 'requiredContextToLoad'],
+    ['必须加载的上下文', 'requiredContextToLoad'],
     ['Depends On', 'dependsOn'],
+    ['依赖', 'dependsOn'],
     ['Parallel With', 'parallelWith'],
-    ['Why this is ready now', 'whyReadyNow']
+    ['可并行', 'parallelWith'],
+    ['Why this is ready now', 'whyReadyNow'],
+    ['为什么现在已就绪', 'whyReadyNow']
   ].map(([label, key]) => [normalizeHeader(label), key])
 );
 
 const PARKED_FIELD_MAP = new Map(
   [
     ['Reason parked', 'parkedReason'],
+    ['暂存原因', 'parkedReason'],
     ['Trigger to reopen', 'triggerToReopen'],
-    ['Missing evidence', 'missingEvidence']
+    ['重新打开触发条件', 'triggerToReopen'],
+    ['Missing evidence', 'missingEvidence'],
+    ['缺失证据', 'missingEvidence']
   ].map(([label, key]) => [normalizeHeader(label), key])
 );
 

package/CHANGELOG.md

@@ -9,12 +9,30 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [4.5.15] - 2026-05-14
+_No unreleased changes._
+
+## [4.5.17] - 2026-05-17
 
 ### Added
 
-- Added Product / Creative Discovery and Second-Move Review gates to `cc-plan` so non-trivial plans confirm product value and shape before engineering details.
-- Updated `cc-plan` task templates, planning contract, playbook, and examples with durable slots for product shape, narrowest wedge, better-version thinking, and question-quality review.
+- Added an explicit `cc-act` postmortem trigger gate through `evaluate-postmortem-trigger.sh`.
+- Added `pr-brief.md` postmortem trigger output so closeout records whether an incident postmortem is required.
+
+### Changed
+
+- Updated `cc-act` to require `POSTMORTEM_REQUIRED=yes/no` before declaring closeout complete.
+- Updated project postmortem guidance so session-only rework, reroutes, or tool failures can be passed into the gate with `--trigger`.
+
+## [4.5.16] - 2026-05-17
+
+### Changed
+
+- Updated `cc-plan`, `cc-investigate`, `cc-review`, and `cc-pr-review` to require ASCII branch-chain analysis in their task or review outputs.
+- Added plan and investigation task-template fields that trace upstream sources, deepest affected code or prompt/provider layers, downstream impact, and verification seams.
+- Clarified that ASCII branch-chain connector tokens stay ASCII while labels, findings, evidence, and explanatory text follow the configured output language.
+- Replaced hard-coded English branch-chain templates with shared semantic label tables for English and Chinese outputs.
+- Updated runtime output-policy rendering so `zh-CN` configurations describe the policy in Chinese instead of English-only prose.
+- Added `Output language` metadata to generated roadmap and backlog projections.
 
 ### Removed
 

package/README.md

@@ -181,7 +181,7 @@ CC-DevFlow reads layered YAML config before durable workflow documents are writt
 <repo>/.cc-devflow/config.local.yml
 ```
 
-Precedence is deterministic: defaults < user < project < local < environment < CLI. `output.document_language` is machine-enforced and currently supports `en` and `zh-CN`. Non-standard preferences belong under `agent_preferences`; they guide style but do not override workflow contracts.
+Precedence is deterministic: defaults < user < project < local < environment < CLI. `output.document_language` is machine-enforced and currently supports `en` and `zh-CN`. It controls durable planning, review, and handoff Markdown headings, prose, placeholders, evidence summaries, and PR/body drafts; code, commands, paths, schema keys, API names, and commit type/scope literals stay unchanged. Non-standard preferences belong under `agent_preferences`; they guide style but do not override workflow contracts.
 
 ```yaml
 version: 1

package/README.zh-CN.md

@@ -181,7 +181,7 @@ CC-DevFlow 会在写入 durable workflow 文档前读取分层 YAML 配置：
 <repo>/.cc-devflow/config.local.yml
 ```
 
-优先级固定为：默认值 < 用户 < 项目 < 本地 < 环境变量 < CLI 参数。`output.document_language` 是机器约束，目前支持 `en` 和 `zh-CN`。非标偏好放在 `agent_preferences` 下，只影响表达风格，不覆盖 workflow 契约。
+优先级固定为：默认值 < 用户 < 项目 < 本地 < 环境变量 < CLI 参数。`output.document_language` 是机器约束，目前支持 `en` 和 `zh-CN`。它约束 durable planning、review、handoff Markdown 的标题、正文、占位符、证据说明和 PR/body 草稿；代码、命令、路径、schema key、API 名、commit type/scope 等机器字面量保持原文。非标偏好放在 `agent_preferences` 下，只影响表达风格，不覆盖 workflow 契约。
 
 ```yaml
 version: 1

package/docs/examples/example-bindings.json

@@ -1,17 +1,17 @@
 {
-  "updatedAt": "2026-05-13",
+  "updatedAt": "2026-05-17",
   "skills": {
-    "cc-roadmap": "5.3.0",
+    "cc-roadmap": "5.3.1",
     "cc-next": "1.1.1",
-    "cc-dev": "1.1.2",
-    "cc-plan": "3.10.4",
-    "cc-investigate": "1.6.2",
+    "cc-dev": "1.1.3",
+    "cc-plan": "3.10.7",
+    "cc-investigate": "1.6.5",
     "cc-do": "1.7.2",
-    "cc-review": "2.2.1",
-    "cc-pr-review": "1.1.1",
+    "cc-review": "2.2.3",
+    "cc-pr-review": "1.1.3",
     "cc-pr-land": "1.1.0",
     "cc-check": "1.12.2",
-    "cc-act": "1.9.1",
+    "cc-act": "1.9.3",
     "cc-spec-init": "1.2.0"
   },
   "examples": [

package/docs/examples/full-design-blocked/BACKLOG.md

@@ -5,10 +5,11 @@
 ## Backlog Meta
 
 - Roadmap version: `roadmap.v2`
-- Skill version: `5.3.0`
+- Skill version: `5.3.1`
 - Last synced: `2026-04-19`
 - Current focus stage: `Stage 2`
 - Roadmap state source: `roadmap.json`
+- Output language: en
 
 ## Queue
 
@@ -22,6 +23,16 @@
 - Parallel-ready next wave: -
 - Notes on blockers: verification is blocked until the import contract covers limits, duplicates, billing, and audit consistency
 
+## Project Direction Handoff
+
+- Project direction mode: -
+- Direction mode rationale: -
+- Direction-specific questions selected: -
+- Direction-specific questions skipped: -
+- Direction guardrails applied: -
+- Planning posture: -
+- Evidence maturity: -
+
 ## Ready For Req-Plan
 
 - RM-010:

package/docs/examples/full-design-blocked/README.md

@@ -4,7 +4,7 @@
 
 - Example version: `1.0.0`
 - Last reviewed: `2026-04-17`
-- Bound skills: `cc-roadmap@5.3.0`, `cc-plan@3.10.4`, `cc-do@1.7.2`, `cc-check@1.12.2`
+- Bound skills: `cc-roadmap@5.3.1`, `cc-plan@3.10.7`, `cc-do@1.7.2`, `cc-check@1.12.2`
 
 This example shows a requirement that **looked executable**, but `cc-check` correctly stopped it and sent it back to `cc-plan`.
 

package/docs/examples/full-design-blocked/ROADMAP.md

@@ -3,7 +3,7 @@
 ## Roadmap Meta
 
 - Roadmap version: `roadmap.v2`
-- Skill version: `5.3.0`
+- Skill version: `5.3.1`
 - Status: `active`
 - Last updated: `2026-04-16`
 - Owner / decider: `product-owner`
@@ -60,6 +60,7 @@
 
 ## Implementation Tracking
 - Roadmap state source: `roadmap.json`
+- Output language: en
 
 <!-- roadmap-tracking:start -->
 | RM-ID | Item | Stage | Priority | Primary Capability | Secondary Capabilities | Expected Spec Delta | Depends On | Status | REQ | Progress |
@@ -67,7 +68,6 @@
 | RM-010 | Add CSV bulk invite import for admins | Stage 2 | P1 | cap-bulk-invite-import | cap-workspace-membership | define import semantics before widening current truth | - | Verification blocked | REQ-002 | 80% |
 <!-- roadmap-tracking:end -->
 
-
 ## Technical Architecture
 
 ```mermaid

package/docs/examples/full-design-blocked/changes/REQ-002-bulk-invite-import/task.md

@@ -4,8 +4,9 @@
 
 - Requirement version: `REQ-002.v2`
 - Design version: `design.v2`
-- CC-Plan skill version: `3.10.4`
+- CC-Plan skill version: `3.10.7`
 - Work branch: `REQ/002-bulk-invite-import`
+- Output language: en
 - Source roadmap item: `RM-010`
 - Source roadmap version: `roadmap.v2`
 
@@ -36,6 +37,27 @@
   - Better architecture: later move bulk provisioning into a job-backed import workflow.
   - Selected move: row classification first, then admin surface and audit mapping.
   - Rejected tradeoff: no SCIM, background jobs, or rollback wizard in this requirement.
+- ASCII Branch Chain Analysis:
+  Language rule: connector tokens stay ASCII; node text follows `Output language: en`.
+
+```text
+Requirement Impact Chain
+REQ: deterministic bulk invite row outcomes
+|-- Upstream source: RM-010 + admin import failure cases
+|-- Current code path: src/invite/bulk-import.ts
+|   |-- caller: src/admin/BulkInvitePanel.tsx
+|   |-- data or state: CSV rows, duplicate state, seat-limit state, audit rows
+|   `-- deepest affected layer: row-outcome matrix shared by invite and audit behavior
+|-- Required change: classify each row before executing visible bulk results
+`-- Verification seam: bulk-import and admin panel tests
+
+Business Impact Chain
+OUTCOME: admins can trust mixed CSV import results
+|-- Direct behavior impact: duplicate, invalid, and over-limit rows get stable results
+|-- Downstream impact: audit mapping and visible admin result rendering
+|-- Risk branch: row semantics drift between UI and audit log
+`-- Non-goal branch: SCIM, background jobs, and rollback wizard stay out
+```
 - Read first:
   - `design.md`
   - `src/admin/BulkInvitePanel.tsx`

package/docs/examples/full-design-blocked/roadmap.json

@@ -5,12 +5,17 @@
   },
   "meta": {
     "roadmapVersion": "roadmap.v2",
-    "skillVersion": "5.3.0",
+    "skillVersion": "5.3.1",
     "status": "active",
     "lastUpdated": "2026-04-19",
     "currentFocusStage": "Stage 2"
   },
   "context": {
+    "projectDirectionMode": "",
+    "projectDirectionRationale": "",
+    "directionQuestionsSelected": [],
+    "directionQuestionsSkipped": [],
+    "directionGuardrailsApplied": [],
     "planningPosture": "",
     "evidenceMaturity": "",
     "canonicalTerms": [],
@@ -127,7 +132,7 @@
   },
   "backlogMeta": {
     "roadmapVersion": "roadmap.v2",
-    "skillVersion": "4.4.1",
+    "skillVersion": "5.3.1",
     "currentFocusStage": "Stage 2"
   },
   "dependencyHandoff": {

package/docs/examples/local-handoff/BACKLOG.md

@@ -5,10 +5,11 @@
 ## Backlog Meta
 
 - Roadmap version: `roadmap.v2`
-- Skill version: `5.3.0`
+- Skill version: `5.3.1`
 - Last synced: `2026-04-19`
 - Current focus stage: `Stage 2`
 - Roadmap state source: `roadmap.json`
+- Output language: en
 
 ## Queue
 
@@ -22,6 +23,16 @@
 - Parallel-ready next wave: -
 - Notes on blockers: export work stays local-only until the next maintainer has remote access
 
+## Project Direction Handoff
+
+- Project direction mode: -
+- Direction mode rationale: -
+- Direction-specific questions selected: -
+- Direction-specific questions skipped: -
+- Direction guardrails applied: -
+- Planning posture: -
+- Evidence maturity: -
+
 ## Ready For Req-Plan
 
 - RM-020:

package/docs/examples/local-handoff/README.md

@@ -4,7 +4,7 @@
 
 - Example version: `1.0.0`
 - Last reviewed: `2026-04-17`
-- Bound skills: `cc-roadmap@5.3.0`, `cc-plan@3.10.4`, `cc-do@1.7.2`, `cc-check@1.12.2`, `cc-act@1.9.1`
+- Bound skills: `cc-roadmap@5.3.1`, `cc-plan@3.10.7`, `cc-do@1.7.2`, `cc-check@1.12.2`, `cc-act@1.9.3`
 
 This example shows verified work that is **ready to move forward**, but `cc-act` still chooses `local-handoff`.
 

package/docs/examples/local-handoff/ROADMAP.md

@@ -3,7 +3,7 @@
 ## Roadmap Meta
 
 - Roadmap version: `roadmap.v3`
-- Skill version: `5.3.0`
+- Skill version: `5.3.1`
 - Status: `active`
 - Last updated: `2026-04-16`
 - Owner / decider: `product-owner`
@@ -52,6 +52,7 @@
 
 ## Implementation Tracking
 - Roadmap state source: `roadmap.json`
+- Output language: en
 
 <!-- roadmap-tracking:start -->
 | RM-ID | Item | Stage | Priority | Primary Capability | Secondary Capabilities | Expected Spec Delta | Depends On | Status | REQ | Progress |
@@ -59,7 +60,6 @@
 | RM-020 | Add an audit-log export summary download | Stage 2 | P1 | cap-audit-log-export | - | codify local export summary truth | - | Local handoff | REQ-003 | 100% |
 <!-- roadmap-tracking:end -->
 
-
 ## Technical Architecture
 
 ```mermaid

package/docs/examples/local-handoff/changes/REQ-003-audit-log-export/task.md

@@ -4,8 +4,9 @@
 
 - Requirement version: `REQ-003.v1`
 - Design version: `design.v1`
-- CC-Plan skill version: `3.10.4`
+- CC-Plan skill version: `3.10.7`
 - Work branch: `REQ/003-audit-log-export`
+- Output language: en
 - Source roadmap item: `RM-020`
 - Source roadmap version: `roadmap.v3`
 
@@ -36,6 +37,27 @@
   - Better architecture: later introduce a reporting backend for scheduled exports.
   - Selected move: visible-row CSV download from the existing panel.
   - Rejected tradeoff: no JSON export, scheduling, or shared reporting backend here.
+- ASCII Branch Chain Analysis:
+  Language rule: connector tokens stay ASCII; node text follows `Output language: en`.
+
+```text
+Requirement Impact Chain
+REQ: CSV export for visible audit summary rows
+|-- Upstream source: RM-020 + weekly admin reporting workflow
+|-- Current code path: src/admin/AuditSummaryPanel.tsx
+|   |-- caller: admin audit summary panel action
+|   |-- data or state: visible summary rows
+|   `-- deepest affected layer: browser download/blob boundary for CSV output
+|-- Required change: export visible rows without adding reporting storage
+`-- Verification seam: src/admin/AuditSummaryPanel.test.tsx
+
+Business Impact Chain
+OUTCOME: admins stop manually copying weekly audit summaries
+|-- Direct behavior impact: visible rows become a downloadable CSV
+|-- Downstream impact: local handoff documents proof for CSV-only export
+|-- Risk branch: exported rows diverge from visible panel state
+`-- Non-goal branch: JSON export, scheduled reporting, and backend history stay out
+```
 - Read first:
   - `design.md`
   - `src/admin/AuditSummaryPanel.tsx`

package/docs/examples/local-handoff/roadmap.json

@@ -5,12 +5,17 @@
   },
   "meta": {
     "roadmapVersion": "roadmap.v2",
-    "skillVersion": "5.3.0",
+    "skillVersion": "5.3.1",
     "status": "active",
     "lastUpdated": "2026-04-19",
     "currentFocusStage": "Stage 2"
   },
   "context": {
+    "projectDirectionMode": "",
+    "projectDirectionRationale": "",
+    "directionQuestionsSelected": [],
+    "directionQuestionsSkipped": [],
+    "directionGuardrailsApplied": [],
     "planningPosture": "",
     "evidenceMaturity": "",
     "canonicalTerms": [],
@@ -123,7 +128,7 @@
   },
   "backlogMeta": {
     "roadmapVersion": "roadmap.v2",
-    "skillVersion": "4.4.1",
+    "skillVersion": "5.3.1",
     "currentFocusStage": "Stage 2"
   },
   "dependencyHandoff": {

package/docs/examples/pdca-loop/BACKLOG.md

@@ -5,10 +5,11 @@
 ## Backlog Meta
 
 - Roadmap version: `roadmap.v1`
-- Skill version: `5.3.0`
+- Skill version: `5.3.1`
 - Last synced: `2026-04-19`
 - Current focus stage: `Stage 1`
 - Roadmap state source: `roadmap.json`
+- Output language: en
 
 ## Queue
 
@@ -23,6 +24,16 @@
 - Parallel-ready next wave: none until RM-001 proves the copy action shape
 - Notes on blockers: RM-002 should reuse the final interaction contract from RM-001, not race it
 
+## Project Direction Handoff
+
+- Project direction mode: -
+- Direction mode rationale: -
+- Direction-specific questions selected: -
+- Direction-specific questions skipped: -
+- Direction guardrails applied: -
+- Planning posture: -
+- Evidence maturity: -
+
 ## Ready For Req-Plan
 
 - RM-001:

package/docs/examples/pdca-loop/README.md

@@ -4,7 +4,7 @@
 
 - Example version: `1.0.0`
 - Last reviewed: `2026-04-17`
-- Bound skills: `cc-roadmap@5.3.0`, `cc-plan@3.10.4`, `cc-do@1.7.2`, `cc-check@1.12.2`, `cc-act@1.9.1`
+- Bound skills: `cc-roadmap@5.3.1`, `cc-plan@3.10.7`, `cc-do@1.7.2`, `cc-check@1.12.2`, `cc-act@1.9.3`
 
 This folder shows one minimal but complete `cc-roadmap -> cc-plan -> cc-do -> cc-check -> cc-act` loop.
 

package/docs/examples/pdca-loop/ROADMAP.md

@@ -3,7 +3,7 @@
 ## Roadmap Meta
 
 - Roadmap version: `roadmap.v1`
-- Skill version: `5.3.0`
+- Skill version: `5.3.1`
 - Status: `active`
 - Last updated: `2026-04-15`
 - Owner / decider: `product-owner`
@@ -138,6 +138,7 @@
 
 ## Implementation Tracking
 - Roadmap state source: `roadmap.json`
+- Output language: en
 
 <!-- roadmap-tracking:start -->
 | RM-ID | Item | Stage | Priority | Primary Capability | Secondary Capabilities | Expected Spec Delta | Depends On | Status | REQ | Progress |
@@ -147,7 +148,6 @@
 | RM-004 | Collaboration analytics follow-up | - | - | - | - | - | - | - | - | - |
 <!-- roadmap-tracking:end -->
 
-
 ## Technical Architecture
 
 ```mermaid

package/docs/examples/pdca-loop/changes/REQ-001-copy-invite-link/task.md

@@ -4,8 +4,9 @@
 
 - Requirement version: `REQ-001.v1`
 - Design version: `design.v1`
-- CC-Plan skill version: `3.10.4`
+- CC-Plan skill version: `3.10.7`
 - Work branch: `REQ/001-copy-invite-link`
+- Output language: en
 - Source roadmap item: `RM-001`
 - Source roadmap version: `roadmap.v1`
 
@@ -37,6 +38,27 @@
   - Better architecture: centralize all share actions behind a richer share command model later.
   - Selected move: same-dialog copy action with minimal copied-state confirmation.
   - Rejected tradeoff: no broader share-service redesign in this bounded requirement.
+- ASCII Branch Chain Analysis:
+  Language rule: connector tokens stay ASCII; node text follows `Output language: en`.
+
+```text
+Requirement Impact Chain
+REQ: one-click copy for the visible invite URL
+|-- Upstream source: RM-001 + share dialog user story
+|-- Current code path: src/features/share/ShareDialog.tsx
+|   |-- caller: share dialog render flow
+|   |-- data or state: existing invite URL prop + copied confirmation state
+|   `-- deepest affected layer: clipboard boundary in the dialog behavior
+|-- Required change: add copy action without changing share-service contracts
+`-- Verification seam: src/features/share/ShareDialog.test.tsx
+
+Business Impact Chain
+OUTCOME: users can share invites without manual text selection
+|-- Direct behavior impact: visible invite URL copies from the dialog
+|-- Downstream impact: tests and PR brief document the bounded copy behavior
+|-- Risk branch: clipboard boundary failure or stale copied-state feedback
+`-- Non-goal branch: invite generation, analytics, and fallback redesign stay out
+```
 - Read first:
   - `design.md`
   - `src/features/share/ShareDialog.tsx`

package/docs/examples/pdca-loop/roadmap.json

@@ -5,12 +5,17 @@
   },
   "meta": {
     "roadmapVersion": "roadmap.v1",
-    "skillVersion": "5.3.0",
+    "skillVersion": "5.3.1",
     "status": "active",
     "lastUpdated": "2026-04-19",
     "currentFocusStage": "Stage 1"
   },
   "context": {
+    "projectDirectionMode": "",
+    "projectDirectionRationale": "",
+    "directionQuestionsSelected": [],
+    "directionQuestionsSkipped": [],
+    "directionGuardrailsApplied": [],
     "planningPosture": "",
     "evidenceMaturity": "",
     "canonicalTerms": [],
@@ -193,7 +198,7 @@
   },
   "backlogMeta": {
     "roadmapVersion": "roadmap.v1",
-    "skillVersion": "4.4.1",
+    "skillVersion": "5.3.1",
     "currentFocusStage": "Stage 1"
   },
   "dependencyHandoff": {

package/docs/guides/project-postmortem.md

@@ -13,6 +13,14 @@ Postmortems preserve recurring failures without turning every workflow step into
 - repeated AI, test, release, Git, or architecture failure
 - explicit user request
 
+`cc-act` must make the decision explicit by running:
+
+```bash
+.claude/skills/cc-act/scripts/evaluate-postmortem-trigger.sh --dir devflow/changes/<change-key>
+```
+
+If the trigger only exists in the current session, pass it as `--trigger <short-label>` so the final closeout does not silently drop rework or unusual failure evidence.
+
 ## Rules
 
 - Use Git evidence, commands, and current files.