bmad-module-skill-forge 0.5.0 → 0.6.0

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

@@ -103,7 +103,7 @@ Perform tier-aware extraction on only the changed files identified in step 02, p
 DO NOT BE LAZY — For EACH file in the change manifest with status MODIFIED, ADDED, or RENAMED, launch a subprocess that:
 
 1. Loads the source file
-2. Performs tier-appropriate extraction (Quick/Forge/Deep)
+2. Performs tier-appropriate extraction (Quick/Forge/Forge+/Deep)
 3. For each export found:
    - Record: export name, type (function/class/type/constant), signature
    - Record: file path, start line, end line
@@ -119,6 +119,23 @@ DO NOT BE LAZY — For EACH file in the change manifest with status MODIFIED, AD
 
 **Re-export tracing (Forge/Deep only):** After extracting changed files, check if any public exports from the package entry point (`__init__.py`, `index.ts`, `lib.rs`) are unresolved — particularly when a changed file is part of a module re-export chain. Follow the **Re-Export Tracing** protocol in `{extractionPatternsData}` to trace unresolved symbols to their actual definition files.
 
+### 2b. CCC Semantic Ranking (Forge+ and Deep with ccc)
+
+**IF `tools.ccc` is true in forge-tier.yaml:**
+
+Before aggregating extraction results, use CCC to assess semantic significance of changes:
+
+1. Run `ccc_bridge.search("{skill_name}", source_root, top_k=15)` to get the skill's most semantically central files
+2. Cross-reference the change manifest files with CCC results
+3. Files appearing in BOTH the change manifest AND CCC's top results are **semantically significant changes** — flag them for priority in the merge step
+4. Store `{ccc_significant_changes: [{file, score}]}` in context
+
+This helps the merge step (section 4) prioritize which changes are most likely to affect the skill's core content vs. peripheral modifications.
+
+CCC failures: skip ranking silently, all changes treated equally.
+
+**IF `tools.ccc` is false:** Skip this section silently.
+
 ### 3. Deep Tier QMD Enrichment (Conditional)
 
 **ONLY if forge_tier == Deep:**
@@ -200,7 +217,7 @@ ONLY WHEN all changed files have been extracted and results compiled will you lo
 - Every changed file from manifest extracted with tier-appropriate method
 - All exports labeled with confidence tier (T1/T1-low/T2)
 - AST file:line citations on every extracted export
-- QMD enrichment performed for Deep tier (skipped with notice for Quick/Forge)
+- QMD enrichment performed for Deep tier (skipped with notice for Quick/Forge/Forge+)
 - Extraction results compiled with per-file detail
 - Summary displayed before auto-proceeding
 - No unchanged files extracted

package/src/workflows/update-skill/steps-c/step-05-validate.md

@@ -73,7 +73,7 @@ Launch subprocesses in parallel for each validation category, aggregating result
 
 **If available**, run: `npx skill-check check <skill-dir> --fix --format json --no-security-scan`
 
-Parse JSON output for quality score (0-100), auto-fixed issues, and remaining diagnostics. If `body.max_lines` reported, prefer selective split: extract only the largest Tier 2 section(s) to `references/`, keeping all Tier 1 content inline (see `knowledge/split-body-strategy.md`). Fall back to `npx skill-check split-body <skill-dir> --write` only if selective split is not feasible. After any split, verify `#quick-start` and `#key-types` anchors still resolve in SKILL.md.
+Parse JSON output for quality score (0-100), auto-fixed issues, and remaining diagnostics. If `body.max_lines` reported, prefer selective split: extract only the largest Tier 2 section(s) to `references/`, keeping all Tier 1 content inline (selective split preserves agent accuracy — inline passive context achieves 100% task accuracy vs 79% for on-demand retrieval per Vercel research). Fall back to `npx skill-check split-body <skill-dir> --write` only if selective split is not feasible. After any split, verify `#quick-start` and `#key-types` anchors still resolve in SKILL.md.
 
 **If unavailable**, perform manual check: validate merged SKILL.md structure, verify required sections (exports, usage patterns, conventions), verify export entries have name/type/signature/file:line reference, flag missing sections.
 

