qfai 1.5.1 → 1.5.3

package/README.md

@@ -246,7 +246,7 @@ flowchart LR
 - Contracts SSOT: `.qfai/contracts/**`
 - Report outputs (`.qfai/report/**`) are derived artifacts and not SSOT.
 
-## Minimal tutorial (v1.5.1)
+## Minimal tutorial (v1.5.3)
 
 1. `npx qfai init`
 2. Run `/qfai-discussion` to structure scope, open questions, and produce a discussion pack under `.qfai/discussion/discussion-<ts>/`.
@@ -340,10 +340,14 @@ Typical customizations.
 │   │   │   ├── qfai-configure
 │   │   │   │   └── SKILL.md
 │   │   │   ├── qfai-discussion
+│   │   │   │   ├── references
+│   │   │   │   │   └── rcp_footer.md
 │   │   │   │   └── SKILL.md
 │   │   │   ├── qfai-prototyping
 │   │   │   │   └── SKILL.md
 │   │   │   ├── qfai-sdd
+│   │   │   │   ├── references
+│   │   │   │   │   └── rcp_footer.md
 │   │   │   │   └── SKILL.md
 │   │   │   ├── qfai-atdd
 │   │   │   │   └── SKILL.md
@@ -357,8 +361,6 @@ Typical customizations.
 │   │   │       └── SKILL.md
 │   │   ├── skills.local
 │   │   │   └── README.md
-│   │   ├── templates
-│   │   │   └── rcp_footer.md
 │   │   ├── steering
 │   │   │   ├── README.md
 │   │   │   ├── review-gate.rules.yml

package/assets/init/.qfai/README.md

@@ -98,7 +98,8 @@ It is useful for local review but should not pollute version control.
 
 ### R4. Layered specs are runtime SSOT
 
-- Runtime validators and downstream skills consume `_shared/**` and `spec-XXXX/**`.
+- Runtime validators consume `_policies/**` and `spec-XXXX/**`.
+- Execution skills enter from `spec-XXXX/01_Spec.md` and read `_policies/**` only through the spec's Escalation Hook.
 - Split rule is fixed: `1 CAP = 1 spec`.
 - Parent chain is fixed: `US -> CAP`, `AC -> US`, `BR -> AC`, `EX -> BR|AC`, `TC -> EX`.
 - Derived outputs under `.qfai/report/**` are non-SSOT.

package/assets/init/.qfai/assistant/agents/prototyping-coverage-auditor.md

@@ -9,7 +9,7 @@
 - `.qfai/assistant/instructions/*`
 - `.qfai/assistant/steering/*`
 - `.qfai/specs/spec-*`
-- `.qfai/specs/_shared/05_Contracts.md`
+- `.qfai/specs/_policies/05_Contracts.md`
 - prototyping markdown evidence artifact in the evidence directory
 - prototyping json evidence artifact in the evidence directory
 

package/assets/init/.qfai/assistant/instructions/drift-protocol.md

@@ -9,7 +9,7 @@ This file defines mandatory change control for all downstream execution phases.
 Upstream artifacts include, at minimum:
 
 - `01_Spec.md`, `02_User-stories.md`, `03_Acceptance-Criteria.md`, `04_Business-Rules.md`, `05_Examples.md`, `06_Test-Cases.md`, `07_Decisions.md`, `08_Open-questions.md`, `09_delta.md`
-- `_shared/*` layered artifacts and `11_Contracts.md` (or project-equivalent contract index)
+- `_policies/*` layered artifacts and `11_Contracts.md` (or project-equivalent contract index)
 - `10_Plan.md` and other owner-phase planning outputs
 - Legacy spec-pack SSOT files when present: `spec.md`, `delta.md`, `plan.md`, `traceability-matrix.md`, `scenario.feature`, `case-catalogue.md`, and numbered pack files (for example `01_Spec.md`..`18_delta.md`)
 - contracts and schema decisions owned by earlier phases

package/assets/init/.qfai/assistant/instructions/requirements-decomposition.md

@@ -15,7 +15,7 @@ This document is the decision rule SSOT for AI and humans when answering:
 1. **Source registry** (`require/require-*/01_Sources.md`)
 2. **Requirement index** (`require/require-*/03_REQ.md`)
 3. **Input gaps / Open Questions** (`require/require-*/08_OQ.md`)
-4. **Shared specs** (`specs/_shared/01..04`)
+4. **Policy layer** (`specs/_policies/01..04`)
 5. **Capability slices** (`specs/spec-*/01..05` minimum)
 6. **ATDD / TDD** (tests + code)
 
@@ -35,21 +35,21 @@ This document is the decision rule SSOT for AI and humans when answering:
 ### Rule 3 - Keep ambiguity explicit
 
 - Unknowns remain explicit as Open Questions.
