cc-devflow 4.5.14 → 4.5.16

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,6 +9,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+_No unreleased changes._
+
+## [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
+
+- Removed the `cc-devflow query` runtime surface and the `workflow-context` query.
+- Removed workflow-context stage-transition requirements from distributed skills; stages now start from `task.md`, Git, and PR or handoff reality.
+
 ## [4.5.14] - 2026-05-14
 
 ### Changed

package/README.md

@@ -118,7 +118,7 @@ Canonical language and durable decisions stay inside cc-devflow-native sources:
 
 `cc-plan` freezes more implementation decisions before `cc-do` starts. Non-trivial plans compare minimal viable and ideal architecture options, full designs include decision horizon plus error/rescue mapping, and test-first plans record test framework evidence, public test seams, spec-style test names, public verification paths, behavior assertions, mock boundaries, coverage quality, mandatory regression tests, interface depth, Green minimality guards, refactor candidates, and vertical tracer-bullet slices when existing behavior changes. Before handoff, `cc-plan` and `cc-investigate` also reconcile the source roadmap item so RM status, REQ/FIX binding, progress, and spec diagnosis do not drift from the frozen change artifacts.
 
-Every post-planning stage can start from `cc-devflow query workflow-context --change <id> --change-key <key> --data-only --no-trace --compact`. Treat the result as a context index, not semantic compression: it routes the next stage from `task.md`, Git history, and PR/handoff truth. Source artifacts still decide disputed facts. Use `npm run benchmark:skills` to keep public skill entrypoints thin; deeper planning rules should live behind conditional references instead of default context.
+Every post-planning stage starts from `task.md`, current Git history/status, and PR or handoff truth when present. There is no runtime context query layer; disputed facts must be re-read from source artifacts. Use `npm run benchmark:skills` to keep public skill entrypoints thin; deeper planning rules should live behind conditional references instead of default context.
 
 `cc-review` is optional and deeper than `cc-check`. It can run immediately after `cc-plan` / `cc-investigate` to review the frozen plan or root-cause contract, or after `cc-do` to review the implementation. Plan and investigation review findings are written directly into `task.md`. Implementation review findings are returned in the response with repair options; the user chooses the repair path before code is edited. PR reviews stay in the response or GitHub review. No local review report, ledger, findings JSON, or other review output file is written.
 
@@ -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
@@ -247,14 +247,13 @@ The currently distributed skill folders are:
 - `devflow/changes/<change>/` stores durable change truth in `task.md`, optional `handoff/pr-brief.md`, and Git commits. Real recurring failures may also write incident postmortems under `devflow/postmortems/`.
 - New changes default to one human-authored Markdown artifact: `task.md`. Feature plans put the frozen design in `## Contract Summary`; bug investigations put root-cause truth in `## Root Cause Contract`. Legacy planning and review artifacts are readable fallback inputs only.
 - Workflow state is Git-owned: keep `task.md` current, commit each completed stage/environment, and do not create extra process files.
-- Use `cc-devflow query workflow-context`, `npm run verify:examples`, and `npm run benchmark:skills` to keep workflow truth and skill entrypoints small and measurable.
+- Use `npm run verify:examples` and `npm run benchmark:skills` to keep workflow truth and skill entrypoints small and measurable.
 - `devflow/workspaces/<change>/` stores ephemeral runtime scratch such as worker assignment, journals, prompts, and session logs.
 - Regenerable files should not be persisted under `devflow/changes/`.
 
 Artifact contract quick checks:
 
 ```bash
-npx cc-devflow query workflow-context --change REQ-001 --change-key REQ-001-copy-invite-link --data-only --no-trace --compact
 npm run verify:examples
 npm run benchmark:skills
 ```

package/README.zh-CN.md

@@ -118,7 +118,7 @@ Canonical language 和 durable decisions 只收敛到 cc-devflow 原生真相源
 
 `cc-plan` 会在 `cc-do` 开始前冻结更多实现决策。非 trivial 计划需要比较 minimal viable 和 ideal architecture，full-design 需要包含 implementation decision horizon 和 error/rescue map；测试计划要记录测试框架证据、public test seam、spec-style test name、public verification path、behavior assertion、mock boundary、覆盖质量、强制 regression test、interface depth、Green minimality guard、refactor candidates 和 vertical tracer-bullet slices。交接前，`cc-plan` 和 `cc-investigate` 还会校准 source roadmap item，让 RM 状态、REQ/FIX 绑定、progress 和 spec diagnosis 不再漂移。
 
