bmad-module-skill-forge 1.4.0 → 1.5.0

package/src/skf-audit-skill/steps-c/step-01-init.md

@@ -1,221 +0,0 @@
----
-nextStepFile: './step-02-re-index.md'
-outputFile: '{forge_version}/drift-report-{timestamp}.md'
-templateFile: 'assets/drift-report-template.md'
----
-
-# Step 1: Initialize Audit
-
-## STEP GOAL:
-
-Load the existing skill artifacts, provenance map, and forge tier configuration to establish the baseline for drift detection. Create the drift report document and present a baseline summary for user confirmation before proceeding with analysis.
-
-## Rules
-
-- Focus only on loading skill artifacts and establishing the baseline — do not perform any diff or analysis
-- Do not proceed if skill path is invalid or SKILL.md not found
-- Present baseline summary clearly so user can confirm before analysis begins
-- Docs-only limitation: If `metadata.json` indicates `source_type: "docs-only"` or `confidence_tier: "Quick"` with all T3 citations, inform user: "**This is a docs-only skill.** Drift detection compares against upstream documentation, not source code. Re-run `@Ferris US` to re-fetch documentation URLs and detect content changes." Recommend update-skill instead.
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Get Skill Path
-
-"**Audit Skill — Drift Detection**
-
-Which skill would you like to audit? Please provide the skill name or path."
-
-**If user provides skill name (not full path) — version-aware path resolution (see `knowledge/version-paths.md`):**
-1. Read `{skills_output_folder}/.export-manifest.json` and look up the skill name in `exports` to get `active_version`
-2. If found: resolve to `{skill_package}` = `{skills_output_folder}/{skill_name}/{active_version}/{skill_name}/`
-3. If not in manifest: check for `active` symlink at `{skills_output_folder}/{skill_name}/active` — resolve to `{skill_group}/active/{skill_name}/`
-4. If neither: fall back to flat path `{skills_output_folder}/{skill_name}/`. If SKILL.md exists at the flat path, auto-migrate per `knowledge/version-paths.md` migration rules
-5. Store the resolved path as `{resolved_skill_package}`
-
-**If user provides full path:**
-- Use as provided
-
-**Validate:** Check that `SKILL.md` exists at the resolved path.
-- If missing → "Skill not found at `{resolved_skill_package}`. Check the path and try again."
-- If found → Continue
-
-### 2. Load Forge Tier
-
-Load `{sidecar_path}/forge-tier.yaml` to detect available tools.
-
-**If file missing:**
-- "Setup-forge has not been run. Cannot determine tool availability. Run `[SF] Setup Forge` first."
-- HALT workflow
-
-**If found:**
-- Extract tier level: Quick / Forge / Forge+ / Deep
-- Extract available tools: gh_bridge, ast_bridge, qmd_bridge — see `knowledge/tool-resolution.md` for concrete tool resolution per IDE
-
-**Apply tier override:** Read `{sidecar_path}/preferences.yaml`. If `tier_override` is set and is a valid tier value (Quick, Forge, Forge+, or Deep), use it instead of the detected tier.
-
-### 3. Load Skill Artifacts
-
-Load the following from the skill directory:
-
-**Required:**
-- `SKILL.md` — The skill document to audit
-- `metadata.json` — Skill metadata (version, created date, export count)
-
-**Extract from metadata.json:**
-- `name`, `version`, `generation_date`, `confidence_tier` used during creation
-- `source_root` — Resolved source code path used during extraction
-
-**Detect split-body state:** If a `references/` directory exists and SKILL.md's `## Full` headings are absent or stubs, this is a split-body skill. Flag `split_body: true` in the baseline so downstream steps (especially semantic diff in step-04) know to also read `references/*.md` for complete content comparison.
-
-### 4. Load Provenance Map
-
-Search for provenance map at `{forge_data_folder}/{skill_name}/{active_version}/provenance-map.json` (i.e., `{forge_version}/provenance-map.json`). If not found at the versioned path, fall back to `{forge_data_folder}/{skill_name}/provenance-map.json`:
-
-**If found:**
-- Load and extract: export list, file mappings, extraction timestamps, confidence tiers
-- Record provenance map age (days since last extraction)
-
-**If missing at both paths:**
-- "No provenance map found for `{skill_name}`. This skill may not have been created by create-skill."
-- "**Degraded mode available:** I can perform text-based comparison without provenance data. Findings will have T1-low confidence."
-- "**[D]egraded mode** — proceed with text-diff only"
-- "**[X]** — abort audit"
-- Wait for user selection. If D, set `degraded_mode: true`. If X, halt workflow.
-
-### Stack Skill Detection
-
-After loading provenance-map.json, detect skill type:
-- If `provenance_version` is `"2.0"` and `skill_type` is `"stack"`: set `{is_stack_skill}` = true
-- If provenance-map has top-level `libraries` key (v1 stack format): set `{is_stack_skill}` = true, `{legacy_stack_provenance}` = true
-- Otherwise: `{is_stack_skill}` = false
-
-If `{is_stack_skill}` is true and `constituents` array is present (compose-mode stack):
-- For each constituent, compute the current metadata hash: read `{constituent.skill_path}/active/{constituent.skill_name}/metadata.json` and compute SHA-256
-- Compare against `constituent.metadata_hash`
-- Flag any mismatches as **constituent drift** with severity HIGH
-- Record constituent freshness results for the report
-
-If `{legacy_stack_provenance}` is true: log a note that this stack uses v1 provenance format with reduced audit depth (library-level only, no per-export verification).
-
-### 5. Resolve Source Path
-
-**If provenance map loaded:**
-- Use `source_root` from provenance map as source code path
-- Verify source path still exists and is accessible
-- Extract `baseline_commit` = `provenance-map.source_commit` (fall back to `metadata.source_commit` if absent from the provenance map)
-- Extract `baseline_ref` = `metadata.source_ref` (may be a tag, branch, `HEAD`, or `"local"`)
-
-**If degraded mode:**
-- Ask user: "Please provide the path to the current source code."
-- `baseline_commit` and `baseline_ref` are unavailable — §5b will short-circuit
-
-**Validate:** Confirm source directory exists and contains expected files.
-
-### 5b. Detect Upstream Drift
-
-Upstream drift detection is the primary use case of this workflow. If the local clone is still pinned to the baseline commit while upstream has shipped newer tags, auditing against the unchanged tree will misleadingly report CLEAN even after a major release.
-
-**Skip this section** if any of the following hold:
-- `baseline_ref` is `"local"`, `null`, or unset (non-git source)
-- `{source_root}` is not a git worktree (`git -C {source_root} rev-parse --git-dir` fails)
-- `baseline_commit` is unavailable
-- Degraded mode is active (no provenance map)
-
-When skipping, log the reason, then set the audit-ref context variables to baseline values so step-06 renders a coherent Provenance row: `audit_ref = baseline_ref or "(unknown)"`, `audit_ref_source = "baseline"` (or `"unavailable"` if both `baseline_ref` and `baseline_commit` are unset), `audit_commit = baseline_commit or "(unknown)"`, `latest_tag = null`, `remote_head = null`. Continue to §6.
-
-**Otherwise:**
-
-1. **Fetch upstream refs** (read-only, no working-tree mutation):
-
-   ```bash
-   git -C {source_root} fetch --tags --quiet origin
-   ```
-
-   If fetch fails (no network, no remote, detached clone), log the reason, record `upstream_fetch: "failed:{reason}"` in context, set `audit_ref = baseline_ref`, `audit_ref_source = "baseline"`, `audit_commit = baseline_commit`, `latest_tag = null`, `remote_head = null`, and continue to §6 without gating.
-
-2. **Find latest remote ref:**
-   - Remote default-branch HEAD: `git -C {source_root} rev-parse origin/HEAD` (fall back to `origin/main` or `origin/master` if the symbolic ref is unavailable) — record as `remote_head`.
-   - Newest semver tag: `git -C {source_root} for-each-ref --sort=-v:refname --format='%(refname:short)' 'refs/tags/v*' | head -1` — record as `latest_tag`.
-
-3. **Compare to baseline:**
-   - If `baseline_commit` equals the commit that `remote_head` resolves to AND (`latest_tag` is empty OR semver-equals `baseline_ref` OR is older than `baseline_ref`), upstream has not moved. Set `audit_ref = baseline_ref`, `audit_ref_source = "baseline"`, `audit_commit = baseline_commit`. Continue to §6.
-   - Otherwise upstream has moved — proceed to the gate.
-
-4. **User gate — Upstream drift detected:**
-
-   "**Upstream has moved since this skill was created.**
-
-   | | Baseline | Upstream |
-   |---|---|---|
-   | Ref | `{baseline_ref}` | `{latest_tag}` (newest tag) / `{remote_head}` (default HEAD) |
-   | Commit | `{baseline_commit_short}` | `{latest_tag_commit_short}` / `{remote_head_short}` |
-
-   Auditing against the baseline clone will report little-to-no structural drift even if the upstream API has changed. Options:
-
-   - **[C] Checkout-and-audit-against-latest** — checkout `{latest_tag}` (or `{remote_head}` if no newer tag) in `{source_root}` and audit against that. Re-extraction will reflect the current upstream surface.
-   - **[S] Stay-on-baseline** — keep `{source_root}` at `{baseline_ref}` and audit structural drift against the unchanged tree. The report will note `audit_ref = baseline`.
-   - **[X] Abort** — halt the workflow without producing a report.
-
-   **Select:** [C] / [S] / [X]"
-
-   **Gate handling:**
-   - **[C]:** Acquire an exclusive lock on `{source_root}/.skf-workspace.lock` (`flock -x` or `fcntl.flock(LOCK_EX)`) before mutating the working tree — matches the concurrency discipline in `src/skf-create-skill/references/source-resolution-protocols.md` and avoids racing with a concurrent create-skill / test-skill run against the same workspace clone. If `flock` is unavailable, emit a warning and proceed. Then `git -C {source_root} checkout {chosen_ref}` (prefer `latest_tag` when present, else `remote_head`). Set `audit_ref = {chosen_ref}`, `audit_ref_source = "checkout-latest"`, `audit_commit = git rev-parse HEAD`. Hold the lock through step-02 re-extraction and release only after the extraction snapshot is complete.
-   - **[S]:** Keep baseline. Set `audit_ref = baseline_ref`, `audit_ref_source = "baseline"`, `audit_commit = baseline_commit`.
-   - **[X]:** HALT workflow — do not create drift report.
-   - **Other input:** help user, redisplay gate.
-
-   **Headless default** (when `{headless_mode}`): auto-select **[S]** and emit a loud log line: `"headless: upstream drift detected ({baseline_ref} → {latest_tag or remote_head}); staying on baseline. Re-run interactively to audit against latest."` Do not check out in headless mode — silent ref changes under automation would mutate the user's working tree without consent.
-
-5. **Record for report:** store `audit_ref`, `audit_ref_source`, `audit_commit`, `latest_tag`, `remote_head`, and `baseline_commit` in context. Step-06 surfaces them in the Provenance section so readers can tell which comparison actually ran.
-
-### 6. Create Drift Report
-
-Create `{outputFile}` from `{templateFile}`:
-
-- Populate frontmatter: skill_name, skill_path, source_path, forge_tier, date, user_name
-- Set `stepsCompleted: ['step-01-init']`
-- Fill Audit Summary skeleton with loaded baseline data
-
-### 7. Present Baseline Summary (User Gate)
-
-"**Audit Baseline Loaded**
-
-| Field | Value |
-|-------|-------|
-| **Skill** | {skill_name} v{version} |
-| **Created** | {generation_date} |
-| **Source** | {source_path} |
-| **Forge Tier** | {current_tier} (created at {original_tier}) |
-| **Provenance Age** | {days} days since last extraction |
-| **Export Count** | {count} exports in provenance map |
-| **Mode** | {normal / degraded} |
-
-**Analysis plan based on tier:**
-- {Quick: text-diff comparison (T1-low confidence)}
-- {Forge: AST structural comparison (T1 confidence)}
-- {Forge+: AST structural comparison + CCC-assisted rename detection (T1 confidence)}
-- {Deep: AST structural + QMD semantic comparison (T1 + T2 confidence)}
-
-**Ready to begin drift analysis?**"
-
-### 8. Present MENU OPTIONS
-
-Display: "**Select:** [C] Continue to Analysis"
-
-#### Menu Handling Logic:
-
-- IF C: Save baseline to {outputFile}, update frontmatter stepsCompleted, then load, read entire file, then execute {nextStepFile}
-- IF Any other: help user, then [Redisplay Menu Options](#8-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- **GATE [default: C]** — If `{headless_mode}`: auto-proceed with [C] Continue, log: "headless: auto-continue past baseline confirmation"
-- ONLY proceed to next step when user selects 'C'
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN C is selected and the drift report has been created with baseline data populated, will you then load and read fully `{nextStepFile}` to execute and begin source re-indexing.
-

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.