-- Resolved answers are promoted to `_shared` or `spec-XXXX` artifacts, then OQ status is updated.
+- Resolved answers are promoted to `_policies` or `spec-XXXX` artifacts, then OQ status is updated.
 
 ## How to decompose (mechanical procedure)
 
 1. Register source documents and assumptions in `require-*/01_Sources.md`.
 2. Extract concise requirement index entries in `require-*/03_REQ.md`.
 3. Capture missing information in `require-*/08_OQ.md`.
-4. Build `_shared` layer (`Objective`, `Initiative`, `Capabilities`, `Business Flow`).
+4. Build `_policies` layer (`Objective`, `Initiative`, `Capabilities`, `Business Flow`).
 5. Split by capability (`1 CAP = 1 spec-XXXX`) and produce slice files.
 6. Derive acceptance tests and implementation from the finalized slices.
 
 ## Example
 
 - Requirement index entry: `REQ-0003` linked to `SRC-0002`
-- Capability mapping: `CAP-0003` in `_shared/03_Capabilities.md`
+- Capability mapping: `CAP-0003` in `_policies/03_Capabilities.md`
 - Spec slice: `spec-0003/01_Spec.md` through `06_Test-Cases.md`
 
 ## Non-goals

package/assets/init/.qfai/assistant/instructions/workflow.md

@@ -49,7 +49,7 @@ Do not proceed without a declared Change Type.
 0. Steering refresh (project memory bootstrap)
 1. Discussion (optional): clarify idea → requirement seed
 2. Requirements: requirements document in `.qfai/require/`
-3. Specification (SDD): unified preflight + `_shared` / `spec-XXXX/01..10`
+3. Specification (SDD): unified preflight + `_policies` / `spec-XXXX/01..10`
 4. Prototyping (optional): contract-aligned implementation skeleton
 5. Acceptance tests (ATDD): runnable E2E/API/Integration tests derived from specs/contracts obligations (`US` / `TC` / `CON-API`)
 6. Verify: run quality gates and provide evidence
@@ -57,7 +57,7 @@ Do not proceed without a declared Change Type.
 Stage 3 (`/qfai-sdd`) target policy:
 
 - With argument (`/qfai-sdd <spec-id-or-name>`): scope is the matched single spec only.
-- Without argument (`/qfai-sdd`): scope is all capabilities from `.qfai/specs/_shared/03_Capabilities.md` in order.
+- Without argument (`/qfai-sdd`): scope is all capabilities from `.qfai/specs/_policies/03_Capabilities.md` in order.
 - For no-argument batch runs, execute Contracts-first and Outline once, then delegate Slice/Plan/Delta in parallel per `spec-XXXX`.
 
 Prototyping stage policy:

package/assets/init/.qfai/assistant/skills/qfai-atdd/SKILL.md

@@ -33,15 +33,30 @@ When unsure, read inputs in this order:
 
 - P1: `.qfai/assistant/instructions/*`
 - P2: `.qfai/assistant/steering/*`
-- P3: `.qfai/specs/<spec-id>/09_delta.md` (Decision Records; if no spec yet, state "not applicable")
+- P3: `.qfai/specs/<spec-id>/01_Spec.md` (Primary SSOT / Consumer View)
 - P4: specs/contracts obligations
   - `.qfai/specs/<spec-id>/02_User-stories.md` (US)
+  - `.qfai/specs/<spec-id>/03_Acceptance-Criteria.md` (AC)
+  - `.qfai/specs/<spec-id>/05_Examples.md` (EX)
   - `.qfai/specs/<spec-id>/06_Test-Cases.md` (TC)
   - `.qfai/contracts/api/**` (CON-API)
-- P5: legacy artifacts (optional only)
+- P5: `.qfai/specs/<spec-id>/09_delta.md` (Decision Records; if no spec yet, state "not applicable")
+- P6: legacy artifacts (optional only)
   - `.qfai/specs/<spec-id>/scenario.feature`
   - coverage ledger files
 
+## Read Set Contract (Mandatory)
+
+- Default Mode:
+  - `.qfai/specs/<spec-id>/01_Spec.md`
+  - `.qfai/specs/<spec-id>/03_Acceptance-Criteria.md`
+  - `.qfai/specs/<spec-id>/05_Examples.md`
+  - `.qfai/specs/<spec-id>/06_Test-Cases.md`
+- Escalation Mode:
+  - allowed only when `01_Spec.md` Escalation Hook signals ambiguity / conflict / missing constraint / trade-off
+  - read only `.qfai/specs/_policies/01_Objective.md` and `.qfai/specs/_policies/08_Decisions.md`
+- Do not read `_policies/**` by default.
+
 ## Sub-agent Delegation (MANDATORY)
 
 This section is mandatory and overrides any conflicting fallback text in this file.

package/assets/init/.qfai/assistant/skills/qfai-discussion/SKILL.md

@@ -28,7 +28,7 @@ mode: interactive-by-default
   - `.qfai/specs/README.md`
   - `.qfai/evidence/README.md`
   - `.qfai/assistant/steering/review-roster.yml`
-  - `.qfai/assistant/templates/rcp_footer.md`
+  - `.qfai/assistant/skills/qfai-discussion/references/rcp_footer.md`
 - Keep templates as source of truth and preserve file naming/order.
 
 ## Sub-agent Delegation (MANDATORY)
@@ -93,7 +93,7 @@ Every major artifact in this stage MUST include this table schema:
 - `03_Story-Workshop.md` MUST contain at least one Mermaid diagram in ` ```mermaid ` fences.
 - If UI requirements exist, include an HTML+CSS visual mock in `03_Story-Workshop.md`.
 - Review roster is fixed by `.qfai/assistant/steering/review-roster.yml` and must be executed in full.
-- RCP wording must be sourced from `.qfai/assistant/templates/rcp_footer.md`.
+- RCP wording must be sourced from `.qfai/assistant/skills/qfai-discussion/references/rcp_footer.md`.
 - Discussion artifacts are logs/rationale and must not duplicate spec SSOT.
 - If diagrams are written, Mermaid syntax must be in ` ```mermaid ` fences only.
 - Do not enforce fixed EX/BR or TC/EX ratios in this phase.
@@ -220,14 +220,14 @@ For each review cycle, create:
 RCP rules:
 
 - Append-only: create a new review pack for each cycle.
-- Apply `.qfai/assistant/templates/rcp_footer.md` as the common footer rule set.
+- Apply `.qfai/assistant/skills/qfai-discussion/references/rcp_footer.md` as the common footer rule set.
 - Any `FAIL` requires return/fix/full rerun from the first reviewer.
 - Mark fixed only when all reviewers are `PASS` or valid `N/A`.
 - `summary.json` `target.kind` must be `"discussion"`.
 
 ## RCP Footer Include (MUST)
 
-- Include and follow `.qfai/assistant/templates/rcp_footer.md` without rewriting it per skill.
+- Include and follow `.qfai/assistant/skills/qfai-discussion/references/rcp_footer.md` without rewriting it per skill.
 - Roster and loop rules must stay synchronized with the footer SSOT.
 
 ## Required Coverage Topics

package/assets/init/.qfai/assistant/skills/qfai-discussion/references/rcp_footer.md

@@ -0,0 +1,91 @@
+# RCP Footer (qfai-discussion / SSOT)
+
+この文書は `/qfai-discussion` のレビュー周回（Review Cycle）を「discussion-pack 前提」で固定するための SSOT です。
+他skill向けの共通規約ではありません。
+
+---
+
+## Review Target（固定）
+
+- Scope: `discussion`
+- Pack: `.qfai/discussion/discussion-<YYYYMMDDhhmmssSSS>/`
+- レビュー対象（必須15ファイル）:
+  - `01_Context.md`
+  - `02_Inception-Deck.md`
+  - `03_Story-Workshop.md`
+  - `04_Sources.md`
+  - `05_Scope.md`
+  - `06_REQ.md`
+  - `07_NFR.md`
+  - `08_Glossary.md`
+  - `09_Constraints.md`
+  - `10_Policy.md`
+  - `11_OQ-Register.md`
+  - `12_OQ-Resolution-Log.md`
+  - `13_Deferred.md`
+  - `14_Review-Request.md`
+  - `99_delta.md`
+
+---
+
+## Roster Execution Rule（固定）
+
+- Roster は `.qfai/assistant/steering/review-roster.yml` を読む
+- 各レビューは `PASS` / `FAIL` / `N/A` を返す
+- `N/A` は `na_rule` を満たす理由が必須
+- `FAIL` が1つでも出たら **即修正へ戻る**（後続レビューは回さない）
+- 修正後は **review cycle を新規作成し** roster を先頭から再実行する（スキップ禁止）
+
+---
+
+## Validate Hard Gate（必須）
+
+- 各 review cycle で `qfai validate --fail-on error --format github` を実行していること
+- `.qfai/report/validate.log` が存在し、最新の成果物に対応していること
+
+---
+
+## discussion-pack 固有の Gate（必須）
+
+以下は validator が **error** として扱うため、`fixed` 判定前に必ず潰す：
+
+1. 命名（最新pack判定）
+
+- pack は `discussion-YYYYMMDDhhmmssSSS/` のみ許可
+- 不正な `discussion-*` がある場合は latest 判定が壊れるため、退避または削除する
+
+2. Blocking OQ の解消
+
+- `11_OQ-Register.md` の **Disposition が `open` のまま**で、
+  かつ Gate が `discuss|require|sdd` の OQ が残っていないこと
+- `open` を残す場合は、**Gateを外す**か `Disposition: deferred/resolved` に変更する
+
+3. Deferred の整合
+
+- OQ register で `deferred` にした OQ-ID は、`13_Deferred.md` に同じ OQ-ID で必ず記載する
+
+4. Story Workshop の Mermaid（最小要件）
+
+- `03_Story-Workshop.md` に mermaid fenced block を最低1つ含める
+  - `flowchart` または `sequenceDiagram` を推奨
+
+---
+
+## レビュー観点（discussion-pack 特化）
+
+- Context → Inception Deck → Story Workshop の因果が通っているか
+  - 「なぜ作るか」→「誰のためか」→「どんな業務フローか」が矛盾しない
+- `06_REQ.md` と `07_NFR.md` の境界が崩れていないか
+- Glossary/Constraints/Policy が単なる箇条書きでなく、意思決定（後工程の設計/実装）の入力として使える粒度か
+- `99_delta.md` が “更新履歴” ではなく “検討ログ（採用/不採用/基準）” を持っているか
+
+---
+
+## 代表的な FAIL と復旧（discussion-pack 特化）
+
+- FAIL: `11_OQ-Register.md` に open+Gate が残る
+  - 復旧: 影響範囲が大きいものは `Disposition: deferred` + `13_Deferred.md` に詳細を移す
+- FAIL: `03_Story-Workshop.md` に図がない
+  - 復旧: 1本でよいので、登場人物（ペルソナ）と主要分岐が分かる flowchart を入れる
+- FAIL: pack 名が不正（latest 判定がブレる）
+  - 復旧: 不正 pack を `discussion-legacy-*` に退避し、最新 pack を timestamp 命名で作り直す

