qfai 1.0.5 → 1.0.7

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

@@ -0,0 +1,27 @@
+---
+id: quality
+category: universal
+update_frequency: occasional
+---
+
+# Quality (Gates, tests, and safety)
+
+## Quality gates (baseline)
+
+When code changes are requested, the expected minimum gates are:
+
+- `pnpm format:check`
+- `pnpm lint`
+- `pnpm check-types`
+- `pnpm test`
+- `pnpm verify:pack` (when publishing/distribution matters)
+
+## Do not weaken safety nets
+
+- Do not suppress or disable checks via inline ignores unless explicitly approved.
+- If a rule must be changed, justify with evidence and update tests/docs accordingly.
+
+## Testing expectations
+
+- Prefer adding/adjusting tests over weakening validation.
+- Keep outputs deterministic (avoid time/randomness).

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

@@ -0,0 +1,29 @@
+---
+id: thinking
+category: universal
+update_frequency: rare
+---
+
+# Thinking (Evidence-first, ambiguity elimination)
+
+## Principles
+
+- Prefer **repo evidence** over assumptions (file paths, configs, tests, commands).
+- If something cannot be verified, write `TBD` and raise an Open Question (what evidence is missing).
+- Minimize ambiguity: define terms, scope, and measurable acceptance criteria.
+
+## Working method
+
+1. Restate the goal and constraints (brief).
+2. Enumerate unknowns and assumptions.
+3. Identify the evidence to check (files/commands).
+4. Decide with a rationale grounded in evidence.
+5. Record residual risk and the rollback path.
+
+## When to stop and ask
+
+Stop and ask the user if:
+
+- required inputs are missing (e.g., target behavior, API shape, UX intent),
+- multiple interpretations are plausible and impact is material,
+- a change could be breaking and intent is unclear.

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

@@ -10,10 +10,10 @@ Rule:
 Files:
 
 - qfai-discuss.md (optional)
+- qfai-configure.md (run after init; updates qfai.config.yaml testFileGlobs; outputs updated YAML + validation checklist)
 - qfai-require.md
 - qfai-spec.md
 - qfai-scenario-test.md
 - qfai-unit-test.md
 - qfai-implement.md
 - qfai-verify.md
-- qfai-pr.md (optional)

package/assets/init/.qfai/assistant/prompts/qfai-configure.md

