qfai 1.1.1 → 1.1.2

package/README.md

@@ -61,6 +61,7 @@ QFAI includes a small set of custom prompts (stored under `.qfai/assistant/promp
 - **qfai-discuss**: Turn an idea into clear requirements by discussing scope, constraints, risks, and open questions.
 - **qfai-require**: Produce `.qfai/require/require.md` from your idea or discussion output.
 - **qfai-spec**: Produce `.qfai/specs/*` and `.qfai/contracts/*` from the requirements, including traceability scaffolding.
+  - Includes a preflight step that bootstraps missing `qfai.config.yaml` and `assistant/steering/*` when run directly after init.
 - **qfai-scenario-test**: Implement acceptance tests (ATDD) driven by specs/scenarios.
 - **qfai-unit-test**: Implement unit tests (TDD) driven by specs/scenarios.
 - **qfai-implement**: Implement the feature; iterate test→fix until all quality gates are green.
@@ -97,6 +98,7 @@ AG->>R: Create/Update requirements docs
 AG-->>U: Requirements ready
 
 U->>AG: Run /qfai-spec
+Note over U,AG: /qfai-spec performs a preflight to converge config/steering when /qfai-configure is skipped.
 AG->>Q: Read .qfai/assistant/prompts/qfai-spec.md
 AG->>R: Create specs + contracts + scenario.feature
 AG-->>U: SDD artifacts ready

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

@@ -22,6 +22,9 @@ mode: evidence-focused
 
 Analyze the repository and update `qfai.config.yaml` so QFAI traceability checks (especially SC->Test) are actionable without manual tuning, and optionally tune required spec sections if requested.
 
+Note: /qfai-spec includes a preflight step that bootstraps missing config/steering when run directly after init.
+/qfai-configure remains the recommended way to tune `qfai.config.yaml` early with a clean, minimal diff.
+
 ## Success Criteria (Definition of Done)
 
 - `qfai.config.yaml` is updated with a **minimal diff** focused on traceability globs.

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

@@ -133,28 +133,61 @@ Before producing any deliverable, **thoroughly analyze the current project** so
 
 If analysis cannot be performed (missing access), clearly state what could not be verified and proceed with minimal-risk assumptions.
 
-## Step 0.5 — Steering Bootstrap / Refresh (mandatory when incomplete)
+## Step 0.4 — Preflight: Config + Steering convergence (mandatory)
 
-QFAI expects `assistant/steering/` to contain **project‑specific facts** so all subsequent design/test/implementation fits this repository.
+QFAI prompt operations are flexible. In some workflows, the user may run **/qfai-spec directly after init** without running /qfai-configure.
+Therefore, /qfai-spec MUST converge the workspace into a usable state before writing spec packs.
 
-### What to do
+### Preflight goals
 
-1. Open these files:
+- Ensure `qfai.config.yaml` exists and is schema-valid.
+- Ensure `validation.traceability.testFileGlobs` is not empty and not obviously zero-match.
+- Ensure `assistant/steering/*` is populated to a usable level.
 
-- `.qfai/assistant/steering/product.md`
-- `.qfai/assistant/steering/tech.md`
-- `.qfai/assistant/steering/structure.md`
+### Steering completion levels (definition)
 
-2. If they are missing, mostly empty, or still have placeholders (e.g., `- ` only), **populate them by analyzing the current repository**:
+- L0: files exist
+- L1: format skeleton is present (headings / minimum sections)
+- L2: evidence-based repo facts are filled
+- L3: human-judgment areas are marked as TBD/OQ and impact is reflected in spec outputs
+- L4: human-judgment areas are confirmed
 
-- derive “what/why/users/success/non-goals” from README/docs/issues (product.md)
-- derive runtime/tooling versions + constraints from package.json, CI config, lockfiles (tech.md)
-- derive repo layout + key directories + gate commands from the file tree and scripts (structure.md)
+Target for /qfai-spec preflight: **L2-L3**.
 
-3. Do **not** invent facts. If something cannot be verified, write it as:
+### 0.4-A Ensure qfai.config.yaml
 
-- `TBD` + what evidence is missing, or
-- an Open Question (if it blocks correctness)
+1. If `qfai.config.yaml` does not exist:
+
+- Create a schema-valid minimal config.
+- Derive reasonable `validation.traceability.testFileGlobs` from repo evidence (package.json, test configs, file tree).
+
+2. If it exists:
+
+- Validate the structure (do not invent keys).
+- If clearly broken (missing required keys / invalid YAML), do a minimal repair OR record an Open Question and proceed with the safest assumptions.
+
+### 0.4-B Converge traceability globs
+
+- If `validation.traceability.testFileGlobs` is empty OR it matches 0 test files:
+  - Run a lightweight "configure" procedure:
+    - inspect test runner config and conventions
+    - propose 3-10 include globs
+    - add exclude globs only when needed
+    - update `qfai.config.yaml` with a minimal diff
+
+- Evidence requirement:
+  - Always sample 5-15 matched test files and include them in the output.
+
+### 0.4-C Steering bootstrap/refresh
+
+- Open these files:
+  - `.qfai/assistant/steering/product.md`
+  - `.qfai/assistant/steering/tech.md`
+  - `.qfai/assistant/steering/structure.md`
+
+- If missing/empty/placeholder:
+  - Fill the evidence-based parts from repo docs and configs.
+  - Never invent facts. Use `TBD` + missing evidence, or Open Questions.
 
 ### Steering refresh checklist
 
@@ -162,6 +195,16 @@ QFAI expects `assistant/steering/` to contain **project‑specific facts** so al
 - [ ] tech.md: Node / package manager / TS / test / lint / CI constraints
 - [ ] structure.md: repo layout, key packages, entrypoints, standard gate commands, how to run locally
 
+### Preflight output contract
+
+Your final response MUST include:
+
+- Whether preflight changed any files (and which ones)
+- Why changes were needed
+- Evidence samples (matched test files, referenced repo docs)
+- Remaining TBD / Open Questions (blocking vs non-blocking)
+- A short "Preflight summary" (max 10 lines), followed by details
+
 ## Step 1 — Determine spec pack identity
 
 If the user does not provide an ID:

package/dist/cli/index.cjs

@@ -1067,8 +1067,8 @@ var import_promises7 = require("fs/promises");
 var import_node_path9 = __toESM(require("path"), 1);
 var import_node_url2 = require("url");
 async function resolveToolVersion() {
-  if ("1.1.1".length > 0) {
-    return "1.1.1";
+  if ("1.1.2".length > 0) {
+    return "1.1.2";
   }
   try {
     const packagePath = resolvePackageJsonPath();

package/dist/cli/index.mjs

@@ -1048,8 +1048,8 @@ import { readFile as readFile4 } from "fs/promises";
 import path9 from "path";
 import { fileURLToPath as fileURLToPath2 } from "url";
 async function resolveToolVersion() {
-  if ("1.1.1".length > 0) {
-    return "1.1.1";
+  if ("1.1.2".length > 0) {
+    return "1.1.2";
   }
   try {
     const packagePath = resolvePackageJsonPath();

package/dist/index.cjs

@@ -1699,8 +1699,8 @@ var import_promises8 = require("fs/promises");
 var import_node_path9 = __toESM(require("path"), 1);
 var import_node_url = require("url");
 async function resolveToolVersion() {
-  if ("1.1.1".length > 0) {
-    return "1.1.1";
+  if ("1.1.2".length > 0) {
+    return "1.1.2";
   }
   try {
     const packagePath = resolvePackageJsonPath();

package/dist/index.mjs

@@ -1639,8 +1639,8 @@ import { readFile as readFile5 } from "fs/promises";
 import path9 from "path";
 import { fileURLToPath } from "url";
 async function resolveToolVersion() {
-  if ("1.1.1".length > 0) {
-    return "1.1.1";
+  if ("1.1.2".length > 0) {
+    return "1.1.2";
   }
   try {
     const packagePath = resolvePackageJsonPath();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qfai",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "description": "Quality-first AI-driven development toolkit (SDD × ATDD × TDD).",
   "license": "MIT",
   "repository": {