bmad-module-skill-forge 0.5.0 → 0.6.0

package/src/workflows/setup-forge/steps-c/step-01-detect-and-tier.md

@@ -2,7 +2,7 @@
 name: 'step-01-detect-and-tier'
 description: 'Detect available tools and determine forge capability tier'
 
-nextStepFile: './step-02-write-config.md'
+nextStepFile: './step-01b-ccc-index.md'
 tierRulesData: '../data/tier-rules.md'
 ---
 
@@ -10,7 +10,7 @@ tierRulesData: '../data/tier-rules.md'
 
 ## STEP GOAL:
 
-Verify availability of the three forge tools (ast-grep, gh, qmd), read any existing configuration for re-run comparison, check for tier override, and calculate the capability tier.
+Verify availability of the four forge tools (ast-grep, gh, qmd, ccc), read any existing configuration for re-run comparison, check for tier override, and calculate the capability tier.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -30,7 +30,7 @@ Verify availability of the three forge tools (ast-grep, gh, qmd), read any exist
 
 - 🎯 Focus only on tool detection and tier calculation
 - 🚫 FORBIDDEN to write any files — that is step-02's job
-- 🚫 FORBIDDEN to skip any tool check — all 3 must be verified
+- 🚫 FORBIDDEN to skip any tool check — all 4 must be verified
 - 💬 Tool command failures are NOT errors — they indicate unavailability
 
 ## EXECUTION PROTOCOLS:
@@ -38,7 +38,7 @@ Verify availability of the three forge tools (ast-grep, gh, qmd), read any exist
 - 🎯 Follow the MANDATORY SEQUENCE exactly
 - 💾 Store all results in memory for step-02
 - 📖 Load tier-rules.md for calculation reference
-- 🚫 FORBIDDEN to proceed without checking all 3 tools
+- 🚫 FORBIDDEN to proceed without checking all 4 tools
 
 ## CONTEXT BOUNDARIES:
 
@@ -95,22 +95,38 @@ Check if the `SNYK_TOKEN` environment variable is set:
 
 This is informational only — security scan availability does NOT affect the tier level. It is recorded in forge-tier.yaml so that create-skill's validation step can report actionable guidance when security scanning is unavailable.
 
-### 7. Calculate Tier
+### 7. Verify Tool: ccc (cocoindex-code)
 
-**If `{tier_override}` is set and valid (Quick, Forge, or Deep):**
+**Step A — Binary existence:** Run `ccc --help`
+
+- If exits 0: binary confirmed. Continue to Step B.
+- If fails (command not found or error): record `{ccc: false}`. Skip Step B.
+
+**Step B — Daemon health:** Run `ccc doctor`
+
+- If daemon is running and model check OK: record `{ccc: true}` and store version string from output
+- If daemon is not running: record `{ccc: true, ccc_daemon: "stopped"}` — binary available, daemon needs starting. Step-01b will handle this.
+- If error or timeout: record `{ccc: true, ccc_daemon: "error"}` — binary works but daemon has issues.
+
+ccc availability gates the Forge+ tier and enhances Deep tier when present.
+
+### 8. Calculate Tier
+
+**If `{tier_override}` is set and valid (Quick, Forge, Forge+, or Deep):**
 - Use `{tier_override}` as `{calculated_tier}`
 - Note that override is active for the report step
 
-**If no override, apply tier rules from {tierRulesData}:**
+**If no override, apply tier rules from {tierRulesData} in order — the first matching rule wins. Do not continue checking once a match is found:**
 - `{ast_grep}` AND `{gh_cli}` AND `{qmd}` all true → **Deep**
-- `{ast_grep}` true (regardless of gh/qmd) → **Forge**
+- `{ast_grep}` AND `{ccc}` both true (regardless of gh/qmd) → **Forge+**
+- `{ast_grep}` true (regardless of ccc/gh/qmd) → **Forge**
 - Otherwise → **Quick**
 
 **If `{tier_override}` is set but invalid:** ignore it, use detected tier, flag for warning in report.
 
-### 8. Auto-Proceed
+### 9. Auto-Proceed
 
-"**Proceeding to write configuration...**"
+"**Proceeding to CCC index check...**"
 
 #### Menu Handling Logic:
 
@@ -123,7 +139,7 @@ This is informational only — security scan availability does NOT affect the ti
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN all 3 core tools have been verified, optional security scan checked, and the tier calculated will you load and read fully `{nextStepFile}` to execute the configuration write step.
+ONLY WHEN all 4 core tools have been verified, optional security scan checked, and the tier calculated will you load and read fully `{nextStepFile}` to execute the CCC index check step.
 
 ---
 
@@ -131,19 +147,20 @@ ONLY WHEN all 3 core tools have been verified, optional security scan checked, a
 
 ### ✅ SUCCESS:
 
-- All 3 tools checked via verification commands (not existence checks)
+- All 4 tools checked via verification commands (not existence checks)
 - Existing forge-tier.yaml read for re-run comparison (if present)
 - Existing preferences.yaml read for tier_override (if present)
 - Tier correctly calculated from tool results or override applied
-- All results stored in context for step-02
-- Auto-proceeded to step-02
+- All results stored in context for step-01b and step-02
+- Auto-proceeded to step-01b
 
 ### ❌ SYSTEM FAILURE:
 
-- Skipping any tool verification
+- Skipping any tool verification (ast-grep, gh, qmd, ccc — all 4 must be checked)
 - Using `which` or `command -v` instead of verification commands
 - Assuming tool availability without running the command
 - Writing files in this step (that is step-02)
 - Not checking for existing configuration on re-runs
+- Not checking ccc availability (both binary and daemon health)
 
 **Master Rule:** Every tool MUST be verified empirically. No assumptions, no shortcuts.

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:
+  - Store `{ccc_index_result: "stale", ccc_indexed_path: {existing path}, ccc_last_indexed: {existing timestamp}}` — proceed to section 3 for re-index
+
+- 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

@@ -63,18 +63,32 @@ 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_status from step-01b: "fresh"|"created"|"none"|"failed"}
+  staleness_threshold_hours: 24
+
+# CCC index registry (tracks which source paths have been indexed for skill workflows)
+ccc_index_registry: []
+
 # QMD collection registry (populated by create-skill, consumed by audit/update-skill)
 # Each entry tracks a QMD collection created during skill workflows
 qmd_collections: []
 ```
 
+**Note on re-runs:** The `qmd_collections` and `ccc_index_registry` arrays must be preserved across re-runs. Before overwriting forge-tier.yaml, read the existing `qmd_collections` and `ccc_index_registry` arrays and re-inject them into the new write. These arrays are populated by create-skill workflows 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,15 +104,19 @@ 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
+# Language defaults
+output_language: ~
+skill_format_version: ~
+
+# Output preferences
+citation_style: ~
+confidence_display: ~
 ```
 
 **If it DOES exist:** Do not modify. Preserve entirely.
@@ -133,7 +151,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:** 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)
 

package/src/workflows/setup-forge/validation-report.md

@@ -403,7 +403,7 @@ No subprocess optimization needed. The workflow is appropriately simple and sequ
 |-------------|------------|---------|
 | Initialize forge environment | Yes — all 4 steps address this | High |
 | Detect tools (ast-grep, gh, qmd) | Yes — step-01 verifies all 3 | High |
-| Set tier (Quick/Forge/Deep) | Yes — step-01 calculates, step-02 writes | High |
+| Set tier (Quick/Forge/Forge+/Deep) | Yes — step-01 calculates, step-02 writes | High |
 | Auto-index project | Yes — step-03 (Deep tier only) | High |
 
 #### Classification Attributes

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

@@ -32,7 +32,7 @@ Initialize forge environment, detect tools, set tier, auto-index project
 ### Original Steps (Complete List)
 
 **Step 1:** detect-tools - Check for gh, ast-grep, QMD availability
-**Step 2:** determine-tier - Set Quick/Forge/Deep based on tools found
+**Step 2:** determine-tier - Set Quick/Forge/Forge+/Deep based on tools found
 **Step 3:** create-config - Generate forge-config.yaml with tier and tool flags
 **Step 4:** auto-index - Index current project as QMD collection (Deep only)
 **Step 5:** report - Display forge status, tier, and capabilities
@@ -65,7 +65,7 @@ Initialize forge environment, detect tools, set tier, auto-index project
 
 **What works well in original:**
 - Clear 5-step decomposition with logical progression
-- Well-defined progressive tier system (Quick/Forge/Deep)
+- Well-defined progressive tier system (Quick/Forge/Forge+/Deep)
 - Three distinct output artifacts with clear purposes
 - Correctly identified as foundation workflow all others depend on
 
@@ -104,9 +104,9 @@ Initialize forge environment, detect tools, set tier, auto-index project
 
 **Structure Implications:**
 - Simple `steps-c/` folder only, no edit/validate modes
-- No `step-01b-continue.md` needed
+- step-01b added for CCC index verification (Forge+ integration)
 - No document template — output is config files written directly
-- Standard init step without continuation logic
+- Standard init step with step-01b bridge to config writing
 
 ---
 
@@ -179,7 +179,7 @@ Initialize forge environment, detect tools, set tier, auto-index project
 - Frequency: Single execution per run (idempotent, safe to re-run)
 
 **Success Criteria:**
-- All 3 tools (ast-grep, gh, qmd) verified via version/status commands, results accurately recorded
+- All 4 tools (ast-grep, gh, qmd, ccc) verified via version/status commands, results accurately recorded
 - Correct tier assigned from tool availability (or tier_override respected if set)
 - forge-tier.yaml written with tools, tier, and tier_detected_at timestamp
 - preferences.yaml exists with defaults (created on first run, preserved on re-run)
@@ -233,6 +233,7 @@ setup-forge/
 │   └── tier-rules.md             # Tier calculation rules + capability descriptions
 └── steps-c/
     ├── step-01-detect-and-tier.md
+    ├── step-01b-ccc-index.md
     ├── step-02-write-config.md
     ├── step-03-auto-index.md
     └── step-04-report.md
@@ -244,9 +245,10 @@ No templates/ directory (non-document workflow).
 
 | Step | File | Type | Menu | Goal |
 |------|------|------|------|------|
-| 01 | step-01-detect-and-tier.md | Init (Non-Continuable) | Auto-proceed | Verify 3 tools functional, check tier_override, calculate tier, read previous tier |
+| 01 | step-01-detect-and-tier.md | Init (Non-Continuable) | Auto-proceed | Verify 4 tools functional (ast-grep, gh, qmd, ccc), check tier_override, calculate tier, read previous tier |
+| 01b | step-01b-ccc-index.md | Middle (Simple + Conditional) | Auto-proceed | Verify/create CCC index for Forge+/Deep tiers when ccc available, skip silently otherwise |
 | 02 | step-02-write-config.md | Middle (Simple) | Auto-proceed | Write forge-tier.yaml, create preferences.yaml defaults if missing, ensure forge-data/ exists |
-| 03 | step-03-auto-index.md | Middle (Simple + Conditional) | Auto-proceed | QMD index project (Deep only), skip gracefully otherwise |
+| 03 | step-03-auto-index.md | Middle (Simple + Conditional) | Auto-proceed | QMD index project (Deep only) + CCC registry hygiene, skip gracefully otherwise |
 | 04 | step-04-report.md | Final Step | None | Display status with positive framing, handle --update-spec, report tier changes |
 
 ### Step Detail: step-01-detect-and-tier
@@ -384,8 +386,8 @@ step-01 ──→ step-02 ──→ step-03 ──→ step-04
 - Type: Init (Non-Continuable)
 - Input Discovery: No
 - Menu: Auto-proceed (Pattern 3)
-- Next Step: step-02-write-config.md
-- No step-01b needed (single-session)
+- Next Step: step-01b-ccc-index.md
+- step-01b handles CCC index verification before config writing
 
 **Supporting Files:**
 - data/tier-rules.md (created in foundation step)

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

@@ -7,7 +7,7 @@ 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.
 

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

@@ -45,6 +45,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/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
 

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/validation-report.md

@@ -247,7 +247,7 @@ Each step has explicit CONTEXT BOUNDARIES with FORBIDDEN markers preventing scop
 
 ### Error Handling: Good
 
-- step-01: Three-tier handling (hard stop for missing SKILL.md, warning for missing metadata.json, graceful default for missing forge-tier.yaml). Checks `preferences.yaml` for `tier_override` after loading forge tier.
+- step-01: Four-tier handling (hard stop for missing SKILL.md, warning for missing metadata.json, graceful default for missing forge-tier.yaml). Checks `preferences.yaml` for `tier_override` after loading forge tier.
 - step-03/04: Subprocess fallback rules at multiple locations
 - step-06: Zero-gaps clean pass path
 
@@ -299,7 +299,7 @@ Subprocess optimization correctly concentrated in steps 03 and 04 (heavy analysi
 ### Strengths:
 
 1. Rigorous traceability (zero hallucination with file:line citations)
-2. Three-tier depth scaling (Quick/Forge/Deep)
+2. Four-tier depth scaling (Quick/Forge/Forge+/Deep)
 3. Clean separation of concerns with explicit FORBIDDEN markers
 4. Well-designed subprocess optimization with structured return formats
 5. Actionable remediation quality rules with good/bad examples

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

@@ -76,7 +76,7 @@ Cognitive completeness verification — Verifies that a skill is complete enough
 - No frontmatter configuration for steps
 - No data files, templates, or output format specifications
 - Batch mode mechanics are unspecified
-- No forge tier awareness — coverage depth must scale with Quick/Forge/Deep tiers
+- No forge tier awareness — coverage depth must scale with Quick/Forge/Forge+/Deep tiers
 - No reference to forge-tier.yaml sidecar state for tier detection
 - Zero hallucination principle not encoded — scoring must trace to AST citations
 
@@ -274,7 +274,7 @@ Ferris (Audit mode): methodical, precise, evidence-based. Zero hallucination —
 workflowType: 'test-skill'
 skillName: '{skill_name}'
 testMode: '{naive|contextual}'
-forgeTier: '{Quick|Forge|Deep}'
+forgeTier: '{Quick|Forge|Forge+|Deep}'
 testResult: '{pass|fail}'
 score: '{N%}'
 threshold: '{N%}'

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