bmad-module-skill-forge 0.5.0 → 0.6.0

package/src/workflows/create-skill/steps-c/step-02b-ccc-discover.md

@@ -0,0 +1,157 @@
+---
+name: 'step-02b-ccc-discover'
+description: 'CCC semantic discovery pass — Forge+ and Deep tiers when ccc is available, skip for Quick/Forge'
+nextStepFile: './step-03-extract.md'
+---
+
+# Step 2b: CCC Semantic Discovery
+
+## STEP GOAL:
+
+If tier is Forge+ or Deep AND ccc is available, perform a semantic discovery pass over the source code to identify the most relevant files for the skill being created. Store ranked discovery results in context to pre-rank the file extraction queue in step-03.
+
+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
+- 🎯 ALWAYS follow the exact instructions in the step file
+- 🔄 CRITICAL: When loading next step, ensure entire file is read
+- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a tool you do not have access to, you MUST still achieve the outcome in your main context thread
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a skill compilation engine performing semantic pre-discovery
+- ✅ CCC discovery is a hint layer — it guides extraction, it does not replace it
+- ✅ Discovery failure is graceful degradation, not an error
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on running ccc semantic search and storing results
+- 🚫 FORBIDDEN to extract exports — that is step-03
+- 🚫 FORBIDDEN to modify brief data or source resolution
+- 🚫 FORBIDDEN to block the workflow if ccc fails
+- ⏱️ Quick and Forge tiers: skip this step entirely and silently
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow MANDATORY SEQUENCE exactly
+- 💾 Discovery results stored in context as `{ccc_discovery}`
+- 📖 Results are consumed by step-03 to pre-rank the file extraction queue
+- 🚫 Never treat ccc results as verified extractions
+
+## CONTEXT BOUNDARIES:
+
+- Available: tier, tools.ccc, ccc_index from forge-tier.yaml (loaded in step-01)
+- Available: brief_data (name, scope, description) from step-01
+- Available: source_root (resolved source path) from step-01
+- Focus: Semantic discovery only — no extraction, no compilation
+- Dependencies: step-02 must have completed
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Check Tier Eligibility
+
+**If tier is Quick or Forge:**
+
+Set `{ccc_discovery: []}` in context. Auto-proceed silently. Display no message. Immediately load, read entire file, then execute `{nextStepFile}`.
+
+**If tier is Forge+ or Deep:**
+
+Check `tools.ccc` from forge-tier.yaml. If `tools.ccc` is false, set `{ccc_discovery: []}` in context and auto-proceed to section 5.
+
+If `tools.ccc` is true, continue to section 2.
+
+### 2. Check CCC Index State
+
+Read `ccc_index` from forge-tier.yaml:
+
+- If `ccc_index.status` is `"fresh"`: continue to section 3.
+- If `ccc_index.status` is `"stale"`: display brief note — "CCC index is stale — discovery results may miss recent changes." Continue to section 3.
+- If `ccc_index.status` is `"none"` or `"failed"`: attempt lazy indexing via `ccc_bridge.ensure_index(source_root)`. If indexing succeeds, continue to section 3. If indexing fails, set `{ccc_discovery: []}` and auto-proceed to section 5.
+
+### 3. Construct Semantic Query
+
+Build the discovery query from the brief data:
+
+**Primary query:** `"{brief.name} {brief.scope}"`
+
+Where:
+- `brief.name` is the skill name from the brief
+- `brief.scope` is the scope field (e.g., "Full library", "Public API", or specific module names)
+
+**Query length cap:** Truncate to 80 characters if longer — ccc semantic search is sensitive to overly long queries. When truncating, keep the full skill name and trim `brief.scope` from the end. If `brief.scope` is very short (< 10 chars), append terms from `brief.description` to fill the remaining space.
+
+### 4. Execute CCC Semantic Search
+
+Run `ccc_bridge.search(query, source_root, top_k=20)`:
+
+**If search succeeds:**
+
+Store results as `{ccc_discovery: [{file, score, snippet}]}` in context.
+
+Display brief discovery summary:
+
+"**CCC semantic discovery: {N} relevant regions identified across {M} unique files.**"
+
+Where:
+- `{N}` is the total result count
+- `{M}` is the count of unique file paths in results
+
+**If search fails (any error):**
+
+Set `{ccc_discovery: []}` in context.
+
+Display: "CCC discovery unavailable — proceeding with standard extraction."
+
+Do NOT halt. This is not an error.
+
+**If search returns empty results:**
+
+Set `{ccc_discovery: []}` in context.
+
+No message needed — empty results are normal for small or highly focused libraries.
+
+### 5. Auto-Proceed
+
+Immediately load, read entire file, then execute `{nextStepFile}`.
+
+#### EXECUTION RULES:
+
+- This is an auto-proceed step with no user choices
+- Quick/Forge tiers skip directly with no output
+- Forge+/Deep with ccc displays brief discovery summary then auto-proceeds
+- CCC failures do not halt — degrade and proceed
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN discovery is complete (Forge+/Deep with ccc) or the step is skipped (Quick/Forge or ccc unavailable) will you proceed to load `{nextStepFile}` for AST extraction.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Quick/Forge tiers: skipped silently with no output, auto-proceeded
+- Forge+/Deep with ccc: semantic query constructed from brief data
+- Forge+/Deep with ccc: ccc_bridge.search executed, results stored as `{ccc_discovery}` in context
+- Discovery summary displayed (count of regions and unique files)
+- CCC failures handled gracefully (empty discovery, continue)
+- Auto-proceeded to step-03
+
+### ❌ SYSTEM FAILURE:
+
+- Halting on CCC unavailability or search failures
+- Extracting exports or signatures (that is step-03)
+- Displaying skip messages for Quick/Forge tiers
+- Treating CCC discovery results as verified extractions
+- Not storing `{ccc_discovery}` in context (even if empty)
+- Beginning compilation or SKILL.md assembly in this step
+
+**Master Rule:** CCC discovery is a hint layer. It improves extraction coverage but never replaces structural verification. Failures degrade gracefully.

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

