bmad-module-skill-forge 1.4.1 → 1.5.1

package/src/skf-refine-architecture/steps-c/step-01-init.md

@@ -1,136 +0,0 @@
----
-nextStepFile: './step-02-gap-analysis.md'
-refinementRulesData: 'references/refinement-rules.md'
----
-
-# Step 1: Initialize Refinement
-
-## STEP GOAL:
-
-Load the architecture document (required), scan the skills folder to build a skill inventory with metadata, load the optional VS feasibility report for context, validate that all inputs exist and meet minimum requirements, and present an initialization summary before auto-proceeding.
-
-## Rules
-
-- Focus only on loading inputs, scanning skills, and validating prerequisites — do not perform analysis
-- Present a clear initialization summary so downstream steps have validated inputs
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-### 1. Accept Input Documents
-
-"**Refine Architecture — Evidence-Backed Refinement**
-
-Please provide the following:
-1. **Architecture document path** (REQUIRED) — your project's architecture doc to refine
-2. **VS feasibility report path** (OPTIONAL) — from a previous [VS] Verify Stack run, for additional context"
-
-Wait for user input. Store the validated architecture document path as `architecture_doc`. **GATE [default: use args]** — If `{headless_mode}` and architecture doc path was provided as argument: use that path and auto-proceed, log: "headless: using provided architecture path".
-
-**Validate architecture document:**
-- Confirm the file exists and is readable
-- If missing or unreadable: "Architecture document not found at `{path}`. Provide a valid path."
-- HALT until a valid architecture document is provided
-
-**Validate VS report (if provided):**
-- Confirm the file exists and is readable
-- If missing at user-provided path: attempt auto-probe (below) before giving up
-- Store VS report availability as `vs_report_available: true|false` and `vs_report_path`
-
-### 2. Scan Skills Folder
-
-Read the `{skills_output_folder}` directory. Skills use a version-nested directory structure (see `knowledge/version-paths.md`).
-
-**Version-aware skill discovery:**
-1. Read `{skills_output_folder}/.export-manifest.json` if it exists. For each skill in `exports`, use `active_version` to resolve `{skill_package}` = `{skills_output_folder}/{skill-name}/{active_version}/{skill-name}/`
-2. For any subdirectory not covered by the manifest, check for an `active` symlink at `{skills_output_folder}/{dir_name}/active` — resolve to `{skill_group}/active/{dir_name}/`
-3. Fall back to flat path `{skills_output_folder}/{dir_name}/` for unmigrated skills
-
-For each resolved skill package, check for the presence of `SKILL.md` and `metadata.json`.
-
-**For each valid skill directory, extract from metadata.json:**
-- `name` — skill name
-- `language` — primary language
-- `confidence_tier` — Quick, Forge, Forge+, or Deep
-- `exports_documented` — read from `stats.exports_documented` in metadata.json (count of documented exports)
-- `source_repo` or `source_root` — original source repository
-
-**Build a skill inventory** as an internal list of all loaded skills with the fields above.
-
-**If a resolved skill package lacks SKILL.md or metadata.json:**
-- Log: "Skipping `{dir_name}` — missing SKILL.md or metadata.json"
-- Do not include in inventory
-
-### 3. Validate Minimum Requirements
-
-**Check skill count:**
-- At least 1 valid skill must exist
-- If no skills found: "**Cannot proceed.** No skills found in `{skills_output_folder}`. Generate skills with [CS] Create Skill or [QS] Quick Skill, then re-run [RA]."
-- HALT workflow
-- If exactly 1 valid skill found: "⚠️ Proceeding with 1 skill. Note: gap analysis will find no gaps — pairwise analysis requires at least 2 skills. Step 02 will still execute and issue an appropriate notice. Issue detection and improvement detection will proceed normally."
-
-**Check output_folder:**
-- Verify `output_folder` was resolved from config.yaml and is non-empty
-- If undefined or empty: "**Cannot proceed.** `output_folder` is not configured in config.yaml. Add an `output_folder` path and re-run [RA]."
-- HALT workflow
-- Verify the `output_folder` directory exists. If it does not exist, create it. HALT with error if creation fails.
-
-**Check forge_data_folder:**
-- Verify `forge_data_folder` was resolved from config.yaml and is non-empty
-- If undefined or empty: "**Cannot proceed.** `forge_data_folder` is not configured in config.yaml. Add a `forge_data_folder` path to your config.yaml and re-run [RA]."
-- HALT workflow
-- Verify the `forge_data_folder` directory exists. If it does not exist, attempt to create it. If creation fails: "**Cannot proceed.** `forge_data_folder` at `{forge_data_folder}` does not exist and could not be created. Create the directory manually and re-run [RA]."
-- HALT workflow on creation failure
-
-**Check architecture document:**
-- Confirm it was loaded successfully in section 1
-- If not: HALT with error (should not reach here if section 1 validation passed)
-
-### 3b. Auto-Probe VS Report
-
-**Auto-probe VS report (if not provided by user in section 1, OR if user-provided path was invalid):**
-- Only attempt if `forge_data_folder` is non-empty and the directory exists (validated above); otherwise skip probe and set `vs_report_available: false`
-- Check for `{forge_data_folder}/feasibility-report-{project_name}.md`
-- If found: "Auto-discovered VS report at `{path}`. Loading for additional context."
-- Store `vs_report_available: true` and `vs_report_path`
-- If not found: `vs_report_available: false` — "Proceeding without VS report — issue detection will rely on skill data only."
-
-### 3c. Reset RA State File
-
-Create (or overwrite) `{forge_data_folder}/ra-state-{project_name}.md` with a fresh header:
-
-```markdown
-<!-- RA state for {project_name} — generated {current_date} -->
-```
-
-This ensures steps 02-04 append to a clean slate and context recovery in step-05 never loads stale findings from a prior run.
-
-### 4. Load Refinement Rules
-
-Load `{refinementRulesData}` for reference by downstream steps.
-
-Extract: gap detection rules, issue detection rules, improvement detection rules, citation format, and preservation rules.
-
-### 5. Display Initialization Summary
-
-"**Architecture Refinement Initialized**
-
-| Field | Value |
-|-------|-------|
-| **Architecture Doc** | {architecture_doc} |
-| **VS Report** | {vs_report_path or 'Not provided — issue detection will use skill data only'} |
-| **Skills Loaded** | {skill_count} |
-
-**Skill Inventory:**
-
-| Skill | Language | Tier | Exports |
-|-------|----------|------|---------|
-| {skill_name} | {language} | {confidence_tier} | {exports_documented} |
-
-**Proceeding to gap analysis...**"
-
-### 6. Auto-Proceed to Next Step
-
-Load, read the full file and then execute `{nextStepFile}`.
-