@@ -0,0 +1,174 @@
+<!--
+QFAI Prompt Body (SSOT)
+- This file is intended to be referenced by tool-specific custom prompt definitions (e.g., Copilot .prompt.md, Claude Code slash commands).
+- Keep tool-specific wrappers thin: "Read this file and follow it."
+-->
+
+---
+
+id: qfai-configure
+title: QFAI Configure (Tune qfai.config.yaml)
+description: "Analyze the repository and tune qfai.config.yaml (testFileGlobs, exclude globs)."
+argument-hint: "[--auto]"
+allowed-tools: [Read, Glob, Write, TodoWrite, Task]
+roles: [DevOpsCIEngineer, QAEngineer, CodeReviewer, Planner]
+mode: evidence-focused
+
+---
+
+# /qfai-configure - Configure QFAI for this repository
+
+## Purpose
+
+Analyze the repository and update `qfai.config.yaml` so QFAI traceability checks (especially SC->Test) are actionable without manual tuning.
+
+## Success Criteria (Definition of Done)
+
+- `qfai.config.yaml` is updated with a **minimal diff** focused on traceability globs.
+- `validation.traceability.testFileGlobs` reflects the real test layout.
+- `validation.traceability.testFileExcludeGlobs` is added only when needed.
+- A validation checklist with evidence (sample matched files) is produced.
+
+## Non-Negotiable Principles (QFAI Articles)
+
+These principles are inspired by "constitution / articles" patterns used by other agent frameworks, but tailored to QFAI.
+
+1. **SDD First (Specification is the source of truth)**  
+   If there is a conflict between code and spec, treat the spec as authoritative and either (a) fix code or (b) raise an explicit Open Question to change the spec.
+
+2. **Traceability is mandatory**  
+   Every meaningful change must be traceable: **Require -> Spec -> Scenario -> Tests -> Code -> Verification evidence**.
+
+3. **Evidence over confidence**  
+   Prefer observable proof (logs, commands, file diffs, test results). If you cannot verify, say so and record it.
+
+4. **Minimize scope, but never hide gaps**  
+   Keep changes minimal, but do not "paper over" missing decisions. If something blocks correctness, stop and ask.
+
+5. **Quality gates are the decision mechanism**  
+   Use tests/lint/typecheck/build/pack verification (whatever the repo defines) as the primary guardrail. Fix until PASS.
+
+6. **Make it runnable**  
+   Outputs must be executable in terminal/CI. Provide copy-paste commands.
+
+7. **User time is expensive**  
+   Ask only the questions that are truly blocking. Everything else: make reasonable assumptions and label them clearly.
+
+## Absolute Rule - Output Language
+
+**All outputs MUST be written in the user's working language for this session.**
+
+- If the user writes in Japanese, output Japanese.
+- If the user writes in English, output English.
+- If the user mixes languages, prefer the dominant language unless explicitly instructed otherwise.  
+  This rule overrides all other stylistic preferences.
+
+## Multi-Role Orchestration (Subagents)
+
+This workflow assumes the environment _may_ support subagents (e.g., Claude Code "Task" tool) or may not.
+
+### If subagents are supported
+
+Delegate to multiple roles and then merge the results. Use a "real-world workflow" order:
+
+- Facilitator -> Interviewer -> Requirements Analyst -> Planner -> Architect -> (Contract Designer) -> Test Engineer -> QA Engineer -> Code Reviewer -> DevOps/CI Engineer
+
+**Pseudo-invocation pattern** (adjust to your tool):
+
+```text
+Task(
+  subagent_type="planner",
+  description="Analyze repo and propose testFileGlobs",
+  prompt="Context: ...\nGoal: Tune qfai.config.yaml\nConstraints: minimal diff\nReturn: globs + evidence"
+)
+```
+
+### If subagents are NOT supported
+
+Simulate roles by running the same sequence yourself:
+
+- Write a short "role output" section per role, then consolidate into the final deliverable(s).
+
+## Constraints
+
+- Only update `qfai.config.yaml` unless explicitly asked.
+- Do **not** modify tests or source code.
+- Avoid overly broad globs (e.g., `**/*`).
+- Exclude generated/output directories (`node_modules`, `.git`, `.qfai`, `dist`, `build`, `coverage`, `.next`, `out`, etc.).
+
+## Step 0 - Load Context (always)
+
+1. Read relevant **project steering** (if present):
+   - `.qfai/assistant/steering/structure.md`
+   - `.qfai/assistant/steering/tech.md`
+   - `.qfai/assistant/steering/product.md`
+   - any additional files under `.qfai/assistant/steering/`
+
+2. Read **project constitution / instructions** (if present):
+   - `.qfai/assistant/instructions/constitution.md`
+   - `.qfai/assistant/instructions/workflow.md` (or equivalent)
+
+3. Inspect repo conventions:
+   - package manager (pnpm/npm/yarn), test runner, lint/typecheck scripts, CI definitions
+   - existing test patterns (unit/integration/e2e)
+
+## Step 0 - Project Analysis (mandatory)
+
+Before editing config, **thoroughly analyze the current project**:
+
+- background and goals
+- directory structure and conventions
+- chosen technologies and versions (runtime, package manager, test runner)
+- test locations (unit/integration/e2e)
+- existing test naming rules (`*.test.*`, `*.spec.*`, `*_test.*`, etc.)
+
+If analysis cannot be performed (missing access), clearly state what could not be verified and proceed with minimal-risk assumptions.
+
+## Step 1 - Identify test frameworks and locations
+
+1. Inspect `package.json` and config files (e.g., `vitest.config.*`, `jest.config.*`, `playwright.config.*`, `pytest.ini`, `go.mod`).
+2. Enumerate directories that contain tests (e.g., `tests/`, `src/`, `e2e/`, `integration/`).
+3. Note naming rules and extensions that indicate test files.
+
+## Step 2 - Propose glob patterns
+
+Provide 3-10 **include globs** that cover all known test locations:
+
+- Prefer explicit patterns (e.g., `src/**/*.test.ts`, `tests/**/*.spec.ts`).
+- Include src-colocated tests if they exist.
+
+Provide **exclude globs** only when necessary (beyond the default exclusions).
+
+## Step 3 - Update `qfai.config.yaml` (minimal diff)
+
+Edit:
+
+- `validation.traceability.testFileGlobs`
+- `validation.traceability.testFileExcludeGlobs` (only if needed)
+
+Keep all other config keys unchanged.
+
+## Step 4 - Evidence sampling
+
+Sample 5-15 actual test files that match the proposed globs.
+
+- If zero matches exist, stop and ask for clarification.
+- If some directories are ambiguous, list them as Open Questions.
+
+## Checkpoints
+
+- [ ] Repository analysis completed (frameworks, test layout, naming rules).
+- [ ] Proposed include/exclude globs with rationale.
+- [ ] `qfai.config.yaml` updated (minimal diff).
+- [ ] Evidence: sample matched files listed.
+
+## Output
+
+Provide:
+
+1. Updated `qfai.config.yaml` (diff or full file, as appropriate).
+2. A short summary of changes and rationale.
+3. Validation checklist with sampled files.
+4. Open questions (blocking vs non-blocking).
+
+Suggest next step: `/qfai-require` (or `/qfai-discuss` if requirements are not ready).