package/assets/init/.qfai/assistant/skills/qfai-prototyping/SKILL.md

@@ -59,9 +59,20 @@ When unsure, read inputs in this order:
 
 - P1: `.qfai/assistant/instructions/*`
 - P2: `.qfai/assistant/steering/*`
-- P3: `.qfai/specs/spec-*/09_delta.md` (Decision Records)
-- P4: `.qfai/specs/_shared/05_Contracts.md` and each `spec-*/11_Contracts.md`
-- P5: `.qfai/contracts/**` and existing evidence
+- P3: `.qfai/specs/spec-*/01_Spec.md` (Primary SSOT / Consumer View)
+- P4: `.qfai/contracts/ui/**`, `.qfai/specs/_policies/05_Contracts.md`, and each `spec-*/11_Contracts.md`
+- P5: `.qfai/specs/spec-*/09_delta.md` (Decision Records)
+- P6: existing evidence
+
+## Read Set Contract (Mandatory)
+
+- Default Mode:
+  - `.qfai/specs/spec-*/01_Spec.md`
+  - relevant `.qfai/contracts/ui/**`
+- Escalation Mode:
+  - allowed only when `01_Spec.md` Escalation Hook signals ambiguity / conflict / missing constraint / trade-off
+  - read only `.qfai/specs/_policies/01_Objective.md`, `.qfai/specs/_policies/07_Constraints.md`, `.qfai/specs/_policies/08_Decisions.md`
+- Do not read `_policies/**` by default.
 
 ## Sub-agent Delegation (MANDATORY)
 
@@ -195,7 +206,7 @@ Build the minimum runnable vertical slice for **all specs** so `/qfai-atdd` can
 ## Scope SSOT (ALL contracts -> ALL specs)
 
 1. Enumerate all specs from `.qfai/specs/spec-*`.
-2. Resolve each spec's contracts via `_shared/05_Contracts.md` and/or `spec-*/11_Contracts.md`.
+2. Resolve each spec's contracts via `_policies/05_Contracts.md` and/or `spec-*/11_Contracts.md`.
 3. Do not declare completion while any spec lacks contract assignment.
 
 ## Preflight (required)

package/assets/init/.qfai/assistant/skills/qfai-sdd/SKILL.md

@@ -8,7 +8,7 @@ QFAI Skill Body (SSOT)
 
 name: qfai-sdd
 title: QFAI SDD Unified (Outline/Slice/Plan/Delta)
-description: "Create and update layered SDD artifacts (\_shared + spec-XXXX) in one workflow."
+description: "Create and update layered SDD artifacts (\_policies + spec-XXXX) in one workflow."
 argument-hint: "[<spec-id-or-name>] [--auto]"
 allowed-tools: [Read, Glob, Write, TodoWrite, Task, Bash]
 roles: [Planner, Architect, RequirementsAnalyst, SpecWriter, TraceabilityBuilder, TestStrategist, QAEngineer, CodeReviewer]
@@ -28,7 +28,7 @@ mode: approval-gated
   - `.qfai/contracts/**/README.md`
   - `.qfai/evidence/README.md`
   - `.qfai/assistant/steering/review-roster.yml`
