bmad-module-skill-forge 0.5.0 → 0.6.0

package/src/knowledge/progressive-capability.md

@@ -2,7 +2,7 @@
 
 ## Principle
 
-Every capability tier — Quick, Forge, and Deep — produces legitimate, useful skills. Tiers describe what tools are available, not a quality hierarchy. A Quick skill is complete at its tier; a Deep skill adds depth, not correctness. Framing is always positive: describe what each tier enables, never what it lacks.
+Every capability tier — Quick, Forge, Forge+, and Deep — produces legitimate, useful skills. Tiers describe what tools are available, not a quality hierarchy. A Quick skill is complete at its tier; a Deep skill adds depth, not correctness. Framing is always positive: describe what each tier enables, never what it lacks.
 
 ## Rationale
 
@@ -24,6 +24,7 @@ With progressive capability:
 | --- | --- | --- | --- |
 | Quick | No tools required | Fast, template-driven, package-name resolution | Speed-first skill creation |
 | Forge | ast-grep available | AST-backed structural analysis, line-level citations | Precision-focused compilation |
+| Forge+ | ast-grep + ccc | Semantic discovery + AST verification, pre-ranked extraction | Intelligent precision compilation |
 | Deep | ast-grep + gh + qmd | AST + GitHub exploration + QMD synthesis, maximum provenance | Full intelligence pipeline |
 
 ## Pattern Examples
@@ -35,12 +36,13 @@ With progressive capability:
 **Implementation:** Each tool is verified by executing its version command — presence in PATH is insufficient. The tier is the highest level where all required tools pass verification:
 
 ```
-ast-grep --version  → required for Forge
+ast-grep --version  → required for Forge and above
+ccc --help + ccc doctor → required for Forge+
 gh --version        → required for Deep
 qmd status          → required for Deep
 ```
 
-If ast-grep passes but gh fails, the tier is Forge (not a "degraded Deep").
+If ast-grep passes but gh fails, the tier is Forge (not a "degraded Deep"). If ast-grep and ccc pass but gh and qmd fail, the tier is Forge+ (not a "degraded Deep").
 
 **Key Points:**
 - Tools must be functional, not just installed
@@ -59,6 +61,10 @@ Quick:  "Fast, template-driven skill creation — package-name resolution and
 Forge:  "AST-backed structural analysis — line-level citations with verified
          signatures. Precision-focused compilation."
 
