bmad-module-skill-forge 0.5.0 → 0.7.0

package/src/workflows/setup-forge/steps-c/step-01b-ccc-index.md

@@ -0,0 +1,148 @@
+---
+name: 'step-01b-ccc-index'
+description: 'Ensure ccc project index exists — Forge+ and Deep tiers when ccc is available'
+
+nextStepFile: './step-02-write-config.md'
+---
+
+# Step 1b: CCC Index Verification
+
+## STEP GOAL:
+
+If ccc is available (`{ccc: true}` from step-01), verify that the ccc index exists for the project root. If no index exists, create it. Store index state in context for step-02 to write into forge-tier.yaml.
+
+For Quick and Forge tiers, or when ccc is unavailable, skip silently and proceed.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step, ensure entire file is read
+- 🎯 Execute all operations autonomously — no user interaction
+
+### Role Reinforcement:
+
+- ✅ You are a system executor verifying the ccc index state
+- ✅ ccc indexing failure is never a workflow error — degrade gracefully
+- ✅ No negative messaging for tiers that skip this step
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on ccc index verification and creation
+- 🚫 FORBIDDEN to display skip messages for Quick/Forge tiers
+- 🚫 FORBIDDEN to fail the workflow if ccc indexing fails
+- 🚫 FORBIDDEN to re-index if ccc index already exists and is fresh (< staleness threshold)
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Store ccc index state in context for step-02
+- 🚫 FORBIDDEN to write forge-tier.yaml — that is step-02's job
+
+## CONTEXT BOUNDARIES:
+
+- Available: {ccc} boolean and {ccc_daemon} status from step-01
+- Available: {calculated_tier} from step-01
+- Available: existing forge-tier.yaml may contain prior `ccc_index` state
+- Focus: ccc index state verification and creation only
+- Dependencies: step-01 must have completed with tool detection results
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Check Eligibility
+
+Read `{ccc}` from step-01 context.
+
+**If `{ccc}` is false:** Set `{ccc_index_result: "none", ccc_indexed_path: null, ccc_last_indexed: null}`. Proceed directly to section 4 (Auto-Proceed) — no output, no messaging.
+
+**If `{ccc}` is true:** Continue to section 2.
+
+### 2. Check Existing Index State
+
+Read existing forge-tier.yaml at `{project-root}/_bmad/_memory/forger-sidecar/forge-tier.yaml` (if it exists from a previous run).
+
+Check the `ccc_index` section:
+- If `ccc_index.indexed_path` matches `{project-root}` AND `ccc_index.status` is `"fresh"`:
+  - Check freshness: if `ccc_index.last_indexed` is within `staleness_threshold_hours` (default 24h) of now → index is fresh
+  - Store `{ccc_index_result: "fresh", ccc_indexed_path: {project-root}, ccc_last_indexed: {existing timestamp}}`
+  - Proceed to section 4
+
+- If `ccc_index.indexed_path` matches `{project-root}` but timestamp is older than threshold:
+  - Note index is stale — proceed to section 3 for re-index (section 3 will overwrite `ccc_index_result` to `"created"` or `"failed"`)
+
+- If `ccc_index` is missing, has null values, or path doesn't match:
+  - Proceed to section 3 for initial index
+
+### 3. Create or Refresh CCC Index
+
+**If `{ccc_daemon}` is `"stopped"` or undefined (healthy daemon where no explicit state was recorded):**
+
+The `ccc index` command auto-starts the daemon when needed. Proceed with indexing below.
+
+**If `{ccc_daemon}` is `"error"`:**
+
+Attempt indexing anyway — errors will be caught below.
+
+Run:
+```bash
+ccc init {project-root}
+```
+
+**If init fails** (project may already be initialized): continue — this is not an error.
+
+Then run:
+```bash
+ccc index
+```
+
+**If succeeds:**
+- Run `ccc status` to get file count
+- Store `{ccc_index_result: "created", ccc_indexed_path: {project-root}, ccc_last_indexed: {current ISO timestamp}, ccc_file_count: {count from status}}`
+- Display: "**CCC index created.** {file_count} files indexed for semantic discovery."
+
+**If fails:**
+- Store `{ccc_index_result: "failed", ccc_indexed_path: null, ccc_last_indexed: null}`
+- Display: "CCC indexing failed: {error}. Extraction will use direct AST scanning — semantic pre-ranking unavailable this session."
+- Continue — this is NOT a workflow error
+
+### 4. Auto-Proceed
+
+"**Proceeding to write configuration...**"
+
+#### Menu Handling Logic:
+
+- After ccc index check completes (or is skipped), immediately load, read entire file, then execute {nextStepFile}
+
+#### EXECUTION RULES:
+
+- This is an auto-proceed step with no user choices
+- Proceed directly to next step after ccc index verification
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN ccc index verification is complete (or step is skipped for ccc unavailable) will you load and read fully `{nextStepFile}` to execute the configuration write step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- ccc unavailable: skipped silently with no output, context variables set to null/none
+- ccc available with fresh index: verified freshness, skipped re-index, context variables set
+- ccc available with stale/missing index: index created, context variables set with fresh timestamp
+- ccc indexing fails: logged gracefully, workflow continues, context variables set to failed/null
+- Auto-proceeded to step-02
+
+### ❌ SYSTEM FAILURE:
+
+- Displaying skip messages when ccc is unavailable
+- Halting the workflow on ccc index failure
+- Re-indexing when index is already fresh and path matches
+- Writing forge-tier.yaml (that is step-02's responsibility)
+- Not storing ccc index context variables for step-02
+
+**Master Rule:** CCC indexing is always best-effort. Failures degrade gracefully. The workflow never halts over ccc issues.

package/src/workflows/setup-forge/steps-c/step-02-write-config.md

@@ -41,10 +41,10 @@ Write the detected tool availability and calculated tier to forge-tier.yaml, cre
 
 ## CONTEXT BOUNDARIES:
 
-- Available: {detected_tools}, {calculated_tier}, {previous_tier} from step-01
+- Available: {detected_tools}, {calculated_tier}, {previous_tier} from step-01; {ccc_index_result}, {ccc_indexed_path}, {ccc_last_indexed} from step-01b
 - Focus: file I/O operations only
 - Limits: do not modify preferences.yaml if it exists
-- Dependencies: step-01 must have completed with tool detection results
+- Dependencies: step-01 and step-01b must have completed with tool detection and CCC index results
 
 ## MANDATORY SEQUENCE
 
@@ -63,18 +63,33 @@ tools:
   ast_grep: {true/false from detection}
   gh_cli: {true/false from detection}
   qmd: {true/false from detection}
+  ccc: {true/false from detection}
+  ccc_daemon: {ccc_daemon from step-01 if available: "healthy"|"stopped"|"error", or ~}
   security_scan: {true/false — true when SNYK_TOKEN is set}
 
 # Capability tier (derived from tool availability)
-# Quick = no tools required | Forge = + ast-grep | Deep = + ast-grep + gh + QMD
+# Quick = no tools | Forge = + ast-grep | Forge+ = + ast-grep + ccc | Deep = + ast-grep + gh + QMD
 tier: {calculated_tier}
 tier_detected_at: {current ISO timestamp}
 
+# CCC semantic index state (managed by setup-forge step-01b and extraction workflows)
+ccc_index:
+  indexed_path: {ccc_indexed_path from step-01b, or ~}
+  last_indexed: {ccc_last_indexed from step-01b, or ~}
+  status: {ccc_index_result from step-01b: "fresh"|"created"|"none"|"failed"}
+  staleness_threshold_hours: 24
+
+# CCC index registry (tracks which source paths have been indexed for skill workflows)
+# PRESERVE existing entries on re-runs — see Note below
+ccc_index_registry: {preserved from existing forge-tier.yaml, or [] if first run}
+
 # QMD collection registry (populated by create-skill, consumed by audit/update-skill)
-# Each entry tracks a QMD collection created during skill workflows
-qmd_collections: []
+# PRESERVE existing entries on re-runs — see Note below
+qmd_collections: {preserved from existing forge-tier.yaml, or [] if first run}
 ```
 
+**Note on re-runs:** The `qmd_collections`, `ccc_index_registry` arrays, and `staleness_threshold_hours` value must be preserved across re-runs. Before overwriting forge-tier.yaml, read these existing values and re-inject them into the new write. These values are populated by create-skill workflows or customized by users and must not be reset.
+
 **This file is ALWAYS overwritten** on every run — it reflects current tool state.
 
 If the write fails, report the error and halt the workflow.
@@ -90,29 +105,31 @@ Check if `{project-root}/_bmad/_memory/forger-sidecar/preferences.yaml` exists:
 # Created by setup-forge workflow on first run
 # Edit this file to customize Ferris behavior
 
-# Override detected tier (set to Quick, Forge, or Deep to force a tier)
+# Override detected tier (set to Quick, Forge, Forge+, or Deep to force a tier)
 tier_override: ~
 
 # Passive context injection (set to false to skip snippet generation and CLAUDE.md updates during export)
 passive_context: true
 
-# Skill generation defaults
-default_source_authority: community
-default_confidence_threshold: 0.7
+# Reserved for future use — these fields are not yet consumed by any workflow step
+# output_language: ~
+# skill_format_version: ~
+# citation_style: ~
+# confidence_display: ~
 ```
 
 **If it DOES exist:** Do not modify. Preserve entirely.
 
 ### 3. Ensure forge-data/ Directory
 
-Check if `{project-root}/forge-data/` directory exists:
+Check if `{forge_data_folder}` directory exists:
 
 - If missing: create it
 - If exists: skip silently
 
 ### 4. Auto-Proceed
 
-"**Proceeding to auto-index check...**"
+"**Proceeding to QMD collection hygiene...**"
 
 #### Menu Handling Logic:
 
@@ -133,7 +150,7 @@ ONLY WHEN forge-tier.yaml has been written successfully and preferences.yaml exi
 
 ### ✅ SUCCESS:
 
-- forge-tier.yaml written with accurate tool booleans, tier, timestamp, and empty qmd_collections registry
+- forge-tier.yaml written with accurate tool booleans (including ccc), tier, timestamp, ccc_index state, and preserved qmd_collections/ccc_index_registry arrays
 - preferences.yaml exists (created with defaults on first run, preserved on re-run)
 - forge-data/ directory exists (created or pre-existing)
 - Auto-proceeded to step-03

package/src/workflows/setup-forge/steps-c/step-03-auto-index.md

@@ -1,6 +1,6 @@
 ---
 name: 'step-03-auto-index'
-description: 'Verify and clean QMD collections against the forge-tier.yaml registry (Deep tier only)'
+description: 'Verify and clean QMD collections against the forge-tier.yaml registry (Deep tier only) and CCC index registry hygiene (Forge+/Deep)'
 
 nextStepFile: './step-04-report.md'
 ---
@@ -11,7 +11,7 @@ nextStepFile: './step-04-report.md'
 
 If the detected tier is Deep, verify the health of existing QMD collections by cross-referencing them against the `qmd_collections` registry in `forge-tier.yaml`. Identify orphaned collections (in QMD but not in registry) and stale registry entries (in registry but collection missing from QMD). Prompt the user before removing orphaned collections.
 
-For Quick and Forge tiers, skip silently and proceed.
+For Quick and Forge tiers (without ccc), skip silently and proceed. For Forge+ tier, skip QMD hygiene but the step routes correctly to the next step.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -41,7 +41,7 @@ For Quick and Forge tiers, skip silently and proceed.
 - 🎯 Follow the MANDATORY SEQUENCE exactly
 - 💾 QMD hygiene only verifies and cleans — it does NOT index new content
 - 📖 Use {calculated_tier} from step-01 context
-- 🚫 FORBIDDEN to attempt hygiene for Quick or Forge tiers
+- 🚫 FORBIDDEN to attempt QMD hygiene for Quick, Forge, or Forge+ tiers (Forge+ has no qmd)
 
 ## CONTEXT BOUNDARIES:
 
@@ -59,7 +59,9 @@ For Quick and Forge tiers, skip silently and proceed.
 
 Read `{calculated_tier}` from context.
 
-**If tier is NOT Deep:** Proceed directly to section 6 (Auto-Proceed) — no output, no messaging.
+**If tier is Quick or Forge:** Set `{ccc_registry_stale_cleaned: 0}`. Proceed directly to section 6 (Auto-Proceed) — no output, no messaging.
+
+**If tier is Forge+:** Skip QMD hygiene (qmd is not available at Forge+). Proceed directly to section 5b (CCC Index Registry Hygiene) — no QMD output, no messaging.
 
 **If tier IS Deep:** Continue to section 2.
 
@@ -132,6 +134,26 @@ Update forge-tier.yaml with the cleaned registry.
 
 **If no stale entries:** Skip this section silently.
 
+### 5b. CCC Index Registry Hygiene (Forge+ and Deep with ccc)
+
+**IF `tools.ccc` is true in forge-tier.yaml (regardless of whether QMD hygiene ran):**
+
+Read the `ccc_index_registry` array from forge-tier.yaml.
+
+For each entry, verify the indexed path still exists on disk:
+
+**Healthy** — path exists: no action needed.
+
+**Stale** — path does not exist (source directory removed or moved):
+- Remove the stale entry from `ccc_index_registry`
+- Log: "Removed stale CCC index registry entry: {path} (path no longer exists)"
+
+Update forge-tier.yaml with the cleaned registry.
+
+Store `{ccc_registry_stale_cleaned: count}` in context for step-04 reporting.
+
+**IF `tools.ccc` is false:** Skip this section silently.
+
 ### 6. Store Hygiene Results and Auto-Proceed
 
 Store in context for step-04 reporting:
@@ -141,6 +163,7 @@ Store in context for step-04 reporting:
 {hygiene_orphaned_removed: count}
 {hygiene_orphaned_kept: count}
 {hygiene_stale_cleaned: count}
+{ccc_registry_stale_cleaned: count}
 ```
 
 "**Proceeding to forge status report...**"
@@ -170,7 +193,7 @@ ONLY WHEN the hygiene check has been performed (or skipped for non-Deep tiers) w
 - Orphaned collections flagged and user prompted before removal
 - Stale registry entries cleaned from forge-tier.yaml
 - Hygiene results stored for step-04 reporting
-- Quick/Forge tier: skipped silently with no negative messaging
+- Quick/Forge/Forge+ tier: skipped silently with no negative messaging
 - Workflow continues regardless of hygiene outcome
 - Auto-proceeded to step-04
 
@@ -178,7 +201,7 @@ ONLY WHEN the hygiene check has been performed (or skipped for non-Deep tiers) w
 
 - Creating new QMD collections (that's create-skill's responsibility)
 - Silently deleting collections without user prompt
-- Attempting QMD hygiene for Quick or Forge tiers
+- Attempting QMD hygiene for Quick, Forge, or Forge+ tiers
 - Displaying "skipped" or "missing" messages for non-Deep tiers
 - Halting the workflow due to QMD hygiene failure
 - Indexing project directories (old auto-index behavior — removed)

package/src/workflows/setup-forge/steps-c/step-04-report.md

@@ -43,7 +43,8 @@ Display the forge status report with positive capability framing, report tier ch
 
 - Available: {detected_tools}, {calculated_tier}, {previous_tier}, {tier_override} from step-01
 - Available: tool version strings from step-01
-- Available: {hygiene_result}, {hygiene_healthy}, {hygiene_orphaned_removed}, {hygiene_orphaned_kept}, {hygiene_stale_cleaned} from step-03
+- Available: {hygiene_result}, {hygiene_healthy}, {hygiene_orphaned_removed}, {hygiene_orphaned_kept}, {hygiene_stale_cleaned}, {ccc_registry_stale_cleaned} from step-03
+- Available: {ccc_index_result} from step-01b (values: "fresh", "created", "failed", "none")
 - Focus: report display only — no file modifications
 - Dependencies: steps 01-03 must have completed
 
@@ -75,13 +76,24 @@ Load and read {tierRulesData} for the tier capability descriptions and re-run me
   {hygiene_healthy} collection(s) healthy
   {if hygiene_orphaned_removed > 0: {hygiene_orphaned_removed} orphaned collection(s) removed}
   {if hygiene_orphaned_kept > 0: {hygiene_orphaned_kept} orphaned collection(s) kept}
-  {if hygiene_stale_cleaned > 0: {hygiene_stale_cleaned} stale registry entry/entries cleaned}
+  {if hygiene_stale_cleaned > 0: {hygiene_stale_cleaned} stale QMD registry entry/entries cleaned}
+  {end if}
+
+  {if ccc_registry_stale_cleaned > 0:}
+  CCC Registry: {ccc_registry_stale_cleaned} stale entry/entries cleaned
   {end if}
 
   {if hygiene_result is "completed" and hygiene_healthy is 0:}
   QMD Registry: empty — collections are created automatically when you run [CS] Create Skill.
   {end if}
 
+  {if tools.ccc is true:}
+  CCC Index:
+  {if ccc_index_result is "fresh": up to date — semantic discovery ready}
+  {if ccc_index_result is "created": indexed this run — semantic discovery ready}
+  {if ccc_index_result is "failed": indexing failed — semantic discovery unavailable this session}
+  {end if}
+
 {if tier_override is active:}
   Note: Tier override active (set in preferences.yaml)
 
@@ -103,10 +115,10 @@ Load and read {tierRulesData} for the tier capability descriptions and re-run me
 
 ### 3. Handle --update-spec Flag (Optional)
 
-**If `--update-spec` was passed:**
+**If the user included `--update-spec` in their workflow invocation (e.g., `@Ferris SF --update-spec`):**
 - Attempt to fetch the latest agentskills.io specification schema
 - Use `gh` or `curl` to retrieve the spec
-- Store in `{project-root}/forge-data/agentskills-spec.json` (or appropriate format)
+- Store in `{forge_data_folder}/agentskills-spec.json` (or appropriate format)
 - If fetch succeeds: display "agentskills.io spec updated."
 - If fetch fails: display "Could not fetch agentskills.io spec. Existing spec (if any) unchanged."
 - Do NOT fail the workflow over this — it is purely optional

package/src/workflows/setup-forge/workflow.md

@@ -1,13 +1,13 @@
 ---
 name: setup-forge
-description: Initialize forge environment, detect tools, set tier, auto-index project
+description: Initialize forge environment, detect tools, set tier, verify QMD collection hygiene
 web_bundle: true
 installed_path: '{project-root}/_bmad/skf/workflows/skillforge/setup-forge'
 ---
 
 # Setup Forge
 
-**Goal:** Initialize the forge environment by detecting available tools, determining the capability tier (Quick/Forge/Deep), writing persistent configuration, and optionally indexing the project for deep search.
+**Goal:** Initialize the forge environment by detecting available tools, determining the capability tier (Quick/Forge/Forge+/Deep), writing persistent configuration, and optionally indexing the project for deep search.
 
 **Your Role:** You are a system executor performing environment resolution. This is a fully autonomous workflow — no user interaction is required during execution. Run each step in sequence, write configuration files, and report results at completion.
 
@@ -15,7 +15,7 @@ installed_path: '{project-root}/_bmad/skf/workflows/skillforge/setup-forge'
 
 ### Core Principles
 
-- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
+- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere to 1 file as directed at a time
 - **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **Fully Autonomous**: All steps auto-proceed with no user interaction until the final report
@@ -44,6 +44,7 @@ installed_path: '{project-root}/_bmad/skf/workflows/skillforge/setup-forge'
 Load and read full config from {project-root}/_bmad/skf/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+- `skills_output_folder`, `forge_data_folder`, `sidecar_path`
 
 ### 2. First Step Execution
 

package/src/workflows/test-skill/data/scoring-rules.md

@@ -17,6 +17,8 @@
 
 ## Naive Mode Weight Redistribution
 
+The following weights replace the default table for naive mode. The 18% coherence weight from the default table has been proportionally redistributed into these values. Do not apply a second redistribution.
+
 When running in naive mode (no coherence category):
 - Export Coverage: 45%
 - Signature Accuracy: 25%
@@ -38,6 +40,7 @@ tessl evaluates SKILL.md body content only — it does not read `references/*.md
 - Signature Accuracy: skipped (no AST)
 - Type Coverage: skipped (no AST)
 - Score based on: structural completeness only
+- Weight redistribution: skipped categories' weights (Signature Accuracy 22% + Type Coverage 14%) redistributed proportionally to remaining active categories
 
 ### Forge Tier (ast-grep)
 - Export Coverage: AST-backed export comparison
@@ -45,6 +48,11 @@ tessl evaluates SKILL.md body content only — it does not read `references/*.md
 - Type Coverage: AST-verified type completeness
 - Full scoring formula applied
 
+### Forge+ Tier (ast-grep + ccc)
+- Same scoring as Forge tier — ccc provides pre-ranking but does not change scoring weights
+- Improved extraction coverage (from ccc pre-discovery) may increase T1 count, but scoring formula is identical to Forge
+- Full scoring formula applied
+
 ### Deep Tier (ast-grep + gh + QMD)
 - All Forge tier checks plus:
 - Cross-repository reference verification

package/src/workflows/test-skill/data/source-access-protocol.md

@@ -32,7 +32,7 @@ If no provenance-map.json exists (typical for quick-skill output), fall back to
 If neither provenance-map nor metadata exports provide a usable baseline, but remote reading tools (zread, deepwiki, gh API, or similar) are available and `source_repo` is set in metadata.json, read the entry point remotely to build the export inventory from scratch. Name-matching only — no AST. Set `analysis_confidence: remote-only`.
 
 **State 5 — No source access at all:**
-If none of the above succeed, fall through to docs-only mode (section 0 already handles this). Set `analysis_confidence: docs-only`. Warn: "**No source access available.** Coverage check evaluates documentation self-consistency only. Re-run with local clone or remote access for source-backed verification."
+If none of the above succeed, fall through to docs-only mode (as defined in step-01-init.md Section 0: pre-analysis source type detection). Set `analysis_confidence: docs-only`. Warn: "**No source access available.** Coverage check evaluates documentation self-consistency only. Re-run with local clone or remote access for source-backed verification."
 
 Set `analysis_confidence` in context for use in Section 2 analysis depth, step-05 output, and step-05 scoring.
 

package/src/workflows/test-skill/steps-c/step-01-init.md

@@ -112,7 +112,7 @@ Log each issue as a pre-check finding. Continue with testing — frontmatter iss
 Read `{sidecarFile}` to determine available analysis depth.
 
 **If forge-tier.yaml exists:**
-- Read `tier` value (Quick, Forge, or Deep)
+- Read `tier` value (Quick, Forge, Forge+, or Deep)
 - Read tool availability flags (ast_grep, gh_cli, qmd)
 
 **If forge-tier.yaml missing:**
@@ -124,7 +124,7 @@ Default to Quick tier and continue.
 
 ### 4b. Apply Tier Override (if set)
 
-Read `{sidecar_path}/preferences.yaml`. If `tier_override` is set and is a valid tier value (Quick, Forge, or Deep), update `detected_tier` to the override value for use in subsequent steps and output documents.
+Read `{sidecar_path}/preferences.yaml`. If `tier_override` is set and is a valid tier value (Quick, Forge, Forge+, or Deep), update `detected_tier` to the override value for use in subsequent steps and output documents.
 
 ### 5. Load Skill Metadata
 
@@ -150,6 +150,7 @@ testMode: ''
 forgeTier: '{detected_tier}'
 testResult: ''
 score: ''
+threshold: ''
 analysisConfidence: ''
 testDate: '{current_date}'
 stepsCompleted: ['step-01-init']

package/src/workflows/test-skill/steps-c/step-02-detect-mode.md

@@ -86,6 +86,8 @@ Read the skill metadata (loaded in step 01) and check:
 - Default to **naive mode** (conservative — fewer checks, less chance of false negatives from missing context)
 - Note the default in the report
 
+**Quick-tier adjustment (applies to both modes):** If `forge_tier` is `Quick`, Signature Accuracy and Type Coverage are skipped during scoring (no AST available). Their weights are redistributed proportionally to remaining active categories. See `scoring-rules.md` Tier-Dependent Scoring section for details.
+
 ### 3. Update Output Document
 
 Update `{outputFile}` frontmatter:

package/src/workflows/test-skill/templates/test-report-template.md

@@ -6,6 +6,7 @@ testMode: ''
 forgeTier: ''
 testResult: ''
 score: ''
+threshold: ''
 analysisConfidence: ''
 testDate: ''
 stepsCompleted: []
@@ -20,6 +21,8 @@ nextWorkflow: ''
 
 ## Coherence Analysis
 
+## External Validation
+
 ## Completeness Score
 
 ## Gap Report

package/src/workflows/test-skill/workflow.md

@@ -2,7 +2,7 @@
 name: test-skill
 description: Cognitive completeness verification. Naive and contextual modes.
 web_bundle: true
-installed_path: '{project-root}/_bmad/skf/workflows/test-skill'
+installed_path: '{project-root}/_bmad/skf/workflows/skillforge/test-skill'
 ---
 
 # Test Skill
@@ -15,7 +15,7 @@ installed_path: '{project-root}/_bmad/skf/workflows/test-skill'
 
 ### Core Principles
 
-- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
+- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere to 1 file as directed at a time
 - **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array

package/src/workflows/update-skill/steps-c/step-01-init.md

@@ -89,14 +89,15 @@ Search for the test report at `{forge_data_folder}/{skill_name}/test-report-{ski
 ### 3. Load Forge Tier Configuration
 
 **Load `{sidecar_path}/forge-tier.yaml`:**
-- Extract: `tier` (Quick, Forge, or Deep), available tools
+- Extract: `tier` (Quick, Forge, Forge+, or Deep), available tools
 - If missing: **ABORT** — "No forge-tier.yaml found. Run setup-forge first to detect available tools."
 
-**Apply tier override:** Read `{sidecar_path}/preferences.yaml`. If `tier_override` is set and is a valid tier value (Quick, Forge, or Deep), use it instead of the detected tier.
+**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.
 
 **Determine analysis capabilities:**
 - **Quick:** text pattern matching only → T1-low confidence
 - **Forge:** AST structural extraction → T1 confidence
+- **Forge+:** AST structural extraction + CCC semantic ranking → T1 confidence (with ccc signals)
 - **Deep:** AST + QMD semantic enrichment → T1 + T2 confidence
 
 ### 4. Load Provenance Map

package/src/workflows/update-skill/steps-c/step-02-detect-changes.md

@@ -110,7 +110,7 @@ Launch subprocesses in parallel that compare source state against provenance map
 
 **Category C — Rename detection:**
 - Cross-reference deleted files/exports with added files/exports
-- If content similarity > 80%: classify as RENAMED instead of deleted+added
+- If content similarity > 80%: classify as RENAMED instead of deleted+added. **Similarity mechanism by tier:** Quick: compare file size ratio (within 20%) and export name overlap (>70% of exports match by name). Forge and above: use ast-grep to compare export signatures between the deleted and added files. Forge+/Deep: use CCC semantic similarity when available
 
 **Category D — Script/asset file changes:**
 - Compare `file_entries` from provenance-map.json against current source files
@@ -177,7 +177,7 @@ The skill `{skill_name}` is current — no update needed.
 | Files moved/renamed | {count} |
 | Exports affected | {total_export_changes} |
 
-**Proceeding to re-extraction of {affected_file_count} changed files...**"
+**Proceeding to re-extraction of {affected_file_count if normal mode, or gap_count if gap-driven mode} changes...**"
 
 ### 6. Present MENU OPTIONS
 

package/src/workflows/update-skill/steps-c/step-03-re-extract.md

@@ -4,8 +4,9 @@ description: 'Tier-aware AST extraction on changed files only, producing fresh e
 
 nextStepFile: './step-04-merge.md'
 extractionPatternsData: '../../create-skill/data/extraction-patterns.md'
-tierDegradationRulesData: '../data/tier-degradation-rules.md'
+extractionPatternsTracingData: '../../create-skill/data/extraction-patterns-tracing.md'
 remoteSourceResolutionData: '../data/remote-source-resolution.md'
+tierDegradationRulesData: '../../create-skill/data/tier-degradation-rules.md'
 ---
 
 # Step 3: Re-Extract Changed Exports
@@ -92,6 +93,8 @@ Perform tier-aware extraction on only the changed files identified in step 02, p
 - Extract: parameter types, return types, JSDoc/docstring comments
 - Confidence: T1 (AST-verified structural truth)
 
+**Tier degradation handling (Forge/Forge+/Deep):** If ast-grep is unavailable or fails on individual files, follow `{tierDegradationRulesData}` for fallback strategy and user notification requirements. Silent degradation is forbidden — the user must always know when AST extraction was skipped.
+
 **Deep tier (AST + QMD semantic enrichment):**
 - Perform all Forge tier extractions (T1)
 - Additionally: launch a subprocess that queries qmd_bridge for temporal context on changed exports, returning T2 evidence per export
@@ -103,7 +106,7 @@ Perform tier-aware extraction on only the changed files identified in step 02, p
 DO NOT BE LAZY — For EACH file in the change manifest with status MODIFIED, ADDED, or RENAMED, launch a subprocess that:
 
 1. Loads the source file
-2. Performs tier-appropriate extraction (Quick/Forge/Deep)
+2. Performs tier-appropriate extraction (Quick/Forge/Forge+/Deep)
 3. For each export found:
    - Record: export name, type (function/class/type/constant), signature
    - Record: file path, start line, end line
@@ -117,7 +120,24 @@ DO NOT BE LAZY — For EACH file in the change manifest with status MODIFIED, AD
 
 **For MOVED files:** Re-extract at new location to update file:line references.
 
-**Re-export tracing (Forge/Deep only):** After extracting changed files, check if any public exports from the package entry point (`__init__.py`, `index.ts`, `lib.rs`) are unresolved — particularly when a changed file is part of a module re-export chain. Follow the **Re-Export Tracing** protocol in `{extractionPatternsData}` to trace unresolved symbols to their actual definition files.
+**Re-export tracing (Forge/Deep only):** After extracting changed files, check if any public exports from the package entry point (`__init__.py`, `index.ts`, `lib.rs`) are unresolved — particularly when a changed file is part of a module re-export chain. Follow the **Re-Export Tracing** protocol in `{extractionPatternsTracingData}` to trace unresolved symbols to their actual definition files.
+
+### 2b. CCC Semantic Ranking (Forge+ and Deep with ccc)
+
+**IF `tools.ccc` is true in forge-tier.yaml:**
+
+Before aggregating extraction results, use CCC to assess semantic significance of changes:
+
+1. Run `ccc_bridge.search("{skill_name}", source_root, top_k=15)` to get the skill's most semantically central files
+2. Cross-reference the change manifest files with CCC results
+3. Files appearing in BOTH the change manifest AND CCC's top results are **semantically significant changes** — flag them for priority in the merge step
+4. Store `{ccc_significant_changes: [{file, score}]}` in context
+
+This helps the merge step (section 4) prioritize which changes are most likely to affect the skill's core content vs. peripheral modifications.
+
+CCC failures: skip ranking silently, all changes treated equally.
+
+**IF `tools.ccc` is false:** Skip this section silently.
 
 ### 3. Deep Tier QMD Enrichment (Conditional)
 
@@ -200,7 +220,7 @@ ONLY WHEN all changed files have been extracted and results compiled will you lo
 - Every changed file from manifest extracted with tier-appropriate method
 - All exports labeled with confidence tier (T1/T1-low/T2)
 - AST file:line citations on every extracted export
-- QMD enrichment performed for Deep tier (skipped with notice for Quick/Forge)
+- QMD enrichment performed for Deep tier (skipped with notice for Quick/Forge/Forge+)
 - Extraction results compiled with per-file detail
 - Summary displayed before auto-proceeding
 - No unchanged files extracted