package/src/skf-rename-skill/steps-c/step-04-health-check.md

@@ -1,22 +0,0 @@
----
-# `shared/health-check.md` resolves relative to the SKF module root
-# (`_bmad/skf/` when installed, `src/` during development), NOT relative
-# to this step file.
-nextStepFile: 'shared/health-check.md'
----
-
-# Step 4: Workflow Health Check
-
-## STEP GOAL:
-
-Chain to the shared workflow self-improvement health check at `{nextStepFile}`. This is the terminal step of rename-skill — after the shared health check completes, the workflow is fully done.
-
-## Rules
-
-- No user-facing reports, file writes, or result contracts in this step — those belong in step-03
-- Delegate directly to `{nextStepFile}` with no additional commentary
-- Do not attempt any other action between loading this step and executing `{nextStepFile}`
-
-## MANDATORY SEQUENCE
-
-Load `{nextStepFile}`, read it fully, then execute it.

package/src/skf-test-skill/steps-c/step-07-health-check.md

@@ -1,25 +0,0 @@
----
-# `{nextStepFile}` is resolved by probing both candidate roots in order.
-# HALT if neither exists — step-06 §7 should have caught this already, but
-# this step re-asserts the invariant at dispatch time.
-nextStepFileProbeOrder:
-  - '{project-root}/_bmad/skf/shared/health-check.md'
-  - '{project-root}/src/shared/health-check.md'
----
-
-# Step 7: Workflow Health Check
-
-## STEP GOAL:
-
-Chain to the shared workflow self-improvement health check. This is the terminal step of test-skill — after the shared health check completes, the workflow is fully done.
-
-## Rules
-
-- No user-facing reports, file writes, or result contracts in this step — those belong in step-06
-- Delegate directly to the resolved health-check path with no additional commentary
-- Do not attempt any other action between loading this step and executing the resolved file
-
-## MANDATORY SEQUENCE
-
-1. Probe `{nextStepFileProbeOrder}` in order. Use the FIRST path that exists as `{nextStepFile}`. HALT with the diagnostic from step-06 §7 if neither exists.
-2. Load `{nextStepFile}`, read it fully, then execute it.