@@ -92,7 +92,16 @@ Load `{sourceResolutionData}` completely. Follow the **Remote Source Resolution*
 5. Infer types from JSDoc, docstrings, type annotations
 6. Confidence: All results T1-low — `[SRC:{file}:L{line}]`
 
-**Forge/Deep Tier (AST available):**
+**Forge/Forge+/Deep Tier (AST available):**
+
+**CCC Discovery Integration (Forge+ and Deep with ccc only):**
+
+If `{ccc_discovery}` is in context and non-empty (populated by step-02b):
+- Sort the filtered file list by CCC relevance score: files appearing in `{ccc_discovery}` results move to the front of the extraction queue, sorted by their relevance score descending
+- Files NOT in CCC results remain in the queue after ranked files — they are not excluded, only deprioritized
+- Display: "**CCC discovery: {N} files pre-ranked by semantic relevance** — extraction will prioritize these first."
+
+If `{ccc_discovery}` is empty or not in context: proceed with existing file ordering (no change to current behavior).
 
 ⚠️ **CRITICAL:** Before executing AST extraction, load the **AST Extraction Protocol** section from `{extractionPatternsData}`. Follow the decision tree based on the file count from step-01's file tree. This determines whether to use the MCP tool, scoped YAML rules, or CLI streaming. Never use `ast-grep --json` (without `=stream`) — it loads the entire result set into memory and will fail on large codebases.
 

package/src/workflows/create-skill/steps-c/step-03b-fetch-temporal.md

@@ -27,7 +27,7 @@ To fetch temporal context (issues, PRs, changelogs, release notes) from the sour
 
 ### Step-Specific Rules:
 
-- 🎯 Deep tier only — Quick and Forge tiers skip this step entirely and silently
+- 🎯 Deep tier only — Quick, Forge, and Forge+ tiers skip this step entirely and silently
 - 🎯 GitHub repositories only — other source types degrade gracefully
 - 🚫 FORBIDDEN to halt the workflow if fetching or indexing fails
 - 🚫 FORBIDDEN to modify extraction data from step-03 — this step only creates QMD collections
@@ -56,7 +56,7 @@ To fetch temporal context (issues, PRs, changelogs, release notes) from the sour
 
 Evaluate the following conditions sequentially. **If ANY condition fails, skip silently to section 5 (auto-proceed) with no output:**
 
-1. **Tier is Deep:** If tier is Quick or Forge, skip silently.
+1. **Tier is Deep:** If tier is Quick, Forge, or Forge+, skip silently.
 2. **Source is GitHub:** Verify `source_repo` is a GitHub URL (`https://github.com/...`) or `owner/repo` format. If the source is a local path, a non-GitHub URL, or any other format, skip silently.
 3. **`gh` CLI is available:** Run `gh auth status` to verify the CLI is installed and authenticated. If it fails, skip silently.
 