-planning 之后的每个阶段都可以先运行 `cc-devflow query workflow-context --change <id> --change-key <key> --data-only --no-trace --compact`。把结果当成 context index，而不是语义压缩：它从 `task.md`、Git history 和 PR/handoff truth 路由下一阶段；有争议的事实仍由源 artifact 裁决。用 `npm run benchmark:skills` 保持 public skill 入口足够薄；深层规划规则应该放在条件 reference 后面，而不是默认上下文里。
+planning 之后的每个阶段都从 `task.md`、当前 Git history/status，以及存在时的 PR 或 handoff truth 开始。系统不再提供 runtime context query 层；有争议的事实必须回到源 artifact 重新读取。用 `npm run benchmark:skills` 保持 public skill 入口足够薄；深层规划规则应该放在条件 reference 后面，而不是默认上下文里。
 
 `cc-review` 是可选的深度 Review，不替代 `cc-check`。它可以接在 `cc-plan` / `cc-investigate` 后审冻结的计划或根因合同，也可以接在 `cc-do` 后审实现。计划 / 调查 Review 的 finding 直接写进 `task.md`。执行 Review 的 finding 在当前回复里组织成修复选项，用户选择后才改代码。PR Review 只留在对话或 GitHub review 中。不写本地 review report、ledger、findings JSON 或其它 Review 产物文件。
 
@@ -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
@@ -247,14 +247,13 @@ npx cc-devflow config doctor --cwd /path/to/your/project
 - `devflow/changes/<change>/` 的 durable change truth 只保留 `task.md`、可选 `handoff/pr-brief.md` 和 Git commits。真实复发故障可以在 `devflow/postmortems/` 写 incident postmortem。
 - 新 change 默认只有一个人工编写的 Markdown artifact：`task.md`。功能计划把冻结设计写进 `## Contract Summary`；Bug 调查把根因真相写进 `## Root Cause Contract`。历史 planning / review artifacts 只作为可读 fallback 输入。
 - 流程状态归 Git：保持 `task.md` 当前，每个完成阶段 / 执行环境提交 commit，不创建额外过程文件。
-- 用 `cc-devflow query workflow-context`、`npm run verify:examples` 和 `npm run benchmark:skills` 保持 workflow truth 与 skill 入口小而可测。
+- 用 `npm run verify:examples` 和 `npm run benchmark:skills` 保持 workflow truth 与 skill 入口小而可测。
 - `devflow/workspaces/<change>/` 保存 ephemeral runtime scratch，例如 worker assignment、journal、prompt 和 session log。
 - 能从 durable truth 再生成的文件，不应该持久化到 `devflow/changes/`。
 
 Artifact contract 快速检查：
 
 ```bash
-npx cc-devflow query workflow-context --change REQ-001 --change-key REQ-001-copy-invite-link --data-only --no-trace --compact
 npm run verify:examples
 npm run benchmark:skills
 ```

package/bin/cc-devflow-cli.js

@@ -14,10 +14,6 @@ const {
   setConfigValue,
   writeConfigTemplate
 } = require(path.join(PACKAGE_ROOT, 'lib/skill-runtime/config.js'));
-const {
-  listQueryIds,
-  runQuery
-} = require(path.join(PACKAGE_ROOT, 'lib/skill-runtime/query.js'));
 const ADAPT_BIN = path.join(PACKAGE_ROOT, 'bin', 'adapt.js');
 const ADAPTER_BIN = path.join(PACKAGE_ROOT, 'bin', 'cc-devflow.js');
 const TEMPLATE_IGNORES = new Set(['.DS_Store', 'tsc-cache']);
@@ -58,8 +54,6 @@ Commands:
   config set          Set one project/user/local config value
   config resolve      Print resolved YAML config with key-level trace
   config doctor       Validate config and local ignore safety
-  query list          List typed runtime query ids
-  query <id>          Run a typed runtime query as JSON
   next-change-key     Compute the next REQ/FIX change key
   archive-change      Archive a completed change to devflow/changes/archive/YYYY-MM/
   restore-change      Restore an archived change back to devflow/changes/
