qfai 1.4.38 → 1.5.0

package/README.md

@@ -31,15 +31,24 @@ npx qfai report
 ## What you can do (CLI commands)
 
 - `npx qfai init`
-  - Creates the QFAI workspace under `.qfai/` (requirements/specs/contracts/report) and installs the AI assistant kit (`assistant/` with skills, instructions, agents, and steering templates), plus `qfai.config.yaml`.
+  - Creates the QFAI workspace under `.qfai/` (requirements/specs/contracts/report) and installs the AI assistant kit
+    (`assistant/` with skills, instructions, agents, and steering templates), plus `qfai.config.yaml`.
 - `npx qfai validate`
-  - Validates specs/contracts/scenarios/traceability and review artifacts (`.qfai/review/review-*/summary.json` + minimum schema), writes `.qfai/report/validate.json`, and appends run logs to `.qfai/report/run-*/`; use `--fail-on error` (or `--fail-on warning`) to turn it into a CI gate, and `--format github` to emit GitHub-friendly annotations. Use `--phase refinement` only for local refinement checks; CI should use default/full validation.
+  - Validates specs/contracts/scenarios/traceability and review artifacts
+    (`.qfai/review/review-*/summary.json` + minimum schema), writes `.qfai/report/validate.json`,
+    and appends run logs to `.qfai/report/run-*/`; use `--fail-on error` (or `--fail-on warning`) to turn it into a CI gate,
+    and `--format github` to emit GitHub-friendly annotations.
+    Use `--phase refinement` only for local refinement checks; CI should use default/full validation.
 - `npx qfai report`
   - Produces a human-readable report (`report.md` by default) or an internal JSON export (`report.json`) from `validate.json`; use `--base-url` to link file paths in Markdown to your repository viewer.
 - `npx qfai doctor`
   - Diagnoses configuration discovery, path resolution, glob scanning, and `validate.json` inputs before running validate/report; use `--fail-on` to enforce failures in CI.
 - `npx qfai prototyping --autogen-ui-fidelity --base-url <url>`
-  - Auto-generates `uiFidelity` evidence by crawling UI routes and collecting DOM labels; writes to `.qfai/evidence/prototyping.json` (or `--evidence-out <path>`). Requires `--base-url` or `QFAI_PROTOTYPE_BASE_URL` to specify the running application URL. Use `--autogen-only` to fail when generation fails (for CI gates). Enable with `QFAI_PROTOTYPE_FIDELITY_AUTOGEN=1` as an alternative to `--autogen-ui-fidelity`.
+  - Auto-generates `uiFidelity` evidence by crawling UI routes and collecting DOM labels;
+    writes to `.qfai/evidence/prototyping.json` (or `--evidence-out <path>`).
+    Requires `--base-url` or `QFAI_PROTOTYPE_BASE_URL` to specify the running application URL.
+    Use `--autogen-only` to fail when generation fails (for CI gates).
+    Enable with `QFAI_PROTOTYPE_FIDELITY_AUTOGEN=1` as an alternative to `--autogen-ui-fidelity`.
 
 ## ATDD annotation hard gate (v1.4.36)
 
@@ -103,10 +112,11 @@ The agent reads QFAI assets under `.qfai/assistant/` and produces or updates SDD
 
 QFAI includes a small set of custom skills (stored under `.qfai/assistant/skills/`) designed to keep the workflow opinionated and repeatable.
 
-- **qfai-configure**: Analyze the repository (language, frameworks, test layout, directory structure) and tailor `qfai.config.yaml` accordingly (especially `testFileGlobs`). Run this once right after `npx qfai init`, and re-run it when the repository structure changes.
-- **qfai-discuss**: Turn an idea into clear requirements by discussing scope, constraints, risks, and open questions.
-- **qfai-require**: Produce a fixed 9-file require-pack (`01_Sources.md`..`09_delta.md`) under `.qfai/require/require-<ts>/`.
-- **qfai-sdd**: Unified SDD entrypoint with require-pack preflight guard (missing/incomplete/blocking OQ causes stop + next action guidance).
+- **qfai-configure**: Analyze the repository (language, frameworks, test layout, directory structure)
+  and tailor `qfai.config.yaml` accordingly (especially `testFileGlobs`).
+  Run this once right after `npx qfai init`, and re-run it when the repository structure changes.
+- **qfai-discussion**: Run a unified structured discussion that merges discuss and require into a single 15-file discussion pack under `.qfai/discussion/discussion-<ts>/`.
+- **qfai-sdd**: Unified SDD entrypoint with discussion-pack preflight guard (missing/incomplete/blocking OQ causes stop + next action guidance).
 - **qfai-prototyping**: Build an all-spec contract-aligned skeleton and prove runtime coverage before deep coding.
 - **qfai-atdd**: Implement acceptance tests driven by specs/scenarios.
 - **qfai-tdd-red / qfai-tdd-green / qfai-tdd-refactor (deprecated wrappers)**: Legacy entrypoints kept for backward compatibility only. They return deprecation guidance and route to `/qfai-atdd` + `/qfai-verify`.