package/src/workflows/update-skill/steps-c/step-06-write.md

@@ -115,7 +115,7 @@ Write to `{forge_data_folder}/{skill_name}/provenance-map.json`:
 
 ### 4. Write Updated evidence-report.md
 
-Append update operation section to `{forge_data_folder}/{skill_name}/evidence-report.md`:
+Append update operation section to `{forge_data_folder}/{skill_name}/evidence-report.md` (create the file with a standard header if it does not yet exist):
 
 ```markdown
 ## Update Operation — {current_date}
@@ -182,7 +182,7 @@ External tool checks deferred from step-05 now run against the written files:
 
 **If skill-check available:**
 - Run: `npx skill-check check {skills_output_folder}/{skill_name} --fix --format json --no-security-scan`
-- If `body.max_lines` reported, prefer selective split (see `knowledge/split-body-strategy.md`). Fall back to `npx skill-check split-body {skills_output_folder}/{skill_name} --write` if not feasible. Verify anchors resolve after split.
+- If `body.max_lines` reported, prefer selective split — extract only the largest Tier 2 section(s) to `references/`, keeping Tier 1 inline (inline passive context achieves 100% task accuracy vs 79% for on-demand retrieval). Fall back to `npx skill-check split-body {skills_output_folder}/{skill_name} --write` if not feasible. Verify anchors resolve after split.
 - Run: `npx skill-check diff` if original version was preserved
 - Run: `npx skill-check check {skills_output_folder}/{skill_name} --format json` for security scan
 

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

@@ -413,7 +413,7 @@ This workflow is a well-architected surgical pipeline that achieves its goal of
 
 1. **Zero-hallucination principle** enforced throughout — every statement must trace to actual artifacts
 2. **[MANUAL] section preservation** treated as highest priority with multiple safeguards (inventory in step-01, preservation in step-04, integrity verification in step-05, write verification in step-06)
-3. **Tier-aware extraction** well-implemented across Quick/Forge/Deep with graceful degradation
+3. **Tier-aware extraction** well-implemented across Quick/Forge/Forge+/Deep with graceful degradation
 4. **Subprocess optimization** strategically placed at the right steps (02-parallel, 03-per-file, 03-QMD, 05-parallel)
 5. **Error handling** is comprehensive (missing artifacts → abort with helpful message, missing provenance → degraded mode, [MANUAL] conflicts → user resolution)
 6. **Workflow chaining** properly integrated with input/output contracts

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

@@ -125,7 +125,7 @@ Document-producing workflow that outputs:
 
 ### Missing Features to Add During Conversion
 
-1. Tier-aware re-extraction (Quick/Forge/Deep graceful degradation)
+1. Tier-aware re-extraction (Quick/Forge/Forge+/Deep graceful degradation)
 2. Degraded mode for missing provenance map (fallback to full re-extraction)
 3. Stack skill multi-file update support
 4. Batch mode with checkpoint resume

package/tools/cli/commands/status.js

@@ -146,7 +146,7 @@ function displayStatus(status, version) {
   const tools = ft.tools || {};
   console.log(chalk.white.bold('  Forge Tier'));
   if (status.tierDetected) {
-    const tierColors = { Quick: chalk.yellow, Forge: chalk.hex('#F59E0B'), Deep: chalk.hex('#FCD34D') };
+    const tierColors = { Quick: chalk.yellow, Forge: chalk.hex('#F59E0B'), 'Forge+': chalk.hex('#E88D0E'), Deep: chalk.hex('#FCD34D') };
     const tierColor = tierColors[ft.tier] || chalk.white;
     console.log(`    Tier:         ${tierColor(ft.tier)}`);
     console.log(`    Detected:     ${chalk.dim(ft.tier_detected_at || '(unknown)')}`);
@@ -155,6 +155,7 @@ function displayStatus(status, version) {
   }
   console.log(`    ast-grep:     ${formatTool(tools.ast_grep)}`);
   console.log(`    gh CLI:       ${formatTool(tools.gh_cli)}`);
+  console.log(`    ccc:          ${formatTool(tools.ccc)}`);
   console.log(`    QMD:          ${formatTool(tools.qmd)}`);
   console.log('');