-  - `.qfai/assistant/templates/rcp_footer.md`
+  - `.qfai/assistant/skills/qfai-sdd/references/rcp_footer.md`
 - Use skill-local templates as SSOT:
   - `.qfai/assistant/skills/qfai-sdd/templates/report/preflight_summary.md`
 - Do NOT duplicate templates directly in this workflow markdown.
@@ -94,7 +94,7 @@ Every major artifact in this stage MUST include a `## Work Orders Summary` secti
 ### No-argument batch delegation (MUST)
 
 - If `/qfai-sdd` is invoked without `<spec-id-or-name>`, treat the run as an all-capability batch.
-- Enumerate targets from `.qfai/specs/_shared/03_Capabilities.md` and keep `spec-0001..N` mapping stable by Capability order.
+- Enumerate targets from `.qfai/specs/_policies/03_Capabilities.md` and keep `spec-0001..N` mapping stable by Capability order.
 - In batch mode, run Contracts-first and Outline exactly once as shared outputs.
 - Delegate Slice in parallel per spec:
   - `SpecWriter + TraceabilityBuilder` own `spec-XXXX/01..08`.
@@ -170,7 +170,7 @@ Evidence checked:
 ## Review Cycle Protocol (RCP)
 
 - Roster SSOT: `.qfai/assistant/steering/review-roster.yml`.
-- Footer SSOT: `.qfai/assistant/templates/rcp_footer.md`.
+- Footer SSOT: `.qfai/assistant/skills/qfai-sdd/references/rcp_footer.md`.
 - Every discuss/require/sdd review cycle must execute the full roster.
 - Allowed reviewer verdicts: `PASS`, `FAIL`, `N/A` (`N/A` requires `na_rule` reason).
 - Any `FAIL` triggers return/fix/full-rerun from the first reviewer.
@@ -203,14 +203,14 @@ Rules:
 - **Upper-to-lower references are forbidden. Lower-to-upper references are allowed.**
 - **Connections between layers MUST be represented by IDs and required edges (`US->AC->BR->EX->TC`).**
 - **Plan finalize MUST happen after at least one user-story slice is grounded.**
-- **Unresolved items MUST be moved to `08_Open-questions.md` (spec scope) or `_shared/09_Open-questions.md` (shared scope).**
+- **Unresolved items MUST be moved to `08_Open-questions.md` (spec scope) or `_policies/09_Open-questions.md` (shared scope).**
 
 ## Arguments and Target Selection (Mandatory)
 
 - With argument (`/qfai-sdd <spec-id-or-name> [--auto]`): update only the matched single spec target.
-- Without argument (`/qfai-sdd`): target all capabilities listed in `_shared/03_Capabilities.md`.
-- If `_shared/03_Capabilities.md` does not exist, bootstrap shared templates first, then enumerate capabilities.
-- Capability order in `_shared/03_Capabilities.md` is SSOT for `spec-0001..N` assignment and ID stability.
+- Without argument (`/qfai-sdd`): target all capabilities listed in `_policies/03_Capabilities.md`.
+- If `_policies/03_Capabilities.md` does not exist, bootstrap shared templates first, then enumerate capabilities.
+- Capability order in `_policies/03_Capabilities.md` is SSOT for `spec-0001..N` assignment and ID stability.
 - Reordering capability-to-spec mapping is a Change Request decision and must not be done implicitly.
 - Batch policy (no argument):
   - Contracts-first/Outline: once per batch.
@@ -226,7 +226,7 @@ Rules:
 - Always write `.qfai/report/preflight_summary.md` before generating shared/spec artifacts.
 - Contracts are contract-first mandatory outputs in this skill:
   - create/update `.qfai/contracts/(api|db|ui)/**` before shared/spec slices
-  - `_shared/05_Contracts.md` must include a Contract Index with short IDs (`DB-001`, `API-001`, `UI-001`)
+  - `_policies/05_Contracts.md` must include a Contract Index with short IDs (`DB-001`, `API-001`, `UI-001`)
   - every indexed short ID must map to a declared file with `QFAI-CONTRACT-ID`:
     - `DB-001 -> CON-DB-0001 -> db-0001-<slug>.sql`
     - `API-001 -> CON-API-0001 -> api-0001-<slug>.yaml`
@@ -237,8 +237,8 @@ Rules:
   - contract stubs must be syntactically valid (OpenAPI YAML / UI YAML / executable SQL skeleton)
 - `/qfai-sdd` must stop when discussion-pack is missing/incomplete or has blocking OQ (guide to `/qfai-discussion` first).
 - Review roster is fixed by `.qfai/assistant/steering/review-roster.yml` and must be executed in full.
-- RCP wording must be sourced from `.qfai/assistant/templates/rcp_footer.md`.
-- `_shared/04_Business-Flow.md` must be Markdown and include at least one Mermaid `flowchart` or `sequenceDiagram`.
+- RCP wording must be sourced from `.qfai/assistant/skills/qfai-sdd/references/rcp_footer.md`.
+- `_policies/04_Business-Flow.md` must be Markdown and include at least one Mermaid `flowchart` or `sequenceDiagram`.
 - Business Flow must not be authored as Gherkin (`*Business-flow*.feature` is deprecated).
 - If diagrams are written in discuss/require/spec/evidence artifacts, Mermaid syntax must be inside ` ```mermaid ` fences only.
 - `05_Examples.md` must include `EX-ID` and `BR-Ref` mappings.
@@ -266,12 +266,12 @@ Create/update:
 - `.qfai/contracts/api/**`
 - `.qfai/contracts/db/**`
 - `.qfai/contracts/ui/**`
-- `_shared/05_Contracts.md` Contract Index table (DB/API/UI short IDs)
+- `_policies/05_Contracts.md` Contract Index table (DB/API/UI short IDs)
 
 Rules:
 
 - This phase MUST complete before Outline/Slice.
-- If `_shared/05_Contracts.md` lists an ID, the corresponding declared contract file MUST exist.
+- If `_policies/05_Contracts.md` lists an ID, the corresponding declared contract file MUST exist.
 - If a contract is empty, create a valid minimal stub and include `QFAI-CONTRACT-ID`.
 - `none` is allowed only when there is no contract impact and rationale is written.
 
@@ -279,22 +279,22 @@ Rules:
 
 Create/update:
 
-- `_shared/01_Objective.md`
-- `_shared/02_Initiative.md`
-- `_shared/03_Capabilities.md`
-- `_shared/04_Business-Flow.md`
-- `_shared/05_Contracts.md`
-- `_shared/06_Glossary.md`
-- `_shared/07_Constraints.md`
-- `_shared/08_Decisions.md`
-- `_shared/09_Open-questions.md`
-- `_shared/10_delta.md`
+- `_policies/01_Objective.md`
+- `_policies/02_Initiative.md`
+- `_policies/03_Capabilities.md`
+- `_policies/04_Business-Flow.md`
+- `_policies/05_Contracts.md`
+- `_policies/06_Glossary.md`
+- `_policies/07_Constraints.md`
+- `_policies/08_Decisions.md`
+- `_policies/09_Open-questions.md`
+- `_policies/10_delta.md`
 
 Rules:
 
-- Temporary `TBD` is allowed, but each `TBD` must be mirrored into `_shared/09_Open-questions.md`.
-- `_shared/04_Business-Flow.md` must include Mermaid and keep diagram syntax inside ` ```mermaid ` fences.
-- `_shared/08_Decisions.md` and `_shared/10_delta.md` must exist even when empty, and must explicitly state `0 items`.
+- Temporary `TBD` is allowed, but each `TBD` must be mirrored into `_policies/09_Open-questions.md`.
+- `_policies/04_Business-Flow.md` must include Mermaid and keep diagram syntax inside ` ```mermaid ` fences.
+- `_policies/08_Decisions.md` and `_policies/10_delta.md` must exist even when empty, and must explicitly state `0 items`.
 
 ### Phase 2 - Slice (slice-first)
 
@@ -316,6 +316,7 @@ Slice gate (must pass before Phase 3):
 - For each TC, EX reference must exist.
 - `SC` tags must align with the target `spec-XXXX` namespace.
 - `07_Decisions.md` and `08_Open-questions.md` must exist even when empty and include explicit `0 items` statements.
+- `01_Spec.md` is the execution Primary SSOT and MUST copy down applicable NFR, policy, evidence summary, relevant requirements, and an Escalation Hook to `_policies`.
 
 ### Phase 3 - Plan finalize
 
@@ -366,16 +367,16 @@ Create or update layered SDD artifacts in one run so downstream execution phases
 
 ## Mandatory Outputs
 
-- `.qfai/specs/_shared/01_Objective.md`
-- `.qfai/specs/_shared/02_Initiative.md`
-- `.qfai/specs/_shared/03_Capabilities.md`
-- `.qfai/specs/_shared/04_Business-Flow.md`
-- `.qfai/specs/_shared/05_Contracts.md`
-- `.qfai/specs/_shared/06_Glossary.md`
-- `.qfai/specs/_shared/07_Constraints.md`
-- `.qfai/specs/_shared/08_Decisions.md`
-- `.qfai/specs/_shared/09_Open-questions.md`
-- `.qfai/specs/_shared/10_delta.md`
+- `.qfai/specs/_policies/01_Objective.md`
+- `.qfai/specs/_policies/02_Initiative.md`
+- `.qfai/specs/_policies/03_Capabilities.md`
+- `.qfai/specs/_policies/04_Business-Flow.md`
+- `.qfai/specs/_policies/05_Contracts.md`
+- `.qfai/specs/_policies/06_Glossary.md`
+- `.qfai/specs/_policies/07_Constraints.md`
+- `.qfai/specs/_policies/08_Decisions.md`
+- `.qfai/specs/_policies/09_Open-questions.md`
+- `.qfai/specs/_policies/10_delta.md`
 - `.qfai/specs/spec-XXXX/01_Spec.md`
 - `.qfai/specs/spec-XXXX/02_User-stories.md`
 - `.qfai/specs/spec-XXXX/03_Acceptance-Criteria.md`
@@ -396,7 +397,7 @@ Create or update layered SDD artifacts in one run so downstream execution phases
 2. If readiness checks fail, stop and show blockers with `/qfai-discussion`.
 3. Analyze repository context, existing artifacts, constraints, and open decisions.
 4. Write `.qfai/report/preflight_summary.md` from `templates/report/preflight_summary.md`.
-5. Execute Phase 0 (Contracts-first) and ensure `_shared/05_Contracts.md` index and `.qfai/contracts/**` are aligned.
+5. Execute Phase 0 (Contracts-first) and ensure `_policies/05_Contracts.md` index and `.qfai/contracts/**` are aligned.
 6. Execute Phase 1 (Outline) in layer-first order.
 7. Execute Phase 2 (Slice) and pass slice gate for each target spec (single target: at least one user-story slice; no-argument batch: all enumerated specs).
 8. Execute Phase 3 (Plan finalize) and make every target `10_Plan.md` actionable as How-only.
@@ -410,8 +411,9 @@ Create or update layered SDD artifacts in one run so downstream execution phases
 
 Run static checks:
 
-- Confirm required `_shared` and `spec-XXXX` layered files exist.
-- Confirm `_shared/04_Business-Flow.md` includes Mermaid and at least one `flowchart` or `sequenceDiagram`.
+- Confirm required `_policies` and `spec-XXXX` layered files exist.
+- Confirm `_policies/04_Business-Flow.md` includes Mermaid and at least one `flowchart` or `sequenceDiagram`.
+- Confirm `01_Spec.md` includes copy-down context and Escalation Hook to `_policies`.
 - Confirm Mermaid syntax is not written in ` ```text ` or language-less fences.
 - Confirm `05_Examples.md` provides `EX-ID` + `BR-Ref` mappings.
 - Confirm `06_Test-Cases.md` provides `TC-ID` + `EX-Ref` + `AC-Refs`.
@@ -457,11 +459,11 @@ When declaring DONE, include:
 - [ ] CRITICAL CONSTRAINTS were followed.
 - [ ] `.qfai/report/preflight_summary.md` was generated before spec authoring.
 - [ ] Contracts-first -> Outline -> Slice -> Plan finalize -> Delta update order was preserved.
-- [ ] `_shared/05_Contracts.md` index and `.qfai/contracts/**` declared files are aligned.
+- [ ] `_policies/05_Contracts.md` index and `.qfai/contracts/**` declared files are aligned.
 - [ ] Upper-to-lower references were not introduced.
 - [ ] At least one user-story slice passed gate before plan finalization.
-- [ ] Required `_shared` + `spec-XXXX` outputs exist and are internally consistent.
-- [ ] `_shared/04_Business-Flow.md` is Markdown + Mermaid (`flowchart` or `sequenceDiagram`).
+- [ ] Required `_policies` + `spec-XXXX` outputs exist and are internally consistent.
+- [ ] `_policies/04_Business-Flow.md` is Markdown + Mermaid (`flowchart` or `sequenceDiagram`).
 - [ ] Mermaid syntax was not written in ` ```text ` or language-less fences.
 - [ ] `10_Plan.md` is finalized with implementation/test strategy (How-only).
 - [ ] `specs/plan.md` was not created.
@@ -493,6 +495,6 @@ When this skill is complete, provide a final user-facing completion message and
 - Test-first path: `/qfai-atdd`.
   Action: implement acceptance tests from the finalized spec pack.
 - Contracts status:
-  Action: confirm contracts were created/updated under `.qfai/contracts/**` and referenced by `_shared/05_Contracts.md`.
+  Action: confirm contracts were created/updated under `.qfai/contracts/**` and referenced by `_policies/05_Contracts.md`.
 - Spec pack needs correction: rerun `/qfai-sdd`.
-  Action: fix layered `_shared + spec-XXXX` consistency and decision records, then regenerate evidence.
+  Action: fix layered `_policies + spec-XXXX` consistency and decision records, then regenerate evidence.

package/assets/init/.qfai/assistant/skills/qfai-sdd/references/rcp_footer.md

@@ -0,0 +1,84 @@
+# RCP Footer (qfai-sdd / SSOT)
+
+この文書は `/qfai-sdd` のレビュー周回（Review Cycle）を「spec/contract 前提」で固定するための SSOT です。
+discussion-pack 等の共通規約ではありません。
+
+---
+
+## Review Target（固定）
+
+- Scope: `sdd`
+- 主要成果物（レビュー対象）:
+  - `.qfai/specs/spec-*/**`（spec pack）
+  - `.qfai/contracts/**`（API/DB/UI 契約）
+  - `.qfai/evidence/**`（意思決定根拠・実験ログ）
+  - `.qfai/report/**`（validate / coverage / preflight 出力）
+
+---
+
+## Roster Execution Rule（固定）
+
+- Roster は `.qfai/assistant/steering/review-roster.yml` を読む
+- 各レビューは `PASS` / `FAIL` / `N/A` を返す
+- `FAIL` が1つでも出たら **即修正へ戻る**
+- 修正後は **review cycle を新規作成し** roster を先頭から再実行する（スキップ禁止）
+
+---
+
+## Validate Hard Gate（必須）
+
+- 各 review cycle で `qfai validate --fail-on error --format github` を実行していること
+- `.qfai/report/validate.log` が存在し、最新の成果物に対応していること
+
+---
+
+## Required Review Artifacts（必須）
+
+各 review cycle で、以下を必ず生成する:
+
+- `.qfai/review/review-<timestamp>/review_request.md`
+- `.qfai/review/review-<timestamp>/R01_<reviewer>.md`, `R02_<reviewer>.md`, ...
+- `.qfai/review/review-<timestamp>/summary.json`
+
+`summary.json` の最低要件:
+
+- `version`
+- `created_at`
+- `target`
+- `roster`
+- `overall_status`
+
+---
+
+## spec-pack 固有のレビュー観点（sdd 特化）
+
+1. 仕様の一貫性
+
+- spec の「目的/スコープ/非スコープ」が、後続の user story / acceptance criteria / examples と矛盾しない
+- “例（Examples）” が acceptance criteria を **具体ケースとして裏付け**ている（単なる繰り返しではない）
+
+2. 意思決定の可観測性（Decision Log）
+
+- `delta` / decisions / rejected が「なぜ採用/不採用か」を保持している
+- “Temptation（再発しがちな誤り）” が明文化され、再採用防止になっている
+
+3. Contracts の妥当性
+
+- API / UI / DB 契約が spec の用語と一致している（同一概念に別名を付けない）
+- 禁止参照（contracts 特例ルール等）がある場合は、契約側の README のルールに従っている
+
+4. Traceability（必要なら）
+
+- spec → tests（ATDD/TDD）への紐付けが破綻していない
+- “数を増やす” のではなく “境界/負例/権限/状態遷移” の観点が埋まっている
+
+---
+
+## 代表的な FAIL と復旧（sdd 特化）
+
+- FAIL: acceptance criteria が抽象的で、例に落ちていない
+  - 復旧: 例（Examples）に「入力→状態→出力」形式のケースを追加し、境界/異常系を1つは入れる
+- FAIL: 契約が先行し、spec の用語・概念とズレる
+  - 復旧: 先に Glossary/Capabilities を補強し、契約を spec に合わせて修正する
+- FAIL: decision/rejected が薄く、なぜそうしたかが追えない
+  - 復旧: 代替案A/B/Cと採用基準を書き、Rejected に DO NOT/Temptation を残す

package/assets/init/.qfai/assistant/skills/qfai-sdd/templates/specs/{_shared → _policies}/03_Capabilities.md

@@ -15,5 +15,5 @@
 
 ## Authoring rules
 
-- This file is shared SSOT across all specs.
+- This file is the policy-layer SSOT for capability mapping across all specs.
 - Do not copy spec-level details (US/AC/BR/EX/TC) into this file.

package/assets/init/.qfai/assistant/skills/qfai-sdd/templates/specs/{_shared → _policies}/04_Business-Flow.md

@@ -2,7 +2,7 @@
 
 ## Purpose
 
-- Describe the high-level business process as shared SSOT.
+- Describe the high-level business process as policy-layer SSOT.
 - Keep acceptance scenarios in `spec-XXXX/03_Acceptance-Criteria.md`.
 
 ## Actors / Systems

package/assets/init/.qfai/assistant/skills/qfai-sdd/templates/specs/{_shared → _policies}/05_Contracts.md

@@ -3,7 +3,7 @@
 ## Purpose
 
 - Keep contracts as SSOT under `.qfai/contracts/**` with deterministic IDs.
-- Use this file as a readable index with short IDs for planning and review.
+- Use this file as a readable policy-layer index with short IDs for planning and review.
 
 ## Contract Index