package/src/skf-update-skill/steps-c/step-07-report.md

@@ -1,148 +0,0 @@
----
-nextStepFile: './step-08-health-check.md'
----
-
-# Step 7: Report
-
-## STEP GOAL:
-
-Present a comprehensive change summary showing what was updated, [MANUAL] sections preserved, confidence tier breakdown, and recommend next workflow actions in the SKF chain.
-
-## Rules
-
-- Focus only on reporting — all operations are complete; do not modify any files
-- Present clear, actionable summary with next step recommendations
-- Chains to the local health-check step via `{nextStepFile}` after completion — the user-facing summary is NOT the terminal step
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Handle No-Change Shortcut
-
-**If routed here from step 02 with no changes detected:**
-
-"**Update Skill Report: {skill_name}**
-
-**Status:** No changes detected
-
-Source code matches provenance map exactly. The skill `{skill_name}` is current — no update was needed.
-
-**Provenance age:** {days} days since last extraction
-**Forge tier:** {tier}
-
-**Recommendation:** No action required. Run audit-skill periodically to monitor for drift."
-
-→ Load, read the full file, and execute `{nextStepFile}` — the health-check step is the true terminal step of this workflow.
-
-### 2. Present Change Summary
-
-"**Update Skill Report: {skill_name}**
-
----
-
-### Operation Summary
-
-| Metric | Value |
-|--------|-------|
-| **Skill** | {skill_name} ({single/stack}) |
-| **Forge Tier** | {tier} |
-| **Mode** | {normal/degraded} |
-| **Duration** | {step count} steps |
-
-### Changes Applied
-
-| Category | Count |
-|----------|-------|
-| Files modified | {count} |
-| Files added | {count} |
-| Files deleted | {count} |
-| Files moved/renamed | {count} |
-| **Total exports affected** | {count} |
-
-### Export Changes
-
-| Change Type | Count |
-|-------------|-------|
-| Updated (signature/type change) | {count} |
-| Added (new exports) | {count} |
-| Removed (deleted exports) | {count} |
-| Moved (file relocated) | {count} |
-| Renamed (identifier changed) | {count} |
-
-### Confidence Tier Breakdown
-
-| Tier | Count | Description |
-|------|-------|-------------|
-| T1 | {count} | AST-verified structural extraction |
-| T1-low | {count} | Pattern-matched (Quick tier or degraded) |
-| T2 | {count} | QMD-enriched semantic context |
-
-### [MANUAL] Section Preservation
-
-| Metric | Count |
-|--------|-------|
-| Sections preserved | {count} |
-| Conflicts resolved | {count} |
-| Orphans kept | {count} |
-| Orphans removed | {count} |
-| **Integrity** | {VERIFIED / count issues} |"
-
-### 3. Present Validation Findings (If Any)
-
-**If validation findings exist from step 05:**
-
-"### Validation Findings
-
-| Check | Status | Issues |
-|-------|--------|--------|
-| Spec compliance | {PASS/WARN/FAIL} | {count} |
-| [MANUAL] integrity | {PASS/WARN/FAIL} | {count} |
-| Confidence tiers | {PASS/WARN/FAIL} | {count} |
-| Provenance | {PASS/WARN/FAIL} | {count} |
-
-{List specific findings if WARN or FAIL}"
-
-**If all validations passed:** "### Validation: All checks passed."
-
-### 4. Show Files Updated
-
-"### Files Written
-
-| File | Status |
-|------|--------|
-| `{resolved_skill_package}/SKILL.md` | Updated |
-| `{resolved_skill_package}/metadata.json` | Updated |
-| `{forge_version}/provenance-map.json` | Updated |
-| `{forge_version}/evidence-report.md` | Appended |
-| {stack reference files if applicable} | Updated |
-
-Where `{resolved_skill_package}` = `{skills_output_folder}/{skill_name}/{version}/{skill_name}/` and `{forge_version}` = `{forge_data_folder}/{skill_name}/{version}/` — see `knowledge/version-paths.md`."
-
-### 5. Workflow Chaining Recommendations
-
-"### Next Steps
-
-Based on the update results:"
-
-**If all validations passed:**
-"- **audit-skill** — Run to verify the update resolved known drift
-- **export-skill** — Package the updated skill for distribution
-- **test-skill** — Run test suite against the updated skill"
-
-**If validation warnings/failures exist:**
-"- **audit-skill** — Run to identify remaining issues
-- Review validation findings above before exporting"
-
-**If triggered by audit-skill chain:**
-"- **audit-skill** — Re-run to verify CRITICAL/HIGH drift resolved
-- **export-skill** — Package once audit confirms clean state"
-
-### 5b. Result Contract
-
-Write the result contract per `shared/references/output-contract-schema.md`: the per-run record at `{forge_version}/update-skill-result-{YYYYMMDD-HHmmss}.json` (UTC timestamp, resolution to seconds) and a copy at `{forge_version}/update-skill-result-latest.json` (stable path for pipeline consumers — copy, not symlink). Include all modified file paths in `outputs`; include `exports_affected`, `files_modified`, and `validation_status` (passed/warnings/failures) in `summary`.
-
-### 6. Chain to Health Check
-
-ONLY WHEN the change summary has been presented, files-written list displayed, and result contract saved will you then load, read the full file, and execute `{nextStepFile}`. The health-check step is the true terminal step — do not stop here even though the report reads as final.
-