@@ -89,15 +83,6 @@ Config options:
   --trace              Include key-level source trace with policy output
   --force              Overwrite an existing config template
 
-Query options:
-  --cwd <path>         Project path used for devflow artifact lookup
-  --change <id>        Change id, for example REQ-123
-  --change-id <id>     Alias for --change
-  --change-key <key>   Full change key, for example REQ-123-my-feature
-  --data-only          Print only the query data payload when the query succeeds
-  --no-trace           Omit trace metadata from the JSON output
-  --compact            Print minified JSON instead of pretty JSON
-
 Next-change-key options:
   --prefix <REQ|FIX>   Change type prefix (required)
   --description <text> Short description, will be slugified (required)
@@ -112,8 +97,6 @@ Examples:
   cc-devflow config set output.document_language zh-CN --cwd /path/to/project --project
   cc-devflow config set output.document_language zh-CN --user
   cc-devflow config resolve --cwd /path/to/project --format policy
-  cc-devflow query list
-  cc-devflow query workflow-context --cwd /path/to/project --change REQ-123 --change-key REQ-123-my-feature --data-only --no-trace --compact
 `);
 }
 
@@ -478,82 +461,6 @@ function runConfig(args) {
   return 0;
 }
 
-function parseChangeScopedArgs(args, options = {}) {
-  const { allowQueryFlags = false } = options;
-  const parsed = {
-    cwd: null,
-    changeId: null,
-    changeKey: null,
-    compact: false,
-    dataOnly: false,
-    noTrace: false,
-    rest: []
-  };
-
-  for (let i = 0; i < args.length; i++) {
-    const arg = args[i];
-
-    if (arg === '--cwd') { parsed.cwd = args[++i]; continue; }
-    if (arg.startsWith('--cwd=')) { parsed.cwd = arg.slice('--cwd='.length); continue; }
-    if (arg === '--change' || arg === '--change-id') { parsed.changeId = args[++i]; continue; }
-    if (arg.startsWith('--change=')) { parsed.changeId = arg.slice('--change='.length); continue; }
-    if (arg.startsWith('--change-id=')) { parsed.changeId = arg.slice('--change-id='.length); continue; }
-    if (arg === '--change-key') { parsed.changeKey = args[++i]; continue; }
-    if (arg.startsWith('--change-key=')) { parsed.changeKey = arg.slice('--change-key='.length); continue; }
-    if (allowQueryFlags && arg === '--compact') { parsed.compact = true; continue; }
-    if (allowQueryFlags && arg === '--data-only') { parsed.dataOnly = true; continue; }
-    if (allowQueryFlags && arg === '--no-trace') { parsed.noTrace = true; continue; }
-
-    parsed.rest.push(arg);
-  }
-
-  return parsed;
-}
-
-function formatQueryResult(result, options) {
-  let output = result;
-
-  if (options.dataOnly && result.ok) {
-    output = result.data;
-  } else if (options.noTrace && output && typeof output === 'object') {
-    const { trace, ...withoutTrace } = output;
-    output = withoutTrace;
-  }
-
-  return options.compact
-    ? JSON.stringify(output)
-    : JSON.stringify(output, null, 2);
-}
-
-async function runQueryCommand(args) {
-  const [subcommand, ...rest] = args;
-
-  if (!subcommand || subcommand === '--help' || subcommand === '-h') {
-    console.error('Use: cc-devflow query list OR cc-devflow query <id> --change <changeId> [--change-key <key>] [--cwd <path>]');
-    return 3;
-  }
-
-  if (subcommand === 'list') {
-    process.stdout.write(`${listQueryIds().join('\n')}\n`);
-    return 0;
-  }
-
-  const options = parseChangeScopedArgs(rest, { allowQueryFlags: true });
-  if (!options.changeId) {
-    console.error('Query --change is required.');
-    return 3;
-  }
-
-  const result = await runQuery(subcommand, {
-    repoRoot: path.resolve(options.cwd || process.cwd()),
-    changeId: options.changeId,
-    changeKey: options.changeKey
-  });
-
-  process.stdout.write(`${formatQueryResult(result, options)}\n`);
-  return result.ok ? 0 : 2;
-}
-
 function runNextChangeKey(args) {
   const parsed = { prefix: null, description: null, cwd: null };
 
@@ -700,6 +607,12 @@ async function main() {
     return 0;
   }
 
+  if (command.startsWith('-')) {
+    console.error(`Unknown top-level option: ${command}`);
+    console.error('Use: cc-devflow <command> [options]');
+    return 3;
+  }
+
   if (command === 'init') {
     return runInit(rest);
   }
@@ -713,7 +626,8 @@ async function main() {
   }
 
   if (command === 'query') {
-    return runQueryCommand(rest);
+    console.error('cc-devflow query has been removed. Read task.md, Git history/status, and PR or handoff truth directly.');
+    return 3;
   }
 
   if (command === 'next-change-key') {

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.2",
-    "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.2",
     "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.2`, `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.2`