@@ -133,15 +143,10 @@ AG->>R: Update qfai.config.yaml (testFileGlobs, etc.)
 AG-->>U: Config tuned to this repo
 
 opt If you only have an idea
-U->>AG: Run /qfai-discuss
-AG-->>U: Structured discuss package (.qfai/discuss/discuss-<ts>/)
+U->>AG: Run /qfai-discussion
+AG-->>U: Structured discussion package (.qfai/discussion/discussion-<ts>/)
 end
 
-U->>AG: Run /qfai-require
-AG->>Q: Read .qfai/assistant/skills/qfai-require/SKILL.md
-AG->>R: Create/Update require-pack under require-<ts> (01_Sources..09_delta)
-AG-->>U: Require-pack ready
-
 U->>AG: Run /qfai-sdd
 AG->>Q: Read .qfai/assistant/skills/qfai-sdd/SKILL.md
 AG->>R: Preflight + create/refine layered specs + finalize 10_Plan + 09_delta
@@ -175,7 +180,7 @@ Operational notes.
 
 - Each custom skill must output in the user’s language (absolute requirement).
 - Each custom skill must end with a completion message that enumerates all available next actions and clearly states what to do for each option.
-- Except `qfai-discuss`, each skill must analyze the project context (architecture, tech stack, test framework, repo structure) before generating artifacts or code.
+- Except `qfai-discussion`, each skill must analyze the project context (architecture, tech stack, test framework, repo structure) before generating artifacts or code.
 - Skills should delegate work to multiple role-based sub-agents (Planner, Architect, Contract Designer, QA, Code Reviewer, etc.) to emulate a real delivery flow.
 - Change classification (Primary/Tags) is required in `09_delta.md` and recommended in PRs. See `.qfai/assistant/instructions/change-classification.md`.
 - Verification planning is recorded in `09_delta.md` (`Verification -> Plan`) and validated in CI (`VFY-*` rules).
@@ -192,7 +197,7 @@ Example: override paths and traceability globs.
 paths:
   contractsDir: .qfai/contracts
   specsDir: .qfai/specs
-  requireDir: .qfai/require
+  discussionDir: .qfai/discussion
   outDir: .qfai/report
   skillsDir: .qfai/assistant/skills
   srcDir: src
@@ -232,23 +237,22 @@ Traceability is validated across these artifacts, so code changes remain grounde
 
 ```mermaid
 flowchart LR
-  S[.qfai/specs/** (layered 01..10)] --> V[qfai validate]
-  C[.qfai/contracts/**] --> V
-  V --> R[.qfai/report/**]
+  S[".qfai/specs/** (layered 01..10)"] --> V["qfai validate"]
+  C[".qfai/contracts/**"] --> V
+  V --> R[".qfai/report/**"]
 ```
 
 - Specs SSOT: `.qfai/specs/**` (layered files `01_Spec.md`..`09_delta.md` + shared delta layer)
 - Contracts SSOT: `.qfai/contracts/**`
 - Report outputs (`.qfai/report/**`) are derived artifacts and not SSOT.
 
-## Minimal tutorial (v1.4.36)
+## Minimal tutorial (v1.5.0)
 
 1. `npx qfai init`