@@ -200,7 +200,7 @@ After temporal context is fetched and indexed (or skipped for any reason), immed
 #### EXECUTION RULES:
 
 - This is an auto-proceed step with no user choices
-- Quick/Forge tiers skip directly to next step with no output
+- Quick/Forge/Forge+ tiers skip directly to next step with no output
 - Non-GitHub sources skip directly to next step with no output
 - Cached collections (< 7 days old) skip with brief cache-hit message
 - Deep tier with fresh fetch displays brief confirmation then auto-proceeds
@@ -216,7 +216,7 @@ ONLY WHEN temporal context is indexed into QMD (or the step is skipped due to el
 
 ### ✅ SUCCESS:
 
-- Non-eligible scenarios (Quick/Forge tier, non-GitHub source, no `gh` CLI) skipped silently
+- Non-eligible scenarios (Quick/Forge/Forge+ tier, non-GitHub source, no `gh` CLI) skipped silently
 - Cached collections (< 7 days old) detected and re-fetch skipped
 - Temporal data fetched via `gh` CLI into staging directory (generic + targeted)
 - Targeted searches performed for up to 10 top_exports function names
@@ -231,7 +231,7 @@ ONLY WHEN temporal context is indexed into QMD (or the step is skipped due to el
 - Halting the workflow due to a `gh` CLI, QMD, or network failure
 - Leaving staging files on disk after indexing (must clean up)
 - Overwriting or modifying extraction data from step-03
-- Displaying skip messages for Quick/Forge tiers (should be silent)
+- Displaying skip messages for Quick/Forge/Forge+ tiers (should be silent)
 - Attempting to fetch temporal data from non-GitHub sources
 - Not registering the collection in forge-tier.yaml after successful indexing
 

package/src/workflows/create-skill/steps-c/step-04-enrich.md

@@ -1,6 +1,6 @@
 ---
 name: 'step-04-enrich'
-description: 'QMD knowledge enrichment for extracted functions — Deep tier only, skip for Quick/Forge'
+description: 'QMD knowledge enrichment for extracted functions — Deep tier only, skip for Quick/Forge/Forge+'
 nextStepFile: './step-05-compile.md'
 ---
 
@@ -8,7 +8,7 @@ nextStepFile: './step-05-compile.md'
 
 ## STEP GOAL:
 
-To enrich the extraction inventory with temporal context from QMD knowledge searches — issues, PRs, changelogs, and migration notes that add T2-confidence annotations to extracted functions. Deep tier only; Quick and Forge tiers skip this step entirely.
+To enrich the extraction inventory with temporal context from QMD knowledge searches — issues, PRs, changelogs, and migration notes that add T2-confidence annotations to extracted functions. Deep tier only; Quick, Forge, and Forge+ tiers skip this step entirely.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -31,7 +31,7 @@ To enrich the extraction inventory with temporal context from QMD knowledge sear
 - 🚫 FORBIDDEN to modify extraction results — enrichment is additive only
 - 🚫 FORBIDDEN to begin compilation — that's step-05
 - 💬 QMD failures degrade gracefully — continue without enrichment
-- ⏱️ Quick and Forge tiers: skip this step entirely, auto-proceed
+- ⏱️ Quick, Forge, and Forge+ tiers: skip this step entirely, auto-proceed
 
 ## EXECUTION PROTOCOLS:
 
@@ -53,7 +53,7 @@ To enrich the extraction inventory with temporal context from QMD knowledge sear
 
 ### 1. Check Tier Eligibility
 
-**If tier is Quick or Forge:**
+**If tier is Quick, Forge, or Forge+:**
 
 Auto-proceed silently. Display no message. Immediately load, read entire file, then execute `{nextStepFile}`.
 
@@ -145,13 +145,13 @@ After enrichment is complete (or skipped for non-Deep tiers), immediately load,
 #### EXECUTION RULES:
 
 - This is an auto-proceed step with no user choices
-- Quick/Forge tiers skip directly to next step with no output
+- Quick/Forge/Forge+ tiers skip directly to next step with no output
 - Deep tier displays brief enrichment summary then auto-proceeds
 - QMD failures do not halt — degrade and proceed
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN enrichment is complete (Deep tier) or the step is skipped (Quick/Forge) will you proceed to load `{nextStepFile}` for SKILL.md compilation.
+ONLY WHEN enrichment is complete (Deep tier) or the step is skipped (Quick/Forge/Forge+) will you proceed to load `{nextStepFile}` for SKILL.md compilation.
 
 ---
 
@@ -159,7 +159,7 @@ ONLY WHEN enrichment is complete (Deep tier) or the step is skipped (Quick/Forge
 
 ### ✅ SUCCESS:
 
-- Quick/Forge tiers: skipped silently with no output, auto-proceeded
+- Quick/Forge/Forge+ tiers: skipped silently with no output, auto-proceeded
 - Deep tier: collection inventory checked before searching
 - Deep tier: no temporal collections → reported and auto-proceeded (not silently skipped)
 - Deep tier: temporal collections exist → QMD searches performed per public API function (10-20, not all exports) with module context derived from extraction inventory source paths
@@ -172,7 +172,7 @@ ONLY WHEN enrichment is complete (Deep tier) or the step is skipped (Quick/Forge
 
 - Halting on QMD unavailability or search failures
 - Modifying T1 extraction results with QMD data
-- Displaying skip messages for Quick/Forge tiers (should be silent)
+- Displaying skip messages for Quick/Forge/Forge+ tiers (should be silent)
 - Pre-emptively skipping all searches without checking the collection inventory
 - Searching all 800+ exports instead of scoping to public API surface (10-20)
 - Using bare function names without module context when source path is available in extraction inventory

package/src/workflows/create-skill/steps-c/step-06-validate.md

@@ -101,7 +101,7 @@ If fails: auto-fix (deterministic), re-validate once, record result. If passes:
 
 **If step 2 reported `body.max_lines` failure:**
 
-**Preferred approach — selective split:** Rather than a full `split-body`, identify which Tier 2 section(s) are largest (usually `## Full API Reference`) and manually extract only those to `references/`. Keep all Tier 1 content and smaller Tier 2 sections inline. This preserves agent accuracy — inline passive context achieves 100% task accuracy vs 79% for on-demand retrieval (per Vercel research). See `knowledge/split-body-strategy.md` for the full rationale.
+**Preferred approach — selective split:** Rather than a full `split-body`, identify which Tier 2 section(s) are largest (usually `## Full API Reference`) and manually extract only those to `references/`. Keep all Tier 1 content and smaller Tier 2 sections inline. This preserves agent accuracy — inline passive context achieves 100% task accuracy vs 79% for on-demand retrieval (per Vercel research). The rationale: inline passive context achieves 100% task accuracy vs 79% for on-demand retrieval (per Vercel research).
 
 **If manual selective split is not feasible**, fall back to the automated full split:
 

package/src/workflows/create-skill/steps-c/step-07-generate-artifacts.md

@@ -183,6 +183,38 @@ Write the updated forge-tier.yaml.
 
 **IF forge tier is NOT Deep:** Skip this section silently. No messaging.
 
+### 5b. CCC Index Registry Registration (Forge+ and Deep with ccc)
+
+**IF `tools.ccc` is true in forge-tier.yaml (Forge+ or Deep with ccc available):**
+
+Ensure the source path used for extraction is indexed by ccc and registered in the `ccc_index_registry` array.
+
+**Index verification:**
+
+Dispatch to ccc CLI (`ccc index {source_root}`) or ccc MCP tool — `ccc_bridge.ensure_index` is a conceptual interface, not a callable function. This is a no-op if the source was already indexed during setup-forge or step-02b.
+
+**Registry update:**
+
+Read `{forgeTierConfig}` and update the `ccc_index_registry` array.
+
+Deduplicate by `source_repo` (the canonical upstream URL from brief_data) combined with `skill_name` — NOT by local `path`, which may be an ephemeral clone path that changes on every run for remote repos. If an entry with matching `source_repo` + `skill_name` already exists, replace it. Otherwise, append:
+
+```yaml
+  - source_repo: "{brief.source_repo}"
+    path: "{source_root}"
+    skill_name: "{name}"
+    indexed_at: "{current ISO date}"
+    source_workflow: "create-skill"
+```
+
+Write the updated forge-tier.yaml.
+
+**Error handling:**
+- If ccc indexing fails: log the error, continue. Do NOT fail the workflow.
+- If forge-tier.yaml update fails: log the error, continue.
+
+**IF `tools.ccc` is false:** Skip this section silently. No messaging.
+
 ### 6. Menu Handling Logic
 
 **Auto-proceed step — no user interaction.**

package/src/workflows/create-skill/steps-c/step-08-report.md

@@ -74,6 +74,7 @@ Where `{primary_confidence}` is the predominant confidence tier (T1 if Forge/Dee
 | T1 (AST) | {t1_count} | Structurally verified via ast-grep |
 | T1-low (Source) | {t1_low_count} | Inferred from source reading |
 | T2 (QMD) | {t2_count} | Enriched with temporal context |
+| T3 (External) | {t3_count} | Sourced from external documentation URLs |
 
 **Output Files:**
 - `skills/{name}/SKILL.md` — Active skill with trigger-based usage

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

@@ -146,7 +146,7 @@ Linear pipeline with tool-delegated heavy lifting. No high-priority subprocess o
 
 - Data flows logically: brief → ecosystem → extraction → enrichment → compilation → validation → generation → report
 - No contradictions between steps
-- Tier-dependent behavior consistent across all 8 steps (Quick/Forge/Deep)
+- Tier-dependent behavior consistent across all 8 steps (Quick/Forge/Forge+/Deep)
 - Error handling consistent: graceful degradation everywhere except file write failures (which correctly halt)
 - Provenance citation format consistent (`[AST:{file}:L{line}]`, `[SRC:{file}:L{line}]`, `[QMD:{collection}:{doc}]`)
 - Overall narrative is a clear compilation pipeline

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

@@ -138,7 +138,7 @@ Compile a skill from a brief — the core compilation engine. Takes a skill-brie
 - Pattern: Linear with conditional branches within steps (tier-dependent)
 - Phases: Load → Check → Extract → Enrich → Compile → Validate → Generate → Report
 - Estimated steps: 8
-- Conditional logic: Steps 03/04 branch internally by forge tier (Quick/Forge/Deep)
+- Conditional logic: Steps 03/04 branch internally by forge tier (Quick/Forge/Forge+/Deep)
 - No branching steps — conditions stay within each step
 
 **User Interaction:**
@@ -225,6 +225,7 @@ create-skill/
 └── steps-c/
     ├── step-01-load-brief.md           (~150 lines, Init with Input Discovery)
     ├── step-02-ecosystem-check.md      (~120 lines, conditional gate)
+    ├── step-02b-ccc-discover.md        (~160 lines, conditional auto-proceed)
     ├── step-03-extract.md              (~200 lines, complex middle)
     ├── step-03b-fetch-temporal.md      (~240 lines, conditional auto-proceed)
     ├── step-03c-fetch-docs.md          (~215 lines, conditional auto-proceed)
@@ -241,6 +242,7 @@ create-skill/
 |------|------|------|-------------|------|
 | 01 | load-brief | Init (Input Discovery) | Auto-proceed (P3) | Load brief, resolve source, load forge tier |
 | 02 | ecosystem-check | Middle (Simple) | Conditional: auto if no match, user choice if match | Check ecosystem |
+| 02b | ccc-discover | Middle (Simple) | Auto-proceed (P3) — Forge+/Deep only | CCC semantic discovery to pre-rank files for extraction |
 | 03 | extract | Middle (Standard) | C only (P2) — Gate 2 | Tier-dependent extraction |
 | 03b | fetch-temporal | Middle (Simple) | Auto-proceed (P3) — Deep only | Fetch temporal context (issues, PRs, changelogs) and index into QMD |
 | 03c | fetch-docs | Middle (Simple) | Auto-proceed (P3) — when doc_urls present | Fetch remote documentation from brief-specified URLs for T3-confidence content |
@@ -257,7 +259,7 @@ create-skill/
 - If --batch: discover all briefs in specified directory
 - Load and validate brief structure (required fields: name, version, source_repo, language, scope)
 - Resolve source code location (local path or GitHub owner/repo)
-- Load forge-tier.yaml from sidecar — determine tier (Quick/Forge/Deep)
+- Load forge-tier.yaml from sidecar — determine tier (Quick/Forge/Forge+/Deep)
 - If forge-tier.yaml missing: halt with "Run [SF] Setup Forge first"
 - Auto-proceed to step-02
 

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

@@ -18,7 +18,7 @@ installed_path: '{project-root}/_bmad/skf/workflows/skillforge/create-skill'
 - **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
 - **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
-- **Tier-Aware Execution**: Steps adapt behavior based on forge tier (Quick/Forge/Deep) loaded from sidecar at init
+- **Tier-Aware Execution**: Steps adapt behavior based on forge tier (Quick/Forge/Forge+/Deep) loaded from sidecar at init
 - **Zero Hallucination**: Every claim requires a provenance citation — uncitable content is excluded, not guessed
 
 ### Step Processing Rules

package/src/workflows/create-stack-skill/data/stack-skill-template.md

@@ -69,7 +69,7 @@ Indexed format targeting ~80-120 tokens per stack:
   "name": "{project}-stack",
   "version": "1.0.0",
   "generation_date": "{ISO-8601}",
-  "confidence_tier": "{Quick|Forge|Deep}",
+  "confidence_tier": "{Quick|Forge|Forge+|Deep}",
   "source_authority": "{official|community|internal}",
   "exports": [],
   "library_count": 0,

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

@@ -67,11 +67,11 @@ STOP — do not proceed.
 **If forge-tier.yaml exists:**
 
 Extract:
-- `forge_tier` — Quick, Forge, or Deep
+- `forge_tier` — Quick, Forge, Forge+, or Deep
 - `available_tools` — list of detected tools (gh_bridge, ast_bridge, qmd_bridge, skill-check)
 - `project_root` — project root path
 
-**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.
 
 ### 2. Validate Available Tools
 
@@ -109,6 +109,7 @@ If no optional inputs provided, auto-detection will be used.
 **Forge Tier:** {tier_description}
 - Quick: Source reading and import counting
 - Forge: + AST-backed structural analysis
+- Forge+: + CCC semantic co-import augmentation
 - Deep: + Temporal integration evolution
 
 **Available Tools:** {tool_list}

package/src/workflows/create-stack-skill/steps-c/step-05-detect-integrations.md

@@ -71,6 +71,16 @@ For each library pair (A, B):
 
 **Threshold:** A pair must have 2+ co-import files to qualify as an integration pattern (single file co-imports may be incidental).
 
+**CCC Semantic Augmentation (Forge+ and Deep with ccc):**
+
+If `tools.ccc` is true AND `ccc_index.status` is `"fresh"` or `"stale"` in forge-tier.yaml, augment co-import detection with semantic search (max 1 query per library pair):
+
+For each library pair that has exactly 1 co-import file (below the 2-file threshold), run `ccc_bridge.search("{libA} {libB}", source_root, top_k=10)` to find files where the two libraries interact semantically — even without explicit import co-location. If CCC returns additional files where both libraries appear, add them to the pair's co-import candidate list and re-evaluate against the 2-file threshold.
+
+For pairs that already qualify (2+ files), CCC is not needed for detection — but the CCC results may surface additional integration files for richer classification in section 3.
+
+CCC failures: skip augmentation silently, proceed with grep-only results.
+
 ### 3. Classify Integration Types
 
 Load `{integrationPatterns}` for classification rules.

package/src/workflows/create-stack-skill/steps-c/step-08-validate.md

@@ -83,7 +83,7 @@ Run: `npx skill-check -h`
 
 This validates frontmatter, description, body limits, links, formatting — and auto-fixes deterministic issues. Parse JSON for `qualityScore`, `diagnostics[]`, `fixed[]`.
 
-**If `body.max_lines` reported**, prefer selective split: extract only the largest Tier 2 section(s) to `references/`, keeping Tier 1 content inline (see `knowledge/split-body-strategy.md`). Fall back to `npx skill-check split-body <skill-dir> --write` if not feasible. Verify `#quick-start` and `#key-types` anchors still resolve after split. Then re-validate.
+**If `body.max_lines` reported**, prefer selective split: extract only the largest Tier 2 section(s) to `references/`, keeping Tier 1 content inline (inline passive context achieves 100% task accuracy vs 79% for on-demand retrieval). Fall back to `npx skill-check split-body <skill-dir> --write` if not feasible. Verify `#quick-start` and `#key-types` anchors still resolve after split. Then re-validate.
 
 **If unavailable**, perform manual frontmatter check:
 - [ ] Frontmatter present with `---` delimiters

package/src/workflows/create-stack-skill/validation-report.md

@@ -309,7 +309,7 @@ The workflow progresses logically from initialization through discovery, confirm
 **Strengths:**
 - Integration layer as primary value — not just concatenated library docs
 - Confidence tier system (T1/T1-low/T2) throughout all outputs
-- Forge-tier dependent extraction (Quick/Forge/Deep)
+- Forge-tier dependent extraction (Quick/Forge/Forge+/Deep)
 - Workspace artifacts (provenance-map.json, evidence-report.md) for traceability
 - Graceful degradation (single library failure doesn't halt; zero integrations is valid)
 

package/src/workflows/create-stack-skill/workflow-plan-create-stack-skill.md

@@ -111,7 +111,7 @@ Multi-file document-producing workflow:
 ### Address (gaps identified from memory)
 
 - `manifest_reader` does not exist — needs self-contained dependency detection with fallback chain (npm/PyPI/crates.io/Cargo registry APIs → file parsing → web search)
-- No forge-tier awareness — must implement Quick/Forge/Deep tier behavior matching create-skill, quick-skill, test-skill, export-skill patterns
+- No forge-tier awareness — must implement Quick/Forge/Forge+/Deep tier behavior matching create-skill, quick-skill, test-skill, export-skill patterns
 - No tool bridge specifications — needs gh_bridge (all tiers), ast_bridge (Forge/Deep), qmd_bridge (Deep only)
 - No error handling matrix — needs hard halt / graceful degradation / silent skip / advisory categories
 - "Absorbs analyze-stack internally" undefined — must define concrete analyze-stack functionality within steps 01-05
@@ -273,7 +273,7 @@ create-stack-skill/
 
 **Step 01 (init):**
 - Load SKF module config from `_bmad/skf/config.yaml`
-- Load forge-tier.yaml from sidecar: determine Quick/Forge/Deep tier and available tools
+- Load forge-tier.yaml from sidecar: determine Quick/Forge/Forge+/Deep tier and available tools
 - Validate prerequisites: forge-tier.yaml exists, project root accessible
 - Accept optional explicit dependency list (skip auto-detection if provided)
 - Accept optional scope overrides per library

package/src/workflows/create-stack-skill/workflow.md

@@ -2,7 +2,7 @@
 name: create-stack-skill
 description: Consolidated project stack skill with integration patterns
 web_bundle: true
-installed_path: '{project-root}/_bmad/skf/workflows/create-stack-skill'
+installed_path: '{project-root}/_bmad/skf/workflows/skillforge/create-stack-skill'
 ---
 
 # Create Stack Skill

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

@@ -103,7 +103,7 @@ Extract from `metadata.json`:
 - `source_authority` — `official`, `internal`, or `community`
 - `exports` — Array of exported functions/types
 - `generation_date` — When the skill was last generated
-- `confidence_tier` — Quick/Forge/Deep
+- `confidence_tier` — Quick/Forge/Forge+/Deep
 
 **For stack skills, also extract:**
 - `components` — Array of dependencies with versions

package/src/workflows/export-skill/steps-c/step-02-package.md

@@ -75,7 +75,7 @@ Verify the skill directory contains the expected agentskills.io package layout:
    - `source_authority` ("official", "internal", or "community")
    - `exports` (array)
    - `generation_date` (ISO date string)
-   - `confidence_tier` ("Quick", "Forge", or "Deep")
+   - `confidence_tier` ("Quick", "Forge", "Forge+", or "Deep")
 3. `references/` — If exists, check at least one .md file present
 4. `scripts/` — If exists, verify at least one file present and each file referenced in SKILL.md Section 7b exists. Warn for orphaned scripts (present but not referenced).
 5. `assets/` — If exists, verify at least one file present and each file referenced in SKILL.md Section 7b exists. Warn for orphaned assets (present but not referenced).

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

@@ -174,7 +174,7 @@ Three CLAUDE.md cases:
 **Output Specifications:**
 - Type: Action-based (file writes + console output)
 - Files written:
-  1. `{skills_output_folder}/{name}/context-snippet.md` — ADR-L v2 format (~50-80 tokens/skill)
+  1. `{skills_output_folder}/{name}/context-snippet.md` — ADR-L v2 format (~80-120 tokens/skill)
   2. CLAUDE.md or AGENTS.md — managed `<!-- SKF:BEGIN/END -->` section per ADR-J (3 cases: create/append/regenerate)
   3. agentskills.io package structure — ready for `npx skills publish`
 - Console output: Token count report + export summary with distribution instructions

package/src/workflows/quick-skill/data/skill-template.md

@@ -73,7 +73,15 @@ Indexed format targeting ~80-120 tokens per skill:
   "generated_by": "quick-skill",
   "generation_date": "{date}",
   "confidence_tier": "Quick",
+  "extraction_tier": "quick",
+  "spec_version": "1.3",
   "exports": ["{export_1}", "{export_2}"],
+  "confidence_distribution": {
+    "t1": 0,
+    "t1_low": "{exports_count}",
+    "t2": 0,
+    "t3": 0
+  },
   "stats": {
     "exports_documented": "{number}",
     "exports_public_api": "{number}",

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

@@ -71,9 +71,7 @@ Search for an existing official skill matching `{repo_name}` in the agentskills.
 
 **If no match found:**
 - Set `ecosystem_status: no-match`
-- Auto-proceed to step 3:
-
-"**No existing official skill found for {repo_name}. Proceeding to extraction...**"
+- Auto-proceed silently to step 3. Do not display any message — absence of a match is the expected case.
 
 **If match found:**
 - Set `ecosystem_status: match`

package/src/workflows/setup-forge/data/tier-rules.md

@@ -7,16 +7,20 @@
 | ast-grep | `ast-grep --version` | Returns version string without error |
 | gh | `gh --version` | Returns version string without error |
 | qmd | `qmd status` | Returns status indicating initialized and operational |
+| ccc | Step A: `ccc --help` Step B: `ccc doctor` | Step A: exits 0 (binary exists). Step B: daemon running, version string, model check OK |
 
-**Important:** Use verification commands, not existence checks (`which`, `command -v`). A tool must be functional, not just present on PATH.
+**Important:** Use verification commands, not existence checks (`which`, `command -v`). A tool must be functional, not just present on PATH. For daemon-based tools (ccc), verify both binary existence and daemon health.
 
 ## Tier Calculation
 
-| Tier | Required Tools | Rule |
-|------|---------------|------|
-| Quick | None | Default when no tools are available |
-| Forge | ast-grep | ast-grep available, regardless of gh/qmd |
-| Deep | ast-grep + gh + qmd | All three tools available and functional |
+| Priority | Tier | Required Tools | Rule |
+|----------|------|---------------|------|
+| 1 (highest) | Deep | ast-grep + gh + qmd | All three core tools available and functional |
+| 2 | Forge+ | ast-grep + ccc | ast-grep AND ccc available, regardless of gh/qmd |
+| 3 | Forge | ast-grep | ast-grep available, without ccc/gh/qmd |
+| 4 (default) | Quick | None | Default when no tools are available |
+
+**Evaluation order:** Check Deep first, then Forge+, then Forge. The first match wins. This ensures Deep always takes priority when all tools are present.
 
 **Override:** If `tier_override` is set in preferences.yaml, use that value instead of calculated tier.
 
@@ -24,6 +28,9 @@
 - gh available but no ast-grep → Quick (gh alone doesn't unlock Forge)
 - ast-grep + gh but no qmd → Forge (qmd required for Deep)
 - ast-grep + qmd but no gh → Forge (gh required for Deep)
+- ccc available but no ast-grep → Quick (ccc alone doesn't unlock Forge+)
+- ast-grep + ccc + gh but no qmd → Forge+ (qmd required for Deep)
+- ast-grep + gh + qmd + ccc → Deep (Deep subsumes Forge+; ccc enhances transparently)
 
 ## Tier Capability Descriptions
 
@@ -35,6 +42,9 @@ Use these for positive-framing in the report step. Describe what the tier GIVES,
 ### Forge Tier
 "Forge tier active. You have AST-backed structural code analysis with line-level citations, plus template-driven generation. Every skill instruction traces to verified source code."
 
+### Forge+ Tier
+"Forge+ tier active. Semantic-guided precision compilation — cocoindex-code maps the codebase semantically before AST extraction runs. Every skill begins with a ranked discovery pass that surfaces the most relevant source regions, then AST-backed verification gives each export its line-level citation."
+
 ### Deep Tier
 "Deep tier active. Full capability unlocked — AST-backed code analysis, GitHub repository exploration, and QMD knowledge search with cross-repository synthesis. Maximum provenance and intelligence."