package/assets/init/.qfai/assistant/prompts/qfai-implement.md

@@ -89,15 +89,6 @@ Simulate roles by running the same sequence yourself:
 
 - Write a short “role output” section per role, then consolidate into the final deliverable(s).
 
-## Behavior Rules (high leverage)
-
-- **Language**: Output MUST follow the user’s working language for this session.
-- **Question budget**: Ask at most **5** clarifying questions total. Prioritize blockers. If `--auto`, proceed with explicit assumptions.
-- **No hallucination**: Do not invent file paths, commands, or policies. Confirm via repo inspection.
-- **Evidence**: Do not claim completion without commands/results (format/lint/type/test/pack as applicable).
-- **Subagent contract**: When delegating, require the subagent response structure:
-  1. Findings 2) Recommendations 3) Proposed edits 4) Open Questions/Risks 5) Confidence
-
 ## Step 0 — Load Context (always)
 
 1. Read relevant **project steering** (if present):

package/assets/init/.qfai/assistant/prompts/qfai-pr.md

@@ -92,15 +92,6 @@ Simulate roles by running the same sequence yourself:
 
 - Write a short “role output” section per role, then consolidate into the final deliverable(s).
 
-## Behavior Rules (high leverage)
-
-- **Language**: Output MUST follow the user’s working language for this session.
-- **Question budget**: Ask at most **5** clarifying questions total. Prioritize blockers. If `--auto`, proceed with explicit assumptions.
-- **No hallucination**: Do not invent file paths, commands, or policies. Confirm via repo inspection.
-- **Evidence**: Do not claim completion without commands/results (format/lint/type/test/pack as applicable).
-- **Subagent contract**: When delegating, require the subagent response structure:
-  1. Findings 2) Recommendations 3) Proposed edits 4) Open Questions/Risks 5) Confidence
-
 ## Step 0 — Load Context (always)
 
 1. Read relevant **project steering** (if present):

package/assets/init/.qfai/assistant/prompts/qfai-require.md

@@ -88,15 +88,6 @@ Simulate roles by running the same sequence yourself:
 
 - Write a short “role output” section per role, then consolidate into the final deliverable(s).
 
-## Behavior Rules (high leverage)
-
-- **Language**: Output MUST follow the user’s working language for this session.
-- **Question budget**: Ask at most **5** clarifying questions total. Prioritize blockers. If `--auto`, proceed with explicit assumptions.
-- **No hallucination**: Do not invent file paths, commands, or policies. Confirm via repo inspection.
-- **Evidence**: Do not claim completion without commands/results (format/lint/type/test/pack as applicable).
-- **Subagent contract**: When delegating, require the subagent response structure:
-  1. Findings 2) Recommendations 3) Proposed edits 4) Open Questions/Risks 5) Confidence
-
 ## Step 0 — Load Context (always)
 
 1. Read relevant **project steering** (if present):

package/assets/init/.qfai/assistant/prompts/qfai-scenario-test.md

@@ -88,15 +88,6 @@ Simulate roles by running the same sequence yourself:
 
 - Write a short “role output” section per role, then consolidate into the final deliverable(s).
 
-## Behavior Rules (high leverage)
-
-- **Language**: Output MUST follow the user’s working language for this session.
-- **Question budget**: Ask at most **5** clarifying questions total. Prioritize blockers. If `--auto`, proceed with explicit assumptions.
-- **No hallucination**: Do not invent file paths, commands, or policies. Confirm via repo inspection.
-- **Evidence**: Do not claim completion without commands/results (format/lint/type/test/pack as applicable).
-- **Subagent contract**: When delegating, require the subagent response structure:
-  1. Findings 2) Recommendations 3) Proposed edits 4) Open Questions/Risks 5) Confidence
-
 ## Step 0 — Load Context (always)
 
 1. Read relevant **project steering** (if present):

package/assets/init/.qfai/assistant/prompts/qfai-spec.md

@@ -91,15 +91,6 @@ Simulate roles by running the same sequence yourself:
 
 - Write a short “role output” section per role, then consolidate into the final deliverable(s).
 
-## Behavior Rules (high leverage)
-
-- **Language**: Output MUST follow the user’s working language for this session.
-- **Question budget**: Ask at most **5** clarifying questions total. Prioritize blockers. If `--auto`, proceed with explicit assumptions.
-- **No hallucination**: Do not invent file paths, commands, or policies. Confirm via repo inspection.
-- **Evidence**: Do not claim completion without commands/results (format/lint/type/test/pack as applicable).
-- **Subagent contract**: When delegating, require the subagent response structure:
-  1. Findings 2) Recommendations 3) Proposed edits 4) Open Questions/Risks 5) Confidence
-
 ## Step 0 — Load Context (always)
 
 1. Read relevant **project steering** (if present):
@@ -262,7 +253,20 @@ Only create contracts when the spec requires a stable interface definition.
 
 If your repo defines contract schema or naming rules, follow them. Otherwise:
 
-- Use a clear filename and include “Purpose / Fields / Constraints / Examples” inside the YAML as comments.
+- **UI / API contracts:** write **YAML** and include “Purpose / Fields / Constraints / Examples” as YAML comments.
+- **DB contracts:** write **SQL (`.sql`)** and include a small header comment block, then representative DDL/schema notes.
+
+DB contract default conventions (unless your repo defines others):
+
+- Filename: `db-0001-<slug>.sql`
+- Header (must):
+  ```sql
+  -- QFAI-CONTRACT-ID: DB-0001
+  -- Purpose: <what this schema contract guarantees>
+  -- Constraints: <keys, nullability, ranges, invariants>
+  -- Examples: <optional example rows or queries>
+  ```
+- Body: DDL or schema notes that tests/scenarios can validate (minimal, spec-driven).
 
 ## Step 4 — QA + Review
 

package/assets/init/.qfai/assistant/prompts/qfai-unit-test.md

@@ -88,15 +88,6 @@ Simulate roles by running the same sequence yourself:
 
 - Write a short “role output” section per role, then consolidate into the final deliverable(s).
 
-## Behavior Rules (high leverage)
-
-- **Language**: Output MUST follow the user’s working language for this session.
-- **Question budget**: Ask at most **5** clarifying questions total. Prioritize blockers. If `--auto`, proceed with explicit assumptions.
-- **No hallucination**: Do not invent file paths, commands, or policies. Confirm via repo inspection.
-- **Evidence**: Do not claim completion without commands/results (format/lint/type/test/pack as applicable).
-- **Subagent contract**: When delegating, require the subagent response structure:
-  1. Findings 2) Recommendations 3) Proposed edits 4) Open Questions/Risks 5) Confidence
-
 ## Step 0 — Load Context (always)
 
 1. Read relevant **project steering** (if present):

package/assets/init/.qfai/assistant/prompts/qfai-verify.md

@@ -88,15 +88,6 @@ Simulate roles by running the same sequence yourself:
 
 - Write a short “role output” section per role, then consolidate into the final deliverable(s).
 
-## Behavior Rules (high leverage)
-
-- **Language**: Output MUST follow the user’s working language for this session.
-- **Question budget**: Ask at most **5** clarifying questions total. Prioritize blockers. If `--auto`, proceed with explicit assumptions.
-- **No hallucination**: Do not invent file paths, commands, or policies. Confirm via repo inspection.
-- **Evidence**: Do not claim completion without commands/results (format/lint/type/test/pack as applicable).
-- **Subagent contract**: When delegating, require the subagent response structure:
-  1. Findings 2) Recommendations 3) Proposed edits 4) Open Questions/Risks 5) Confidence
-
 ## Step 0 — Load Context (always)
 
 1. Read relevant **project steering** (if present):

package/assets/init/.qfai/assistant/prompts.local/README.md

@@ -4,3 +4,5 @@ Optional per-project overrides.
 
 If a file with the same name exists here (e.g., `qfai-spec.md`), a tool wrapper may prefer it to customize behavior for this repo.
 Keep overrides minimal; prefer updating steering/instructions instead.
+
+Note: After `qfai init`, this folder contains only this README. Place an override file here only when you intentionally diverge from the SSOT prompt bodies.

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