package/src/skf-update-skill/steps-c/step-08-health-check.md

@@ -1,22 +0,0 @@
----
-# `shared/health-check.md` resolves relative to the SKF module root
-# (`_bmad/skf/` when installed, `src/` during development), NOT relative
-# to this step file.
-nextStepFile: 'shared/health-check.md'
----
-
-# Step 8: Workflow Health Check
-
-## STEP GOAL:
-
-Chain to the shared workflow self-improvement health check at `{nextStepFile}`. This is the terminal step of update-skill — after the shared health check completes, the workflow is fully done.
-
-## Rules
-
-- No user-facing reports, file writes, or result contracts in this step — those belong in step-07
-- Delegate directly to `{nextStepFile}` with no additional commentary
-- Do not attempt any other action between loading this step and executing `{nextStepFile}`
-
-## MANDATORY SEQUENCE
-
-Load `{nextStepFile}`, read it fully, then execute it.

package/src/skf-verify-stack/steps-c/step-01-init.md

@@ -1,178 +0,0 @@
----
-nextStepFile: './step-02-coverage.md'
-reportTemplate: 'assets/feasibility-report-template.md'
-feasibilitySchemaRef: 'src/shared/references/feasibility-report-schema.md'
-atomicWriteScript: '{project-root}/src/shared/scripts/skf-atomic-write.py'
-outputFile: '{forge_data_folder}/feasibility-report-{project_slug}-{timestamp}.md'
-outputFileLatest: '{forge_data_folder}/feasibility-report-{project_slug}-latest.md'
----
-
-# Step 1: Initialize Verification
-
-## STEP GOAL:
-
-Load all generated skills from the skills output folder, accept the architecture document path (required) and optional PRD/vision document path from the user, validate that all inputs exist and are readable, create the feasibility report document, and present an initialization summary before auto-proceeding.
-
-## Rules
-
-- Focus only on loading inputs, scanning skills, and creating the report skeleton — do not perform analysis
-- Auto-proceed — halts only on validation errors
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-### 1. Accept Input Documents
-
-"**Verify Stack — Feasibility Analysis**
-
-Please provide the following:
-1. **Architecture document path** (REQUIRED) — your project's architecture doc
-2. **PRD or vision document path** (OPTIONAL) — for requirements coverage analysis
-3. **Previous feasibility report path** (OPTIONAL) — for delta comparison with a prior run (provide a backup copy)"
-
-Wait for user input. **GATE [default: use args]** — If `{headless_mode}` and architecture doc path was provided as argument: use that path and auto-proceed, log: "headless: using provided architecture path".
-
-**Validate architecture document:**
-- Confirm the file exists and is readable
-- If missing or unreadable → "Architecture document not found at `{path}`. Provide a valid path."
-- HALT until a valid architecture document is provided
-
-**Validate PRD document (if provided):**
-- Confirm the file exists and is readable
-- If missing → "PRD document not found at `{path}`. Proceeding without PRD — requirements pass will be skipped."
-- Store PRD availability as `prdAvailable: true|false`
-
-**Validate previous report (if provided):**
-- Confirm the file exists and is readable
-- **Collision check:** Compare both the provided path and `{outputFile}` via `(st_dev, st_ino)` tuples obtained from `stat(2)` on each path (do not rely on absolute-path string equality — symlinks, bind mounts, and case-insensitive filesystems can defeat string comparison; the `(st_dev, st_ino)` comparison is the canonical kernel-level equivalent of `os.path.realpath`-based equality and is strictly stronger because it also catches hardlinks). If `{outputFile}` does not yet exist, resolve its parent via `realpath`, stat that directory, and combine `(st_dev, parent_ino, basename)` for comparison. If the two paths resolve to the same inode, warn: "The previous report path points to the same inode as the new report. This file will be overwritten during this run. Provide a path to a backup copy, or leave empty to skip delta comparison." HALT until resolved.
-- If missing → "Previous report not found at `{path}`. Proceeding without delta comparison."
-- Store as `previousReport: {path}` (or empty string if not provided)
-
-### 2. Scan Skills Folder
-
-**Pre-flight — skills folder existence:**
-- If `{skills_output_folder}` does not exist on disk: HALT with "**Cannot proceed.** `{skills_output_folder}` does not exist — run **[SF] Setup Forge** to initialize the forge, then generate skills with [CS] or [QS]."
-- If `{skills_output_folder}` exists but is empty (no subdirectories at all): HALT with "**Cannot proceed.** `{skills_output_folder}` contains 0 skills. Generate skills with [CS] Create Skill or [QS] Quick Skill, then re-run [VS]."
-
-Read the `{skills_output_folder}` directory. Skills use a version-nested directory structure (see `knowledge/version-paths.md`).
-
-**Version-aware skill discovery:**
-1. Read `{skills_output_folder}/.export-manifest.json` if it exists. For each skill in `exports`, use `active_version` to resolve `{skill_package}` = `{skills_output_folder}/{skill-name}/{active_version}/{skill-name}/`
-2. For any subdirectory not covered by the manifest, check for an `active` symlink at `{skills_output_folder}/{dir_name}/active` — resolve to `{skill_group}/active/{dir_name}/`
-3. Fall back to flat path `{skills_output_folder}/{dir_name}/` for unmigrated skills
-
-For each resolved skill package, check for the presence of `SKILL.md`, `metadata.json`, and `bmad-skill-manifest.yaml`. If `bmad-skill-manifest.yaml` is missing in the resolved package, log "Skipping `{dir_name}` — missing bmad-skill-manifest.yaml" and exclude from inventory (do not spawn a subagent).
-
-**Non-symlink `active` check:** When resolving via the `active` symlink pattern (case 2 above), perform an explicit `is_symlink` check on `{skills_output_folder}/{dir_name}/active`. If the path exists but is NOT a symlink, log "Skipping `{dir_name}` — `active` is not a symlink (repair with [SKF-update-skill])" and treat as missing.
-
-**Orphan-versions detection:** For any `{skills_output_folder}/{dir_name}/` that contains subdirectories matching semver (`^\d+\.\d+\.\d+`) but has no `active` symlink at all, emit: "**Error:** Skill `{dir_name}` has versions `{list_of_version_dirs}` but no `active` symlink — run [SKF-update-skill] to repair before re-running [VS]." Exclude the skill from inventory; count it toward the failure budget for the run summary.
-
-<!-- Subagent delegation: read metadata.json files in parallel, return compact JSON -->
-
-**Read all metadata.json files in parallel using subagents.** Launch up to **8 subagents concurrently** (batch larger inventories in rounds of 8 — the 8-way cap keeps the aggregate token window for the parent manageable while still parallelizing most typical stack sizes; tune in a future minor if inventories routinely exceed ~40 skills). Each subagent receives one resolved skill package path and MUST:
-1. Read `{skill_package}/metadata.json`
-2. ONLY return this compact JSON — no prose, no extra commentary:
-
-```json
-{
-  "skill_name": "...",
-  "language": "...",
-  "confidence_tier": "...",
-  "exports_documented": 0,
-  "source_repo": "...",
-  "source_root": "..."
-}
-```
-
-Parent collects all subagent JSON summaries. Fields map directly from metadata.json:
-- `skill_name` ← `name`
-- `language` ← `language`
-- `confidence_tier` ← `confidence_tier`
-- `exports_documented` ← `stats.exports_documented`
-- `source_repo` ← `source_repo` (or empty string if absent)
-- `source_root` ← `source_root` (or empty string if absent)
-
-**Subagent JSON schema validation:** For each subagent response, require keys `skill_name`, `language`, and an integer `exports_documented`. Wrap each JSON parse in try/catch. On parse failure or missing required key, log "Skipping `{dir_name}` — metadata.json unparseable (skill may be under active modification)" and exclude from the inventory. If more than **20%** (the failure-budget threshold — chosen so a single malformed skill in a small 3-5 skill inventory does not trip the halt, while larger inventories still halt before evidence quality collapses) of subagent calls fail schema validation, HALT the workflow with: "Inventory scan unreliable — {failed_count}/{total_count} skills returned malformed metadata. Re-run [VS] after skills stabilize."
-
-**Capture mtime:** For each accepted skill, also record `metadata.json`'s mtime (via `stat`) into the inventory as `metadata_mtime`. Step-03 will re-verify this to detect mid-run modifications.
-
-**metadata_schema_version check:** For each accepted skill, read `metadata_schema_version` from `metadata.json`. If missing or below minimum (`1.0`), log "Skipping `{dir_name}` — metadata_schema_version `{value}` below minimum `1.0`. Re-run [SKF-update-skill] to migrate." and exclude from the inventory.
-
-**Build a skill inventory** as an internal list of all loaded skills with the fields above.
-
-**If a resolved skill package lacks SKILL.md or metadata.json:**
-- Log: "Skipping `{dir_name}` — missing SKILL.md or metadata.json"
-- Do not include in inventory
-
-### 3. Validate Minimum Requirements
-
-**Check skill count:**
-- At least 2 valid skills must exist (a stack requires multiple libraries)
-- If fewer than 2 → "**Cannot proceed.** Only {count} skill(s) found in `{skills_output_folder}`. A stack requires at least 2 skills. Generate more skills with [CS] Create Skill or [QS] Quick Skill, then re-run [VS]."
-- HALT workflow
-
-**Check forge_data_folder:**
-- Verify `forge_data_folder` was resolved from config.yaml and is non-empty
-- If undefined or empty → "**Cannot proceed.** `forge_data_folder` is not configured in config.yaml. Re-run [SF] Setup Forge to initialize."
-- HALT workflow
-
-**Check architecture document:**
-- Confirm it was loaded successfully in section 1
-- If not → HALT with error (should not reach here if section 1 validation passed)
-
-### 4. Create Feasibility Report
-
-This skill is the PRODUCER of the feasibility report schema defined in `{feasibilitySchemaRef}`. All outputs MUST conform to that schema — in particular: `schemaVersion: "1.0"`, the defined verdict token set (`Verified|Plausible|Risky|Blocked`; overall `FEASIBLE|CONDITIONALLY_FEASIBLE|NOT_FEASIBLE`), the filename pattern, and the section-heading order.
-
-**Compute filename variables:**
-- `project_slug`: slugify `project_name` (lowercase, hyphens only, no unicode, no whitespace)
-- `timestamp`: UTC `YYYYMMDD-HHmmss` captured at step-01 start
-- `outputFile` resolves to `{forge_data_folder}/feasibility-report-{project_slug}-{timestamp}.md`
-- `outputFileLatest` resolves to `{forge_data_folder}/feasibility-report-{project_slug}-latest.md` (a copy, not a symlink — per schema)
-
-**Load** `{reportTemplate}` and stage the initial content.
-
-**Populate frontmatter (per shared schema — required keys):**
-- `schemaVersion: "1.0"`
-- `reportType: feasibility`
-- `projectName: "{project_name}"`
-- `projectSlug: "{project_slug}"`
-- `generatedAt: "{ISO-8601 UTC}"`
-- `generatedBy: skf-verify-stack`
-- `overallVerdict: "CONDITIONALLY_FEASIBLE"` (provisional until step-05 finalizes)
-- `coveragePercentage: 0`
-- `pairsVerified: 0`, `pairsPlausible: 0`, `pairsRisky: 0`, `pairsBlocked: 0`
-- `recommendationCount: 0`
-- `prdAvailable: true|false` (from section 1 validation)
-
-**Populate producer-local bookkeeping keys (not part of the consumer contract):**
-- `architectureDoc`, `prdDoc` (or "none"), `previousReport` (or empty string)
-- `skillsAnalyzed: {count}`
-- `stepsCompleted: ['step-01-init']`
-
-**Atomic write:** Pipe the staged content through `python3 {atomicWriteScript} write --target {outputFile}` and then again with `--target {outputFileLatest}`. Both writes use the same staged content. Do NOT use `rm`+rewrite; do NOT create a symlink for the `-latest` copy.
-
-### 5. Display Initialization Summary
-
-"**Stack Verification Initialized**
-
-| Field | Value |
-|-------|-------|
-| **Skills Loaded** | {count} |
-| **Architecture Doc** | {architecture_doc} |
-| **PRD Document** | {prd_doc or 'Not provided — requirements pass will be skipped'} |
-| **Previous Report** | {previousReport or 'Not provided — no delta comparison'} |
-
-**Skill Inventory:**
-
-| Skill | Language | Tier | Exports |
-|-------|----------|------|---------|
-| {skill_name} | {language} | {confidence_tier} | {exports_documented} |
-
-**Proceeding to coverage analysis...**"
-
-### 6. Auto-Proceed to Next Step
-
-Load, read the full file and then execute `{nextStepFile}`.
-