+- 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`
 
@@ -24,6 +25,39 @@
   - Testing decisions: test bulk-import rules, admin upload flow, and audit mapping
   - Out of scope: SCIM provisioning, background jobs, rollback wizard
 - AI Leverage Decision Lens: sharp-wedge; AI can implement this bounded import path fast, but cc-check may still block final proof if row semantics drift
+- Product / Creative Discovery:
+  - Worth doing: admins cannot trust bulk invite outcomes when duplicates, invalid rows, and seat limits mix together.
+  - Desired product shape: every uploaded row gets a predictable visible result before downstream audit behavior matters.
+  - Narrowest wedge: deterministic row classification for the known CSV invite path.
+  - 10x / better version: full provisioning workflow with retry, rollback, and background processing, deferred outside this requirement.
+  - Do-nothing consequence: admins keep reconciling failed imports manually and audit logs remain hard to trust.
+- Second-Move Review:
+  - First good move: implement mixed CSV result rendering directly in the admin panel.
+  - Simpler move: freeze the row-outcome matrix first and reuse the existing invite engine.
+  - 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`
@@ -43,8 +77,8 @@
 ClaudeCode / Codex 执行本计划时，必须把本文件当成任务模板合同，而不是普通 TODO 列表。
 
 - Template source: `assets/TASKS_TEMPLATE.md`
-- CLI resolver: all workflow commands must run through `.claude/skills/cc-dev/scripts/resolve-cc-devflow.sh` or `.codex/skills/cc-dev/scripts/resolve-cc-devflow.sh`; if it cannot prove `query workflow-context` and `next-change-key`, stop blocked.
-- Context first: run resolved CLI `query workflow-context --change <changeId> --change-key <changeKey> --cwd <repo-root> --data-only --no-trace --compact` before opening deep sections.
+- CLI resolver: all workflow commands must run through `.claude/skills/cc-dev/scripts/resolve-cc-devflow.sh` or `.codex/skills/cc-dev/scripts/resolve-cc-devflow.sh`; if it cannot prove `next-change-key`, stop blocked.
+- Context first: read this `task.md`, current Git status/history, and PR or handoff truth when present before opening deep sections.
 - Task selection: use `scripts/select-ready-tasks.sh --tasks devflow/changes/<change-key>/task.md`.
 - Task block rule: read the full task block before coding; title-only execution is invalid.
 - Completion rule: after verification and review gates pass, run `scripts/mark-task-complete.sh --tasks devflow/changes/<change-key>/task.md --task <task-id>`.
@@ -55,8 +89,8 @@ DEVFLOW=".claude/skills/cc-dev/scripts/resolve-cc-devflow.sh"
 if [[ ! -f "$DEVFLOW" && -f ".codex/skills/cc-dev/scripts/resolve-cc-devflow.sh" ]]; then
   DEVFLOW=".codex/skills/cc-dev/scripts/resolve-cc-devflow.sh"
 fi
-bash "$DEVFLOW" require query workflow-context next-change-key
-bash "$DEVFLOW" query workflow-context --change <changeId> --change-key <changeKey> --cwd <repo-root> --data-only --no-trace --compactSCRIPT_ROOT=".claude/skills/cc-do/scripts"
+bash "$DEVFLOW" require next-change-key
+SCRIPT_ROOT=".claude/skills/cc-do/scripts"
 if [[ ! -d "$SCRIPT_ROOT" && -d ".codex/skills/cc-do/scripts" ]]; then
   SCRIPT_ROOT=".codex/skills/cc-do/scripts"
 fi

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.2`, `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.2`
 
 This example shows verified work that is **ready to move forward**, but `cc-act` still chooses `local-handoff`.