@@ -31,3 +31,10 @@ Steering MUST be grounded in repo evidence. When possible, include:
 - directory anchors (e.g., `packages/qfai/src/cli`)
 
 If a fact cannot be verified, mark it as `TBD` and record what evidence is missing.
+
+### Default AI-managed flow (recommended)
+
+1. Run a QFAI command (e.g., `/qfai-require`, `/qfai-spec`, `/qfai-implement`).
+2. The agent loads `steering/*` and fills missing placeholders from **repo evidence**.
+3. If evidence is missing, write `TBD` and add an Open Question (what evidence is required).
+4. Optionally, review changes via PR if your team requires human approval.

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

@@ -6,6 +6,6 @@ Subfolders:
 
 - `ui/` : UI contracts (YAML)
 - `api/`: API contracts (YAML)
-- `db/` : DB contracts (YAML)
+- `db/` : DB contracts (SQL / .sql)
 
 Create contracts only when needed by the spec (keep minimal).

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

@@ -1,8 +1,25 @@
 # contracts/db/
 
-Place DB contracts here (YAML).
+Place **DB contracts** here as **SQL DDL files** (`.sql`).
 
-Guidelines:
+## File naming
 
-- Keep contracts minimal: define only what scenarios/tests need to validate.
-- Include examples where helpful.
+- `db-0001-<slug>.sql`
+  - Contract ID: `DB-0001` (4-digit fixed)
+
+## Required header
+
+Include the contract ID in the SQL header comments so QFAI can discover/index it:
+
+```sql
+-- QFAI-CONTRACT-ID: DB-0001
+-- DB-0001 (short description)
+```
+
+## Guidelines
+
+- Keep DB contracts minimal and spec-driven (only what scenarios/tests need).
+- This directory is for the **contract/schema snapshot**, not migrations history.
+- If your project uses an ORM schema (Prisma, etc.), decide one:
+  - (Recommended for v1.0.6) Keep a minimal `.sql` contract snapshot here, and link to the real schema in the spec.
+  - (Future) Add support for other schema formats via config (out of scope for v1.0.6).

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

@@ -7,3 +7,5 @@ A **spec pack** lives under `specs/spec-XXXX/` and contains:
 - `scenario.feature` : Gherkin scenarios (ATDD skeleton)
 
 Create/update spec packs with `/qfai-spec`.
+
+Note: After `qfai init`, this folder contains only this README. Spec packs (`spec-XXXX/`) are created by running `/qfai-spec`.

package/assets/init/root/.claude/commands/qfai-configure.md

@@ -0,0 +1,14 @@
+---
+description: "QFAI: Configure qfai.config.yaml based on the repository"
+argument-hint: "[optional notes]"
+---
+
+Follow the canonical QFAI prompt exactly:
+@.qfai/assistant/prompts/qfai-configure.md
+
+Follow the DoD/Checkpoints in the prompt.
+Use the repository as the source of truth.
+
+Additional user notes: $ARGUMENTS
+
+Critical: output must match the user's language.

package/assets/init/root/.claude/commands/qfai-discuss.md

@@ -0,0 +1,14 @@
+---
+description: "QFAI: Discuss an idea and clarify requirements"
+argument-hint: "[optional notes]"
+---
+
+Follow the canonical QFAI prompt exactly:
+@.qfai/assistant/prompts/qfai-discuss.md
+
+Follow the DoD/Checkpoints in the prompt.
+Use the repository as the source of truth.
+
+Additional user notes: $ARGUMENTS
+
+Critical: output must match the user's language.

package/assets/init/root/.claude/commands/qfai-implement.md

@@ -0,0 +1,14 @@
+---
+description: "QFAI: Implement code changes with tests"
+argument-hint: "[optional notes]"
+---
+
+Follow the canonical QFAI prompt exactly:
+@.qfai/assistant/prompts/qfai-implement.md
+
+Follow the DoD/Checkpoints in the prompt.
+Use the repository as the source of truth.
+
+Additional user notes: $ARGUMENTS
+
+Critical: output must match the user's language.

package/assets/init/root/.claude/commands/qfai-require.md

@@ -0,0 +1,14 @@
+---
+description: "QFAI: Create requirements artifacts"
+argument-hint: "[optional notes]"
+---
+
+Follow the canonical QFAI prompt exactly:
+@.qfai/assistant/prompts/qfai-require.md
+
+Follow the DoD/Checkpoints in the prompt.
+Use the repository as the source of truth.
+
+Additional user notes: $ARGUMENTS
+
+Critical: output must match the user's language.