+Forge+: "Semantic-guided precision compilation — cocoindex-code maps the codebase
+         semantically before AST extraction runs. Every skill begins with a ranked
+         discovery pass, then AST-backed verification."
+
 Deep:   "Full intelligence pipeline — AST verification plus GitHub exploration
          and QMD knowledge synthesis. Maximum provenance depth."
 ```
@@ -75,6 +81,7 @@ Deep:   "Full intelligence pipeline — AST verification plus GitHub exploration
 **Implementation:**
 - **Quick:** Reads source files, applies pattern matching for exports and signatures, produces T1-low citations. Uses `gh_bridge` for file structure when available as a convenience, not a requirement.
 - **Forge:** Uses `ast_bridge.scan_definitions()` for structural parsing, produces T1 citations with exact AST node types. Falls back to source reading for files ast-grep cannot parse.
+- **Forge+:** Identical extraction to Forge, plus ccc semantic pre-discovery narrows the file set before ast-grep runs. For large codebases, `ccc_bridge.search()` produces a ranked candidate list. ast-grep operates on that list rather than the full tree. All results remain T1 (AST-verified) — ccc is upstream, not in the extraction chain.
 - **Deep:** Identical extraction to Forge, plus QMD enrichment in a separate step. T2 annotations layer on top of the T1 base without replacing it.
 
 **Key Points:**
@@ -89,6 +96,7 @@ Deep:   "Full intelligence pipeline — AST verification plus GitHub exploration
 **Implementation:**
 - **Quick (Naive mode):** Export Coverage 45%, Signature Accuracy 25%, Type Coverage 20%, External Validation 10%. No coherence check — AST verification unavailable. When external validation tools (skill-check, tessl) are unavailable, their 10% is redistributed proportionally across the remaining categories.
 - **Forge (Contextual mode):** Export Coverage 40%, Signature Accuracy 25%, Type Coverage 15%, Coherence 20%. Full AST-backed verification.
+- **Forge+ (Contextual mode):** Same weights as Forge. The improved extraction coverage (from ccc pre-ranking) may increase T1 count and reduce gaps, but the scoring weights themselves do not change.
 - **Deep (Contextual mode):** Same weights as Forge, plus cross-repo verification and QMD coherence checks feed into the coherence score.
 
 **Key Points:**
@@ -104,7 +112,7 @@ When a tool becomes unavailable mid-session (e.g., ast-grep uninstalled between
 3. New extractions use the current tier's capabilities
 4. The tier change is logged in the sidecar for audit trail
 
-When source is remote (GitHub URL) and tier is Forge or Deep:
+When source is remote (GitHub URL) and tier is Forge, Forge+, or Deep:
 1. AST extraction requires local files — ast-grep cannot operate on remote URLs
 2. The extraction step attempts an **ephemeral shallow clone** to a system temp path (if `git` is available)
 3. If the clone succeeds: AST extraction proceeds on the local clone, then the temp directory is cleaned up

package/src/knowledge/qmd-registry.md

@@ -95,6 +95,20 @@ Human readability alone is not sufficient justification — the file is already
 
 **Rejection reason:** Decision artifact, not a compilation input. The analyze-source report tells users which skills to create, but create-stack-skill works from individual skill artifacts, not the analysis report. The only consumer would be a human reading the file — which they can do directly.
 
+## Relationship to CCC Index Registry
+
+The `ccc_index_registry` array in forge-tier.yaml is a **parallel but separate** registry from `qmd_collections`. They track different things:
+
+| Aspect | QMD Collections | CCC Index Registry |
+|--------|----------------|-------------------|
+| **What is indexed** | Curated workflow artifacts (SKILL.md, briefs, temporal data) | Source code (the actual codebase) |
+| **Index engine** | QMD (BM25 + optional vector search) | cocoindex-code (AST + vector embeddings) |
+| **Lifecycle** | Per-skill: created by create-skill, consumed by audit/update-skill | Per-project: created by setup-forge, verified by create-skill |
+| **Janitor** | setup-forge step-03 (orphan/stale QMD collection cleanup) | setup-forge step-03 section 5b (stale path cleanup) |
+| **Availability** | Deep tier only | Forge+ and Deep tiers |
+
+These registries are orthogonal — they never reference each other, and their janitor sections operate independently.
+
 ## Pattern Examples
 
 ### Example 1: Producer Registration (create-skill)

package/src/knowledge/skf-knowledge-index.csv

@@ -2,7 +2,8 @@ id,name,description,tags,tier,fragment_file
 overview,Knowledge Overview,"Entry point — knowledge map, JiT loading protocol, relationship to workflow data/ files","knowledge,navigation,jit-loading",core,knowledge/overview.md
 zero-hallucination,Zero Hallucination Principle,"Foundational principle — uncitable content is excluded not guessed, every claim traces to source","integrity,provenance,extraction",core,knowledge/zero-hallucination.md
 confidence-tiers,Confidence Tiers,"Trust model — T1/T1-low/T2/T3 labels, citation formats, tier interaction rules","confidence,citations,evidence,tiers",core,knowledge/confidence-tiers.md
-progressive-capability,Progressive Capability,"Quick/Forge/Deep philosophy — every tier is legitimate, positive framing, graceful degradation","tiers,quick,forge,deep,capability",core,knowledge/progressive-capability.md
+progressive-capability,Progressive Capability,"Quick/Forge/Forge+/Deep philosophy — every tier is legitimate, positive framing, graceful degradation","tiers,quick,forge,forge+,deep,capability",core,knowledge/progressive-capability.md
+ccc-bridge,CCC Bridge,"cocoindex-code semantic discovery — ccc_bridge interface, indexing lifecycle, Forge+ tier, discovery-before-extraction principle","ccc,cocoindex,semantic,discovery,forge+,bridge",core,knowledge/ccc-bridge.md
 agentskills-spec,agentskills.io Specification,"Format principles — frontmatter, progressive disclosure, directory structure, compliance rules, MCP tool naming, script quality, development methodology","agentskills,format,compliance,output,mcp,scripts,methodology",core,knowledge/agentskills-spec.md
 skill-lifecycle,Skill Lifecycle,"End-to-end pipeline — workflow connections, artifact flow, decision rules for workflow selection","lifecycle,pipeline,workflows,artifacts",core,knowledge/skill-lifecycle.md
 provenance-tracking,Provenance Tracking,"Provenance mechanism — provenance-map.json entries and file_entries, evidence reports, claim traceability","provenance,evidence,traceability,citations,file-entries",core,knowledge/provenance-tracking.md

package/src/module-help.csv

@@ -1,5 +1,5 @@
 module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
-skf,anytime,Setup Forge,SF,,_bmad/skf/workflows/skillforge/setup-forge/workflow.md,skf_setup_forge,false,ferris,Create Mode,"Initialize forge environment — detect tools and set capability tier (Quick/Forge/Deep)",,forge-config.yaml,
+skf,anytime,Setup Forge,SF,,_bmad/skf/workflows/skillforge/setup-forge/workflow.md,skf_setup_forge,false,ferris,Create Mode,"Initialize forge environment — detect tools and set capability tier (Quick/Forge/Forge+/Deep)",,forge-config.yaml,
 skf,anytime,Analyze Source,AN,,_bmad/skf/workflows/skillforge/analyze-source/workflow.md,skf_analyze_source,false,ferris,Create Mode,"Discover what to skill in a large repo — produces recommended skill briefs",forge_data_folder,skill-brief.yaml,
 skf,anytime,Brief Skill,BS,,_bmad/skf/workflows/skillforge/brief-skill/workflow.md,skf_brief_skill,false,ferris,Create Mode,"Design a skill scope through guided discovery",forge_data_folder,skill-brief.yaml,
 skf,anytime,Create Skill,CS,,_bmad/skf/workflows/skillforge/create-skill/workflow.md,skf_create_skill,false,ferris,Create Mode,"Compile a skill from a brief — supports --batch for multiple briefs",skills_output_folder,SKILL.md,

package/src/module.yaml

@@ -2,7 +2,7 @@ code: skf
 name: "SKF: Skill Forge — Evidence-Based Agent Skills Compiler"
 header: "Turn code and docs into instructions AI agents can actually follow"
 subheader: "Every instruction traces to source. Zero hallucination tolerance."
-description: "Skill Forge transforms code repositories, documentation, and developer discourse into agentskills.io-compliant, version-pinned, provenance-backed agent skills. Uses ast-grep for structural truth, QMD for knowledge intelligence, and a progressive capability model (Quick/Forge/Deep). Standalone module — no other modules required. Recommended alongside BMM for full development workflow integration."
+description: "Skill Forge transforms code repositories, documentation, and developer discourse into agentskills.io-compliant, version-pinned, provenance-backed agent skills. Uses ast-grep for structural truth, cocoindex-code for semantic discovery, QMD for knowledge intelligence, and a progressive capability model (Quick/Forge/Forge+/Deep). Standalone module — no other modules required. Recommended alongside BMM for full development workflow integration."
 default_selected: false
 
 skills_output_folder:

package/src/workflows/README.md

@@ -91,7 +91,7 @@ Steps execute sequentially via just-in-time loading. Only the current step is in
 
 **4 steps** | **Data:** tier-rules.md
 
-Detects available tools (ast-grep, gh, QMD), determines the capability tier (Quick/Forge/Deep), writes `forge-tier.yaml` to the sidecar, and optionally indexes the project. Run this first — all other workflows adapt behavior to the detected tier.
+Detects available tools (ast-grep, gh, QMD), determines the capability tier (Quick/Forge/Forge+/Deep), writes `forge-tier.yaml` to the sidecar, and optionally indexes the project. Run this first — all other workflows adapt behavior to the detected tier.
 
 ### analyze-source (AN)
 

package/src/workflows/analyze-source/data/skill-brief-schema.md

@@ -14,7 +14,7 @@ Defines the output contract for skill-brief.yaml files generated by analyze-sour
 | language | string | Recognized language | Primary programming language |
 | scope | object | See Scope Object below | Boundary definition |
 | description | string | 1-3 sentences | What the skill covers |
-| forge_tier | string | `quick` / `forge` / `deep` | Inherited from forge-tier.yaml |
+| forge_tier | string | `quick` / `forge` / `forge+` / `deep` | Inherited from forge-tier.yaml |
 | created | string | ISO date `YYYY-MM-DD` | Generation date |
 | created_by | string | user_name from config | Who generated the brief |
 

package/src/workflows/analyze-source/data/unit-detection-heuristics.md

@@ -111,4 +111,5 @@ Flag units as stack skill candidates when:
 |------------|-------------------|
 | Quick | File structure analysis: directory trees, manifest files, entry points, naming conventions |
 | Forge | AST analysis: export surfaces, import graphs, dependency trees, type hierarchies |
+| Forge+ | AST + CCC: semantic file pre-ranking before structural analysis, CCC signals for relevance scoring |
 | Deep | AST + QMD: temporal evolution, refactoring patterns, semantic relationships, architectural drift |

package/src/workflows/analyze-source/steps-c/step-01-init.md

@@ -73,10 +73,10 @@ Look for {outputFile}.
 
 **Check forge-tier.yaml:**
 - Look for `{sidecar_path}/forge-tier.yaml`
-- **IF missing:** HARD HALT — "**Cannot proceed.** forge-tier.yaml not found at `{sidecar_path}/forge-tier.yaml`. Please run the setup-forge workflow first to configure your forge tier (Quick/Forge/Deep)."
+- **IF missing:** HARD HALT — "**Cannot proceed.** forge-tier.yaml not found at `{sidecar_path}/forge-tier.yaml`. Please run the setup-forge workflow first to configure your forge tier (Quick/Forge/Forge+/Deep)."
 - **IF found:** Read and note the forge tier value
 
-**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.
 
 "**Forge tier detected:** {tier} — analysis depth will be calibrated accordingly."
 

package/src/workflows/analyze-source/steps-c/step-04-map-and-detect.md

@@ -81,6 +81,10 @@ DO NOT BE LAZY — For EACH qualifying unit, launch a subprocess (or analyze in
 2. Counts and categorizes exports based on forge tier:
    - **Quick tier:** Count files by type, identify index/barrel files, list directory structure
    - **Forge tier:** Parse export statements, identify public API surface, count exported functions/classes/types
+   - **Forge+ tier:** All Forge analysis plus:
+     - If `tools.ccc` is true: run `ccc_bridge.search("{unit_name} exports public API", top_k=15)` to discover semantically relevant files beyond directory scan
+     - Merge CCC-discovered files with scoped file list — files from CCC that are within the unit's directory are added to the analysis queue
+     - Record CCC signals in per-unit findings: top 3 CCC-ranked file names (or "—" if no ccc results)
    - **Deep tier:** All Forge analysis plus:
      - ast-grep structural export extraction: `ast-grep -p 'export $$$' --lang typescript` or equivalent per language to build a verified export inventory
      - ast-grep type/interface mapping: `ast-grep -p 'interface $NAME' --lang typescript` or `ast-grep -p 'class $NAME($$$)' --lang python`
@@ -96,9 +100,9 @@ DO NOT BE LAZY — For EACH qualifying unit, launch a subprocess (or analyze in
 
 **Per-unit export summary:**
 
-| Unit | Files | Exports | Export Pattern | API Surface | Scripts/Assets |
-|------|-------|---------|----------------|-------------|----------------|
-| {name} | {count} | {count} | {pattern} | {small/medium/large} | {N scripts, M assets or --} |
+| Unit | Files | Exports | Export Pattern | API Surface | Scripts/Assets | CCC Signals |
+|------|-------|---------|----------------|-------------|----------------|-------------|
+| {name} | {count} | {count} | {pattern} | {small/medium/large} | {N scripts, M assets or --} | {CCC signals or --} |
 
 ### 3. Map Import Graph
 

package/src/workflows/analyze-source/validation-report.md

@@ -499,7 +499,7 @@ All steps include: "TOOL/SUBPROCESS FALLBACK: If any instruction references a su
 - **Evidence-based approach** — every recommendation backed by specific file citations
 - **Well-placed collaborative gate** (step 05) — user has agency without slowing autonomous analysis
 - **Complete data flow** — no orphaned data, every piece feeds forward
-- **Tier-aware analysis depth** — adapts to Quick/Forge/Deep
+- **Tier-aware analysis depth** — adapts to Quick/Forge/Forge+/Deep
 - **Continuation support** — large repo analysis can resume across sessions
 - **Stack skill candidate detection** — value beyond individual skills
 - **Schema validation before writing** — prevents downstream workflow failures
@@ -647,7 +647,7 @@ A developer onboarding a brownfield project would experience:
 - Complete evidence-based analysis pipeline with zero-hallucination principle
 - Well-placed collaborative gate at step 05 with Y/N/M + "why?" support
 - Perfect data flow — every step builds on previous work
-- Tier-aware analysis depth (Quick/Forge/Deep)
+- Tier-aware analysis depth (Quick/Forge/Forge+/Deep)
 - Continuation support for interrupted sessions
 - Schema validation before file writing
 - Clear downstream workflow recommendations

package/src/workflows/analyze-source/workflow-plan-analyze-source.md

@@ -150,7 +150,7 @@ Decomposition engine — discover what to skill, recommend stack skill. Analyzes
 **Inputs Required:**
 - Required: Project root or repo path
 - Required: SKF module config (forge_data_folder, skills_output_folder, forge_tier)
-- Required: forge-tier.yaml (determines Quick/Forge/Deep analysis depth)
+- Required: forge-tier.yaml (determines Quick/Forge/Forge+/Deep analysis depth)
 - Optional: Scope hints (monorepo packages, service directories to focus on)
 - Optional: Exclusion patterns (vendor dirs, test dirs, generated code to skip)
 - Prerequisites: setup-forge workflow must have been run

package/src/workflows/audit-skill/data/drift-report-template.md

@@ -13,15 +13,15 @@ nextWorkflow: ''
 previousWorkflow: 'create-skill'
 ---
 
-# Drift Report: {{skill_name}}
+# Drift Report: {skill_name}
 
 ## Audit Summary
 
-**Skill:** {{skill_name}}
-**Source:** {{source_path}}
-**Tier:** {{forge_tier}}
-**Date:** {{date}}
-**Overall Drift Score:** {{drift_score}}
+**Skill:** {skill_name}
+**Source:** {source_path}
+**Tier:** {forge_tier}
+**Date:** {date}
+**Overall Drift Score:** {drift_score}
 
 | Category | Count |
 |----------|-------|

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

@@ -82,10 +82,10 @@ Load `{sidecar_path}/forge-tier.yaml` to detect available tools.
 - HALT workflow
 
 **If found:**
-- Extract tier level: Quick / Forge / Deep
+- Extract tier level: Quick / Forge / Forge+ / Deep
 - Extract available tools: gh_bridge, ast_bridge, qmd_bridge
 
-**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.
 
 ### 3. Load Skill Artifacts
 

package/src/workflows/audit-skill/steps-c/step-02-re-index.md

@@ -134,9 +134,26 @@ Append temporal metadata to each export in the snapshot.
 Log: "No QMD extraction collection found for {skill_name}. Temporal enrichment skipped. Re-run [CS] Create Skill to generate the collection."
 Continue without T2 enrichment — this is not an error.
 
-**IF forge tier is Quick or Forge:**
+**IF forge tier is Quick, Forge, or Forge+:**
 Skip this section. Temporal context requires Deep tier.
 
+### 4b. CCC Rename Detection (Forge+ and Deep with ccc)
+
+**IF `tools.ccc` is true in forge-tier.yaml:**
+
+For each export in the skill baseline that was NOT found at its recorded file path during re-extraction (potential "deleted" export):
+
+1. Run `ccc_bridge.search("{export_name}", source_root, top_k=5)` to find candidate current locations
+2. If CCC returns files containing the export name:
+   - Run ast-grep verification on each candidate file
+   - If verified at a new location: reclassify from "deleted" to "moved" with the new file:line reference
+   - This reduces false-positive structural drift findings where exports were relocated, not removed
+3. If CCC returns no results or verification fails: keep the "deleted" classification
+
+CCC failures: skip rename detection silently, proceed with standard structural diff.
+
+**IF `tools.ccc` is false:** Skip this section silently.
+
 ### 5. Validate Extraction Completeness
 
 "**Extraction complete.**

package/src/workflows/audit-skill/steps-c/step-04-semantic-diff.md

@@ -1,6 +1,6 @@
 ---
 name: 'step-04-semantic-diff'
-description: 'Compare QMD knowledge context for meaning-level changes (Deep tier only, skip at Quick/Forge)'
+description: 'Compare QMD knowledge context for meaning-level changes (Deep tier only, skip at Quick/Forge/Forge+)'
 
 nextStepFile: './step-05-severity-classify.md'
 outputFile: '{forge_data_folder}/{skill_name}/drift-report-{timestamp}.md'
@@ -10,7 +10,7 @@ outputFile: '{forge_data_folder}/{skill_name}/drift-report-{timestamp}.md'
 
 ## STEP GOAL:
 
-Compare QMD knowledge context between the original skill creation and current state to detect meaning-level changes that structural diff cannot catch. This step executes ONLY at Deep tier — at Quick and Forge tiers, it appends a skip notice and auto-proceeds.
+Compare QMD knowledge context between the original skill creation and current state to detect meaning-level changes that structural diff cannot catch. This step executes ONLY at Deep tier — at Quick, Forge, and Forge+ tiers, it appends a skip notice and auto-proceeds.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -35,7 +35,7 @@ Compare QMD knowledge context between the original skill creation and current st
 - 🚫 FORBIDDEN to repeat structural findings from Step 03
 - 💬 Use subprocess Pattern 3 (data operations) when available for QMD queries
 - ⚙️ If subprocess unavailable, query QMD in main thread
-- 🔀 CONDITIONAL: Skip entire analysis at Quick/Forge tier — append skip notice only
+- 🔀 CONDITIONAL: Skip entire analysis at Quick/Forge/Forge+ tier — append skip notice only
 
 ## EXECUTION PROTOCOLS:
 
@@ -57,7 +57,7 @@ Compare QMD knowledge context between the original skill creation and current st
 
 ### 1. Check Forge Tier
 
-**IF forge tier is Quick or Forge:**
+**IF forge tier is Quick, Forge, or Forge+:**
 
 Append to {outputFile}:
 
@@ -179,7 +179,7 @@ ONLY WHEN the ## Semantic Drift section (or skip notice) has been appended to {o
 
 ### ✅ SUCCESS:
 
-- Forge tier checked FIRST — skip gracefully at Quick/Forge
+- Forge tier checked FIRST — skip gracefully at Quick/Forge/Forge+
 - Deep tier: QMD knowledge context queried and compared
 - All semantic findings have T2 confidence labels
 - Findings clearly distinguished from structural drift (T1)

package/src/workflows/audit-skill/validation-report.md

@@ -413,7 +413,7 @@ The audit-skill workflow is a well-designed, cohesive 6-step pipeline that achie
 ### Strengths
 
 1. **Zero-hallucination principle** enforced consistently — every finding traces to actual code
-2. **Graceful degradation** at every level — tier-aware (Quick/Forge/Deep), missing provenance (degraded mode)
+2. **Graceful degradation** at every level — tier-aware (Quick/Forge/Forge+/Deep), missing provenance (degraded mode)
 3. **Structured output** with file:line citations and confidence tier labels on all findings
 4. **Actionable remediation** — specific suggestions per finding (what to change, where, why)
 5. **Workflow chaining** — update-skill recommendation when CRITICAL/HIGH drift found
@@ -441,7 +441,7 @@ The audit-skill workflow is a well-designed, cohesive 6-step pipeline that achie
 |-------------|-------------|---------|--------|
 | Drift detection between skill and source | workflow.md + all 6 steps | High | ✅ |
 | Ferris Audit mode | workflow.md + all step role reinforcements | High | ✅ |
-| Tier-aware depth (Quick/Forge/Deep) | Steps 01-04 adapt per tier | High | ✅ |
+| Tier-aware depth (Quick/Forge/Forge+/Deep) | Steps 01-04 adapt per tier | High | ✅ |
 | Drift report with severity levels | Steps 03-06 build categorized report | High | ✅ |
 
 ### Classification Validation
@@ -534,7 +534,7 @@ None identified. All requirements from the plan are fully implemented.
 ### Key Strengths
 
 - Zero-hallucination principle enforced consistently throughout
-- Graceful tier-aware degradation (Quick/Forge/Deep)
+- Graceful tier-aware degradation (Quick/Forge/Forge+/Deep)
 - Well-chosen subprocess patterns with graceful fallbacks
 - Clean data flow: provenance → extraction → diff → classification → report
 - Actionable remediation suggestions with workflow chaining

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

@@ -54,7 +54,7 @@ Drift report with severity levels (added/removed/changed exports, breaking chang
 ### Key Instructions to LLM
 
 - Primary agent: Ferris (Audit mode)
-- Tiered operation: Forge tier (structural only) vs Deep tier (full semantic + QMD)
+- Tiered operation: Forge/Forge+ tier (structural, with optional CCC augmentation) vs Deep tier (full semantic + QMD)
 - The spec references AST diff for structural comparison and QMD for semantic context
 - CI integration is noted as optional export (ADR-A decision)
 
@@ -70,7 +70,7 @@ Drift report with severity levels (added/removed/changed exports, breaking chang
 - Document-producing output aligns with drift report use case
 
 **What needs improvement (fix during build):**
-- **Missing Quick tier path** — All SKF workflows support Quick/Forge/Deep with graceful degradation; Quick tier needs text-diff fallback
+- **Missing Quick tier path** — All SKF workflows support Quick/Forge/Forge+/Deep with graceful degradation; Quick tier needs text-diff fallback
 - **No provenance map format specification** — Step 01 loads it, but must reference known `provenance-map.json` from create-skill's `forge-data/{name}/` output
 - **No confidence tier labels (T1/T2/T3)** — Every SKF workflow uses these for traceability; drift findings need confidence scoring
 - **Step 04 conditional skip** — semantic-diff is Deep-only but spec has no skip logic or degradation behavior for Forge/Quick tiers

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

@@ -24,7 +24,7 @@ This uses **step-file architecture** for disciplined execution:
 - **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
 - **Append-Only Building**: Build the drift report by appending sections as directed to the output file
-- **Tier-Aware Execution**: Adapt analysis depth based on detected forge tier (Quick/Forge/Deep) with graceful degradation
+- **Tier-Aware Execution**: Adapt analysis depth based on detected forge tier (Quick/Forge/Forge+/Deep) with graceful degradation
 
 ### Step Processing Rules
 

package/src/workflows/brief-skill/data/skill-brief-schema.md

@@ -10,7 +10,7 @@
 | language | string | Primary programming language | Must be detected or user-specified |
 | scope | object | Inclusion/exclusion boundaries | Must have type + at least one pattern |
 | description | string | What this skill covers | 1-3 sentences |
-| forge_tier | string | Compilation tier | One of: quick, forge, deep |
+| forge_tier | string | Compilation tier | One of: quick, forge, forge+, deep |
 | created | string | Creation date | ISO date format |
 | created_by | string | User who created the brief | From config user_name |
 
@@ -67,7 +67,7 @@ source_type: "source"                    # "source" (default) or "docs-only"
 source_repo: "{github-url-or-local-path}"
 language: "{detected-language}"
 description: "{brief-description}"
-forge_tier: "{quick|forge|deep}"
+forge_tier: "{quick|forge|forge+|deep}"
 created: "{date}"
 created_by: "{user_name}"
 scope:
@@ -116,6 +116,6 @@ Created by: {created_by}
 3. `language` must be a recognized programming language
 4. `scope.type` must be one of the three defined types
 5. `scope.include` must have at least one pattern
-6. `forge_tier` must match the tier from forge-tier.yaml (or default to quick)
+6. `forge_tier` must be one of: quick, forge, forge+, deep (must match the tier from forge-tier.yaml, or default to quick)
 7. When `source_type: "docs-only"`: `doc_urls` must have >= 1 entry, `source_repo` becomes optional
 8. Each `doc_urls` entry must have a valid `url` field

package/src/workflows/brief-skill/steps-c/step-01-gather-intent.md

@@ -3,7 +3,7 @@ name: 'step-01-gather-intent'
 description: 'Initialize brief-skill workflow, discover forge tier, and gather user intent for skill creation'
 
 nextStepFile: './step-02-analyze-target.md'
-forgeTierFile: '{project-root}/_bmad/_memory/forger-sidecar/forge-tier.yaml'
+forgeTierFile: '{sidecar_path}/forge-tier.yaml'
 ---
 
 # Step 1: Gather Intent
@@ -61,10 +61,10 @@ To initialize the brief-skill workflow by discovering the forge tier configurati
 Attempt to load `{forgeTierFile}`:
 
 **If found:**
-- Read the tier level (quick, forge, or deep)
+- Read the tier level (quick, forge, forge+, or deep)
 - Note available tools for scoping guidance later
 
-**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.
 
 **If not found:**
 - Display: "**Note:** No forge tier configuration found. Defaulting to Quick tier. Run **setup-forge** first for full capabilities."

package/src/workflows/brief-skill/steps-c/step-02-analyze-target.md

@@ -131,6 +131,21 @@ Based on detected language, identify public API surface:
 **Detected Exports/Entry Points:**
 {numbered list of public-facing items found}"
 
+**Semantic Signals (Forge+ and Deep with ccc only):**
+
+If `tools.ccc` is true in forge-tier.yaml, supplement the module listing with a semantic discovery pass:
+
+Run `ccc_bridge.search("{repo_name} public API exports modules", source_path, top_k=10)`.
+
+If results are returned, display:
+
+"**Semantic Signals (ccc):**
+{numbered list of file:snippet pairs from CCC results — top 5 most relevant}"
+
+This supplements — never replaces — the explicit module list above. CCC may surface non-obvious entry points (dynamically constructed exports, re-export chains) that static directory analysis misses.
+
+If CCC is unavailable or returns no results: skip this subsection silently.
+
 ### 5. Report Analysis Summary
 
 Present the complete analysis:

package/src/workflows/create-skill/data/extraction-patterns.md

@@ -28,7 +28,7 @@ Source reading via gh_bridge — infer exports from file structure and content.
 
 Structural extraction via ast-grep — verified exports with line-level citations.
 
-> **Note:** `ast_bridge.*` and `qmd_bridge.*` references below are **conceptual interfaces**, not callable functions. They describe the operation to perform. Use ast-grep (MCP tool or CLI) for `ast_bridge.*` operations and QMD (MCP tool or CLI) for `qmd_bridge.*` operations. See the AST Extraction Protocol section below and the TOOL/SUBPROCESS FALLBACK rule for dispatch details.
+> **Note:** `ast_bridge.*`, `qmd_bridge.*`, and `ccc_bridge.*` references below are **conceptual interfaces**, not callable functions. They describe the operation to perform. Use ast-grep (MCP tool or CLI) for `ast_bridge.*` operations, QMD (MCP tool or CLI) for `qmd_bridge.*` operations, and ccc CLI or MCP for `ccc_bridge.*` operations. See the AST Extraction Protocol section below and the TOOL/SUBPROCESS FALLBACK rule for dispatch details.
 
 ### Strategy
 
@@ -52,6 +52,42 @@ Structural extraction via ast-grep — verified exports with line-level citation
 
 ---
 
+## Forge+ Tier (AST + CCC)
+
+Identical extraction to Forge tier. CCC adds an upstream semantic discovery step that pre-ranks the file extraction queue.
+
+### When CCC Pre-Discovery Applies
+
+CCC pre-discovery runs in step-02b-ccc-discover (before this extraction step) when ALL of the following are true:
+- Tier is Forge+ or Deep
+- `tools.ccc: true` in forge-tier.yaml
+- `ccc_index.status` is `"fresh"`, `"stale"`, `"created"`, or `"none"`/`"failed"` (step-02b attempts lazy indexing for the latter two)
+
+The discovery step stores `{ccc_discovery: [{file, score, snippet}]}` in context. This extraction step consumes those results to pre-rank the file list.
+
+### CCC Pre-Ranking Strategy
+
+When `{ccc_discovery}` is present and non-empty:
+
+1. Files appearing in `{ccc_discovery}` results move to the front of the extraction queue, sorted by relevance score descending
+2. Files NOT in CCC results remain in the queue — they are not excluded, only deprioritized
+3. If the CCC intersection with scoped files produces <10 files: include all scoped files (CCC results too narrow)
+4. Proceed with the AST Extraction Protocol on the pre-ranked list
+
+### ast-grep Patterns
+
+Same patterns as Forge tier — see Forge tier section above. CCC pre-ranking does not change which AST patterns are used, only which files are processed first.
+
+### Confidence
+
+All results: T1 (AST-verified) — identical to Forge tier. CCC is upstream discovery only and is invisible in the output artifact.
+
+### Important
+
+CCC pre-discovery failures (ccc unavailable, command error, empty results) always result in standard Forge extraction behavior. This is not reported to the user as a problem — it is normal behavior when ccc has no relevant results for the skill's scope.
+
+---
+
 ## Deep Tier (AST + QMD)
 
 Same extraction as Forge tier. Deep tier adds enrichment in step-04, not extraction.

package/src/workflows/create-skill/data/skill-sections.md

@@ -56,7 +56,7 @@ SKILL.md uses a two-tier structure to ensure actionable content survives `split-
 - Tier 1 sections are kept short enough that `split-body` targets the larger Tier 2 sections (`## Full` headings) into `references/`
 - After split-body, SKILL.md retains all Tier 1 content — actionable without loading references
 - An agent loading only SKILL.md (no references) must get enough to act