-2. Run `/qfai-discuss` to structure scope and open questions.
-3. Run `/qfai-require` to produce a require pack (`01_Sources`..`09_delta`) under `.qfai/require/require-<ts>/`.
-4. Run `/qfai-sdd` to build layered specs and finalized plans.
-5. For each completed review cycle, append artifacts under `.qfai/review/review-<timestamp>/`.
-6. Run `npx qfai validate` then `npx qfai report`.
+2. Run `/qfai-discussion` to structure scope, open questions, and produce a discussion pack under `.qfai/discussion/discussion-<ts>/`.
+3. Run `/qfai-sdd` to build layered specs and finalized plans.
+4. For each completed review cycle, append artifacts under `.qfai/review/review-<timestamp>/`.
+5. Run `npx qfai validate` then `npx qfai report`.
 
 Release gate behavior:
 
@@ -335,12 +339,10 @@ Typical customizations.
 │   │   ├── skills
 │   │   │   ├── qfai-configure
 │   │   │   │   └── SKILL.md
-│   │   │   ├── qfai-discuss
+│   │   │   ├── qfai-discussion
 │   │   │   │   └── SKILL.md
 │   │   │   ├── qfai-prototyping
 │   │   │   │   └── SKILL.md
-│   │   │   ├── qfai-require
-│   │   │   │   └── SKILL.md
 │   │   │   ├── qfai-sdd
 │   │   │   │   └── SKILL.md
 │   │   │   ├── qfai-atdd

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

@@ -14,8 +14,7 @@ This folder is generated by `qfai init` and designed to be:
 
 ```mermaid
 flowchart TD
-  A[/qfai-discuss/] --> B[/qfai-require/]
-  B --> C[/qfai-sdd/]
+  A[/qfai-discussion/] --> C[/qfai-sdd/]
   C --> D[/qfai-prototyping/]
   D --> E[/qfai-atdd/]
   E --> F[/qfai-tdd-red/]

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

@@ -72,7 +72,7 @@ Legacy note:
 
 ### Stage 0 — Steering refresh contract (mandatory)
 
-At the beginning of each stage (`qfai-discuss`, `qfai-require`, `qfai-sdd`, `qfai-prototyping`, `qfai-atdd`, `qfai-verify`):
+At the beginning of each stage (`qfai-discussion`, `qfai-sdd`, `qfai-prototyping`, `qfai-atdd`, `qfai-verify`):
 
 1. Check these steering files:
    - `.qfai/assistant/steering/manifest.md`

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

@@ -437,7 +437,7 @@ Provide:
 5. If specSections updated, list the chosen headings and evidence source.
 6. Open questions (blocking vs non-blocking).
 
-Suggest next step: `/qfai-require` (or `/qfai-discuss` if requirements are not ready).
+Suggest next step: `/qfai-discussion` (or rerun `/qfai-configure` if configuration is not ready).
 
 ## DONE Declaration (Mandatory Output)
 
@@ -467,9 +467,9 @@ When you declare DONE, include:
 
 When this skill is complete, provide a final user-facing completion message and enumerate all actionable next steps.
 
-- Proceed (recommended): `/qfai-require`.
+- Proceed (recommended): `/qfai-discussion`.
   Action: run it to formalize requirements from the configured project context.
-- Requirements are still unclear: `/qfai-discuss`.
+- Discussion needs more input: rerun `/qfai-discussion`.
   Action: collect missing scope, constraints, and assumptions first.
 - Configuration needs refinement: rerun `/qfai-configure`.
   Action: provide additional include/exclude evidence and update `qfai.config.yaml`.

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

@@ -0,0 +1,331 @@
+````skill
+<!--
+QFAI Skill Body (SSOT)
+- This file is intended to be referenced by tool-specific wrappers (e.g., GitHub/Claude/Codex skills).
+- Keep wrappers thin and route users to this skill body.
+-->
+
+---
+
+name: qfai-discussion
+title: QFAI Discussion (Unified Discuss + Require)
+description: "Run structured discussion that merges discuss and require into a single 15-file discussion pack with OQ-driven exit."
+argument-hint: "<idea-or-problem> [--auto]"
+allowed-tools: [Read, Glob, Write, TodoWrite, Task, Bash]
+roles: [Researcher, Facilitator, Interviewer, RequirementsAnalyst, QAEngineer, Planner]
+mode: interactive-by-default
+
+---
+
+# /qfai-discussion - Unified Discuss + Require
+
+[DRIFT-PROTOCOL:MANDATORY]
+
+## FORMAT SSOT (Mandatory)
+
+- Before writing artifacts, read and follow:
+  - `.qfai/discussion/README.md`
+  - `.qfai/specs/README.md`
+  - `.qfai/evidence/README.md`
+  - `.qfai/assistant/steering/review-roster.yml`
+  - `.qfai/assistant/templates/rcp_footer.md`
+- Keep templates as source of truth and preserve file naming/order.
+
+## Sub-agent Delegation (MANDATORY)
+
+### Orchestrator Protocol (MUST)
+
+- Orchestrator may only create work orders, delegate tasks, integrate outputs, and present results.
+- Orchestrator MUST NOT generate the primary artifact first draft.
+- Orchestrator MUST NOT self-approve.
+
+### Capability Probe (MUST)
+
+1. Run one harmless Probe Task once at stage start.
+2. If subagents are unavailable, explicitly ask for Simulation mode approval.
+3. Without explicit approval, stop the stage.
+
+### Simulation mode (Opt-in only)
+
+- Allowed only when user explicitly states `Simulation mode allowed`.
+- Record both:
+  - `Subagents: simulated (reason: <why unavailable>)`
+  - `User approval: <quote or reference>`
+
+## Work Orders Summary
+
+Every major artifact in this stage MUST include this table schema:
+
+| Step | Role (sub-agent) | Task title | Input (refs) | Output (refs) | Status (PASS/REVISE) |
+| ---- | ---------------- | ---------- | ------------ | ------------- | -------------------- |
+| 1    | <role>           | <task>     | <refs>       | <refs>        | PASS/REVISE          |
+
+### Reviewer Gate (MUST)
+
+- Delegate final completion gate to an independent Reviewer.
+- Reviewer must check Drift Protocol compliance and alignment with `.qfai/assistant/steering/test-layers.md`.
+- Test volume floors/ratios are not gates; they are risk signals.
+- Do not declare DONE until Reviewer returns `PASS`; otherwise apply `REVISE`.
+
+## CRITICAL CONSTRAINTS (Read First)
+
+- Output path is fixed: `.qfai/discussion/discussion-YYYYMMDDhhmmssSSS/`.
+- Timestamp format is fixed to `YYYYMMDDhhmmssSSS` (3-digit milliseconds).
+- Required fixed files (all 15 are mandatory):
+  - `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`
+- Discussion completion requires `Disposition: open` count to be zero in `11_OQ-Register.md`.
+- `deferred` is allowed only when required metadata is complete in `13_Deferred.md`.
+- `03_Story-Workshop.md` MUST contain at least one Mermaid diagram in ` ```mermaid ` fences.
+- 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`.
+- 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.
+- Example Mapping is mandatory and must be captured as `Example Seeds` sections in `03_Story-Workshop.md`.
+- OQ Register must include all mandatory columns: OQ-ID, Title, Gate, Disposition, Owner, Rationale, Options, Recommendation, Next-Decision-Point, Due, Evidence.
+- Deferred table must include all mandatory columns: OQ-ID, Title, Gate, Deferred-Reason, Deferred-Until, Owner, Due, Severity, Impact, Mitigation, Evidence.
+
+## Goal
+
+Produce a unified 15-file discussion pack with explicit decisions, requirements, OQ states, and rationale so `/qfai-sdd` starts without unresolved blockers.
+
+## Non-goals
+
+- Editing `.qfai/specs/**` directly.
+- Writing implementation-level details.
+- Leaving open blockers hidden in free text.
+
+## Mandatory Outputs
+
+- `.qfai/discussion/discussion-*/01_Context.md`
+- `.qfai/discussion/discussion-*/02_Inception-Deck.md`
+- `.qfai/discussion/discussion-*/03_Story-Workshop.md`
+- `.qfai/discussion/discussion-*/04_Sources.md`
+- `.qfai/discussion/discussion-*/05_Scope.md`
+- `.qfai/discussion/discussion-*/06_REQ.md`
+- `.qfai/discussion/discussion-*/07_NFR.md`
+- `.qfai/discussion/discussion-*/08_Glossary.md`
+- `.qfai/discussion/discussion-*/09_Constraints.md`
+- `.qfai/discussion/discussion-*/10_Policy.md`
+- `.qfai/discussion/discussion-*/11_OQ-Register.md`
+- `.qfai/discussion/discussion-*/12_OQ-Resolution-Log.md`
+- `.qfai/discussion/discussion-*/13_Deferred.md`
+- `.qfai/discussion/discussion-*/14_Review-Request.md`
+- `.qfai/discussion/discussion-*/99_delta.md`
+- review artifacts under `.qfai/review/review-YYYYMMDDhhmmssSSS/`
+- Evidence file: `.qfai/evidence/discussion-YYYYMMDDhhmmssSSS.md`
+- Reviewer notes (`PASS` or `REVISE`)
+
+## Required Process
+
+1. Run the core interview for product concept, scope, stakeholders, and constraints (`01_Context.md`).
+2. Run Inception Deck (10 questions) for ambiguity removal and project alignment (`02_Inception-Deck.md`).
+3. Run Story Workshop to capture user stories, user flows, and at least one Mermaid diagram (`03_Story-Workshop.md`).
+4. Register source traceability in `04_Sources.md` with stable `SRC-XXXX` identifiers.
+5. Define scope boundaries and success criteria in `05_Scope.md`.
+6. Capture functional requirements in `06_REQ.md` with `REQ-0001` format.
+7. Capture non-functional requirements in `07_NFR.md` with `NFR-0001` format.
+8. Capture domain terms and definitions in `08_Glossary.md`.
+9. Capture constraints (technical, operational, legal, budget, deadline) in `09_Constraints.md`.
+10. Capture policies (security, compliance, etc.) in `10_Policy.md`.
+11. Run Example Mapping pass for each BR/AC candidate and capture `Example Seeds` in `03_Story-Workshop.md`.
+12. Update `11_OQ-Register.md` with all identified OQs using all mandatory columns.
+13. Run OQ resolution hearing repeatedly until open count is zero.
+14. Move deferred items to `13_Deferred.md` with all mandatory metadata columns.
+15. Update `12_OQ-Resolution-Log.md`, `14_Review-Request.md`, and `99_delta.md`.
+16. Request review and record Reviewer result.
+
+## Example Mapping Perspectives (Mandatory)
+
+For each BR/AC candidate, enumerate concrete example seeds with these perspectives:
+
+1. Happy path
+2. Negative path
+3. Edge / boundary
+4. Permission / role
+5. State transition (if stateful)
+6. Idempotency / retry (if external I/O exists)
+
+Rules:
+
+- Use perspective coverage as the gate, not raw case counts.
+- Mark intentionally skipped perspectives with reason and follow-up.
+- Feed unresolved seeds into OQ items with owner and decision point.
+
+## OQ Data Model (Mandatory)
+
+`11_OQ-Register.md` must include these fields for each OQ:
+
+- `OQ-ID` (`OQ-0001` format)
+- `Title`
+- `Gate` (`discuss|require|sdd`)
+- `Disposition` (`open|resolved|deferred|rejected`)
+- `Owner` (`user|agent|team`)
+- `Rationale` (required for deferred/rejected)
+- `Options` (at least two alternatives and one recommended option)
+- `Recommendation` (explicitly stated recommended option)
+- `Next-Decision-Point` (required for deferred)
+- `Due` (target date or milestone)
+- `Evidence`
+
+## Deferred Metadata Rules (Mandatory)
+
+`13_Deferred.md` must include:
+
+- `OQ-ID`
+- `Title`
+- `Gate`
+- `Deferred-Reason`
+- `Deferred-Until`
+- `Owner`
+- `Due`
+- `Severity` (`high|medium|low`)
+- `Impact` (spec/tests/implementation/operations)
+- `Mitigation`
+- `Evidence`
+
+## Drift Protocol (Mandatory)
+
+At any point during discussion, if the user changes direction or scope:
+
+1. Record the drift event in `99_delta.md` with Change Type = `Drift`.
+2. Assess impact on all 15 files.
+3. Update affected files and re-validate OQ register exit condition.
+4. If drift contradicts a previously rejected option, record in `99_delta.md` Rejected section with `Recurrence Prevention`.
+
+## Review Gate Artifacts (RCP)
+
+For each review cycle, create:
+
+- `.qfai/review/review-<timestamp>/review_request.md`
+- `.qfai/review/review-<timestamp>/R01_<reviewer>.md`, `R02_<reviewer>.md`, ...
+- `.qfai/review/review-<timestamp>/summary.json`
+
+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.
+- 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.
+- Roster and loop rules must stay synchronized with the footer SSOT.
+
+## Required Coverage Topics
+
+Before completion, confirm all are covered:
+
+1. product concept and target users
+2. scope boundary and anti-goals
+3. user stories and user flows (with Mermaid diagrams)
+4. functional requirements (REQ) with source traceability
+5. non-functional requirements (NFR) with measurable targets
+6. performance constraints and SLO assumptions
+7. security constraints and risk controls
+8. domain glossary consistency
+9. technical and operational constraints
+10. project policies
+
+## Completion Contract (Shared)
+
+Before declaring completion, you MUST:
+
+- verify all 15 mandatory output files exist and are populated;
+- ensure `Disposition: open` count is zero in `11_OQ-Register.md`;
+- ensure every deferred item has full metadata in `13_Deferred.md`;
+- ensure `Example Seeds` sections are present and perspective coverage is explicit in `03_Story-Workshop.md`;
+- ensure `03_Story-Workshop.md` includes at least one Mermaid diagram;
+- avoid duplicating finalized spec content in discussion outputs.
+
+## Evidence (MANDATORY)
+
+Create/update: `.qfai/evidence/discussion-YYYYMMDDhhmmssSSS.md`
+
+Required sections:
+
+- Objective
+- Inputs reviewed (files/paths)
+- Interview summary
+- Inception Deck summary
+- Story Workshop summary
+- Requirements summary (REQ count, NFR count)
+- OQ register summary
+- Deferred summary
+- Work Orders Summary
+- Reviewer result (`PASS`/`REVISE`)
+
+## DONE Declaration (Mandatory Output)
+
+When done, report:
+
+- generated discussion path (`.qfai/discussion/discussion-*/`)
+- open OQ count
+- deferred OQ count
+- REQ count
+- NFR count
+- reviewer result
+- ready-for-next command (`/qfai-sdd`)
+
+## FINAL CHECKLIST (Check Last)
+
+- [ ] CRITICAL CONSTRAINTS were followed.
+- [ ] All 15 required discussion files `01..14, 99` were produced.
+- [ ] OQ register fields follow the mandatory data model (all 11 columns present).
+- [ ] Deferred table fields follow the mandatory data model (all 11 columns present).
+- [ ] `Disposition: open` count is zero at completion.
+- [ ] Deferred items include required metadata.
+- [ ] `03_Story-Workshop.md` includes at least one Mermaid diagram.
+- [ ] Mermaid fence rules were satisfied when diagrams were used.
+- [ ] Evidence file exists and includes Work Orders Summary + Reviewer result.
+- [ ] Reviewer returned `PASS`.
+
+## Completion Checklist (MUST)
+
+- [ ] This skill's Definition of Done is satisfied.
+- [ ] Required artifacts were produced or updated (if applicable).
+- [ ] Diagram artifacts follow Mermaid fence rules (if diagrams were used).
+- [ ] Open questions were logged to the proper OQ file (if applicable).
+- [ ] The completion message was presented to the user.
+- [ ] Next actions were enumerated for all available options.
+
+## Review Cycle Checklist (MUST)
+
+- [ ] Review artifacts were generated for each required discussion review cycle.
+- [ ] All required reviewers completed their reviews for each review pack.
+- [ ] Any feedback triggered return/fix and a new review pack was appended.
+- [ ] `summary.json` satisfies the required schema with `target.kind: "discussion"`.
+
+## Completion Message & Next Actions (MUST)
+
+You MUST end the user-facing output with a handoff sentence to `/qfai-sdd` in the active user language.
+
+- Japanese output (use this exact sentence):
+  ディスカッションが完了しました。他に要望などがあればご提示ください。問題なければ『/qfai-sdd』と入力してください。
+- Non-Japanese output:
+  Use the same meaning in the user's language, and keep `/qfai-sdd` as a literal command token.
+
+- Proceed (recommended): `/qfai-sdd`.
+  Action: run preflight on the latest discussion pack and generate shared/spec artifacts.
+- Upstream idea is still unclear: rerun `/qfai-discussion`.
+  Action: continue discussion loops until OQ states are explicit and complete.
+- Need additional risk analysis before SDD:
+  Action: update `03_Story-Workshop.md` and `11_OQ-Register.md` with additional findings.
+
+````

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/01_Context.md

@@ -0,0 +1,37 @@
+# 01 Context
+
+## Metadata
+
+| Key           | Value                        |
+| ------------- | ---------------------------- |
+| Discussion ID | discussion-YYYYMMDDhhmmssSSS |
+| Date          | YYYY-MM-DD                   |
+| Owner         | <role/person>                |
+| Source        | <request/context>            |
+
+## Goal and Completion Criteria
+
+- Goal:
+- Measurable completion criteria:
+
+## Stakeholders
+
+- Primary stakeholders:
+- Secondary stakeholders:
+
+## Background
+
+- Business context:
+- Technical context:
+- Historical context:
+
+## Inputs
+
+- Existing repository facts:
+- External references:
+- Assumptions:
+
+## Key Issues
+
+- Issue 1:
+- Issue 2:

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/02_Inception-Deck.md

@@ -0,0 +1,64 @@
+# 02 Inception Deck
+
+## 1. Why Are We Here?
+
+- Purpose:
+
+## 2. Elevator Pitch
+
+- For: <target users>
+- Who: <need/problem>
+- The: <product name>
+- Is a: <category>
+- That: <key benefit>
+- Unlike: <alternatives>
+- Our product: <differentiator>
+
+## 3. Product Box (Feature highlights)
+
+- Headline feature 1:
+- Headline feature 2:
+- Headline feature 3:
+
+## 4. NOT List (Out of Scope)
+
+| In Scope | Out of Scope |
+| -------- | ------------ |
+| Item 1   | Item A       |
+
+## 5. Meet Your Neighbors (Stakeholders & Dependencies)
+
+- Upstream dependencies:
+- Downstream dependencies:
+- External integrations:
+
+## 6. Show the Solution (Architecture Overview)
+
+- High-level architecture:
+- Key components:
+
+## 7. What Keeps Us Up at Night (Risks)
+
+| Risk | Probability | Impact | Mitigation |
+| ---- | ----------- | ------ | ---------- |
+| R1   | medium      | high   | TBD        |
+
+## 8. Size It Up (Effort & Timeline)
+
+- Estimated effort:
+- Target timeline:
+
+## 9. What's Going to Give (Trade-offs)
+
+| Dimension | Priority | Notes |
+| --------- | -------- | ----- |
+| Scope     | 1        |       |
+| Quality   | 2        |       |
+| Time      | 3        |       |
+| Budget    | 4        |       |
+
+## 10. What's It Going to Take (Team & Resources)
+
+- Required skills:
+- Team composition:
+- Infrastructure:

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/03_Story-Workshop.md

@@ -0,0 +1,44 @@
+# 03 Story Workshop
+
+## User Stories
+
+### US-001: <Story Title>
+
+- As a: <role>
+- I want: <action>
+- So that: <benefit>
+
+#### Acceptance Criteria
+
+- AC-001-01:
+- AC-001-02:
+
+#### Example Seeds
+
+| Perspective         | Example          | Status |
+| ------------------- | ---------------- | ------ |
+| Happy path          | <example>        | seed   |
+| Negative path       | <example>        | seed   |
+| Edge / boundary     | <example>        | seed   |
+| Permission / role   | <example>        | seed   |
+| State transition    | <example or N/A> | seed   |
+| Idempotency / retry | <example or N/A> | seed   |
+
+## User Flows
+
+```mermaid
+flowchart TD
+    A["Start"] --> B["Action 1"]
+    B --> C{"Decision"}
+    C -->|Yes| D["Action 2"]
+    C -->|No| E["Action 3"]
+    D --> F["End"]
+    E --> F
+```
+
+## Flow Descriptions
+
+- Flow 1:
+  - Entry point:
+  - Steps:
+  - Exit point:

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/04_Sources.md

@@ -0,0 +1,18 @@
+# 04 Sources
+
+## Source Registry
+
+| SRC-ID   | Title | Type    | URL / Path | Retrieved  | Notes |
+| -------- | ----- | ------- | ---------- | ---------- | ----- |
+| SRC-0001 | TBD   | primary | <link>     | YYYY-MM-DD | -     |
+
+## Source Types
+
+- `primary`: First-hand evidence (interviews, documents, code).
+- `secondary`: Derived information (summaries, analyses).
+- `external`: Third-party references (specs, RFCs, vendor docs).
+
+## Traceability
+
+- Each REQ/NFR should reference at least one SRC-ID.
+- Sources without REQ/NFR links should be reviewed for relevance.