package/assets/init/root/.claude/commands/qfai-scenario-test.md

@@ -0,0 +1,14 @@
+---
+description: "QFAI: Implement acceptance tests from scenarios"
+argument-hint: "[optional notes]"
+---
+
+Follow the canonical QFAI prompt exactly:
+@.qfai/assistant/prompts/qfai-scenario-test.md
+
+Follow the DoD/Checkpoints in the prompt.
+Use the repository as the source of truth.
+
+Additional user notes: $ARGUMENTS
+
+Critical: output must match the user's language.

package/assets/init/root/.claude/commands/qfai-spec.md

@@ -0,0 +1,14 @@
+---
+description: "QFAI: Create specs, contracts, and scenarios"
+argument-hint: "[optional notes]"
+---
+
+Follow the canonical QFAI prompt exactly:
+@.qfai/assistant/prompts/qfai-spec.md
+
+Follow the DoD/Checkpoints in the prompt.
+Use the repository as the source of truth.
+
+Additional user notes: $ARGUMENTS
+
+Critical: output must match the user's language.

package/assets/init/root/.claude/commands/qfai-unit-test.md

@@ -0,0 +1,14 @@
+---
+description: "QFAI: Implement unit tests from specs/scenarios"
+argument-hint: "[optional notes]"
+---
+
+Follow the canonical QFAI prompt exactly:
+@.qfai/assistant/prompts/qfai-unit-test.md
+
+Follow the DoD/Checkpoints in the prompt.
+Use the repository as the source of truth.
+
+Additional user notes: $ARGUMENTS
+
+Critical: output must match the user's language.

package/assets/init/root/.claude/commands/qfai-verify.md

@@ -0,0 +1,14 @@
+---
+description: "QFAI: Run quality gates and produce evidence"
+argument-hint: "[optional notes]"
+---
+
+Follow the canonical QFAI prompt exactly:
+@.qfai/assistant/prompts/qfai-verify.md
+
+Follow the DoD/Checkpoints in the prompt.
+Use the repository as the source of truth.
+
+Additional user notes: $ARGUMENTS
+
+Critical: output must match the user's language.

package/assets/init/root/.codex/README.md

@@ -0,0 +1,16 @@
+# QFAI Codex skills
+
+This directory provides thin Codex skill wrappers for QFAI prompts.
+
+## Canonical prompts
+
+The source of truth is always the prompt body under:
+
+- .qfai/assistant/prompts/
+
+If there is any mismatch, the canonical `.qfai` prompt wins.
+
+## Usage
+
+In Codex CLI, select a skill by name (e.g., `qfai-configure`) and provide your request.
+All outputs must match the user's language.

package/assets/init/root/.codex/skills/qfai-configure/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: qfai-configure
+description: QFAI: Configure qfai.config.yaml based on the repository
+---
+
+This skill is a thin wrapper that forwards to the canonical QFAI prompt in this repository:
+
+- .qfai/assistant/prompts/qfai-configure.md
+
+How to invoke (Codex CLI):
+
+- Select the `qfai-configure` skill, or reference it by name and provide your request.
+
+Instructions:
+
+1. Read the prompt above and follow it precisely.
+2. Use the repository as the source of truth (tools, frameworks, directory structure).
+3. Ensure all outputs match the user's language.

package/assets/init/root/.codex/skills/qfai-discuss/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: qfai-discuss
+description: QFAI: Discuss an idea and clarify requirements
+---
+
+This skill is a thin wrapper that forwards to the canonical QFAI prompt in this repository:
+
+- .qfai/assistant/prompts/qfai-discuss.md
+
+How to invoke (Codex CLI):
+
+- Select the `qfai-discuss` skill, or reference it by name and provide your request.
+
+Instructions:
+
+1. Read the prompt above and follow it precisely.
+2. Use the repository as the source of truth (tools, frameworks, directory structure).
+3. Ensure all outputs match the user's language.

package/assets/init/root/.codex/skills/qfai-implement/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: qfai-implement
+description: QFAI: Implement code changes with tests
+---
+
+This skill is a thin wrapper that forwards to the canonical QFAI prompt in this repository:
+
+- .qfai/assistant/prompts/qfai-implement.md
+
+How to invoke (Codex CLI):
+
+- Select the `qfai-implement` skill, or reference it by name and provide your request.
+
+Instructions:
+
+1. Read the prompt above and follow it precisely.
+2. Use the repository as the source of truth (tools, frameworks, directory structure).
+3. Ensure all outputs match the user's language.