-- **Section 4b (Migration & Deprecation Warnings)** is conditional: only emitted for Deep tier when T2-future annotations exist. Quick/Forge tiers and Deep tiers without T2-future annotations omit it entirely (no empty section). Parsers and validators must treat this section as optional.
+- **Section 4b (Migration & Deprecation Warnings)** is conditional: only emitted for Deep tier when T2-future annotations exist. Quick/Forge/Forge+ tiers and Deep tiers without T2-future annotations omit it entirely (no empty section). Parsers and validators must treat this section as optional.
 - **Section 7b (Scripts & Assets)** is conditional: only emitted when `scripts_inventory` or `assets_inventory` is non-empty. Omitted entirely when no scripts or assets are detected. Parsers and validators must treat this section as optional.
 
 ### Provenance Citation Format
@@ -120,7 +120,7 @@ Indexed pipe-delimited format for CLAUDE.md managed section (~80-120 tokens per
   "source_repo": "{github-url}",
   "source_root": "{resolved-source-path}",
   "source_commit": "{commit-hash}",
-  "confidence_tier": "{Quick|Forge|Deep}",
+  "confidence_tier": "{Quick|Forge|Forge+|Deep}",
   "spec_version": "1.3",
   "generation_date": "{ISO-8601}",
   "description": "{SKILL.md frontmatter description}",

package/src/workflows/create-skill/steps-c/step-01-load-brief.md

@@ -61,10 +61,11 @@ Halt with: "Forge halted: No forge configuration found. Run [SF] Setup Forge fir
 
 **If file exists:**
 Extract and report:
-- `tier`: Quick, Forge, or Deep
-- `tools`: which tools are available (gh, ast-grep, qmd)
+- `tier`: Quick, Forge, Forge+, or Deep
+- `tools`: which tools are available (gh, ast-grep, ccc, qmd)
+- `ccc_index`: ccc index state (status, indexed_path, last_indexed) — needed by step-02b
 
-**Apply tier override:** Read `{preferencesFile}`. 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 `{preferencesFile}`. If `tier_override` is set and is a valid tier value (Quick, Forge, Forge+, or Deep), use it instead of the detected tier.
 
 ### 2. Discover Skill Brief
 
@@ -138,6 +139,7 @@ Proceeding to ecosystem check..."
 Where tier_description follows positive capability framing:
 - Quick: "Source reading and spec validation"
 - Forge: "AST-backed structural extraction"
+- Forge+: "Semantic-guided precision — ccc pre-ranks files before AST extraction"
 - Deep: "Full intelligence — structural + contextual + temporal"
 
 ### 6. Menu Handling Logic

package/src/workflows/create-skill/steps-c/step-02-ecosystem-check.md

@@ -1,7 +1,7 @@
 ---
 name: 'step-02-ecosystem-check'
 description: 'Check agentskills.io ecosystem for existing official skill before compilation'
-nextStepFile: './step-03-extract.md'
+nextStepFile: './step-02b-ccc-discover.md'
 ---
 
 # Step 2: Ecosystem Check
@@ -131,7 +131,7 @@ If no match is found, this step auto-proceeds with no user interaction.
 - Match presented factually with clear options if found
 - No-match case auto-proceeds silently
 - User decision respected (Proceed/Install/Abort)
-- Auto-proceeded to step-03 (when no match or user chose Proceed)
+- Auto-proceeded to step-02b (when no match or user chose Proceed)
 
 ### ❌ SYSTEM FAILURE: