bmad-module-skill-forge 0.10.0 → 0.10.1-alpha.0

package/src/README.md

@@ -8,40 +8,38 @@ For user-facing documentation (what SKF does, how to install it, how to use it),
 
 ```
 src/
-├── module.yaml           # Module config: code, name, install prompts
-├── module-help.csv       # Help registry — one row per agent command
-├── agents/
-│   └── forger.agent.yaml # Ferris — the single agent persona
-├── workflows/            # 14 workflows (see workflows/README.md)
-│   ├── setup-forge/
-│   ├── analyze-source/
-│   ├── brief-skill/
-│   ├── create-skill/
-│   ├── quick-skill/
-│   ├── create-stack-skill/
-│   ├── verify-stack/
-│   ├── refine-architecture/
-│   ├── update-skill/
-│   ├── audit-skill/
-│   ├── test-skill/
-│   ├── export-skill/
-│   ├── rename-skill/
-│   └── drop-skill/
-├── knowledge/            # Cross-cutting knowledge fragments (JiT loaded)
+├── skf-forger/               # Agent skill — Ferris persona
+│   ├── SKILL.md              # Agent identity, principles, menu of triggers
+│   └── bmad-skill-manifest.yaml
+├── skf-setup/                # Setup skill (forge initialization)
+│   ├── SKILL.md
+│   └── ...
+├── skf-{name}/               # 13 workflow skills (one directory each)
+│   ├── SKILL.md              # Skill entry point (overview, stages, invocation contract)
+│   ├── steps-c/              # Sequential step files
+│   ├── references/           # Rules, patterns, protocols (decision-making)
+│   ├── assets/               # Schemas, output formats
+│   └── templates/            # Output skeletons (used by some skills)
+├── knowledge/                # Cross-cutting knowledge fragments (JiT loaded)
 │   └── skf-knowledge-index.csv
-└── forger/               # Sidecar seed files (preferences, forge tier)
+├── forger/                   # Sidecar seed files (preferences, forge tier)
+├── shared/                   # Cross-workflow resources
+├── module.yaml               # Module metadata (code, name, config vars)
+└── module-help.csv           # Skill menu for bmad-help integration
 ```
 
+**Workflow skills:** setup, analyze-source, brief-skill, create-skill, quick-skill, create-stack-skill, verify-stack, refine-architecture, update-skill, audit-skill, test-skill, export-skill, rename-skill, drop-skill.
+
 ## Components
 
-- **Agent:** [Ferris](agents/forger.agent.yaml) — single-persona module operating in four modes (Architect / Surgeon / Audit / Delivery)
-- **Workflows:** see [workflows/README.md](workflows/README.md) for the full index, typical flows, and the knowledge-vs-data distinction
+- **Agent:** [Ferris](skf-forger/SKILL.md) — single-persona module operating in five modes (Architect / Surgeon / Audit / Delivery / Management)
+- **Workflow skills:** 14 `skf-{name}/` directories, each containing a SKILL.md, steps, references, and assets
 - **Knowledge fragments:** cross-cutting principles Ferris consults via `knowledge/skf-knowledge-index.csv`
 
 ## Editing this module
 
-- Agent edits — `agents/forger.agent.yaml`; validate with `bmad:bmb:agents:agent-validate`
-- Workflow edits — each workflow in `workflows/{name}/`; validate with `bmad:bmb:workflows:workflow-validate`
+- Agent edits — `skf-forger/SKILL.md`; validate with `bmad:bmb:agents:agent-validate`
+- Workflow edits — each workflow skill in `skf-{name}/`; validate with `bmad:bmb:workflows:workflow-validate`
 - Module-level edits — `module.yaml` and `module-help.csv`; validate with `bmad:bmb:modules:validate-module`
 
 See [CONTRIBUTING.md](../CONTRIBUTING.md) for the contribution workflow.

package/src/forger/forge-tier.yaml

@@ -1,5 +1,5 @@
 # Ferris Sidecar: Forge Tier State
-# Written by setup-forge workflow on first run
+# Written by setup workflow on first run
 
 # Tool availability (detected during [SF] Setup Forge)
 tools:
@@ -15,12 +15,14 @@ tools:
 tier: ~
 tier_detected_at: ~
 
-# CCC semantic index state (managed by setup-forge and extraction workflows)
+# CCC semantic index state (managed by setup and extraction workflows)
 ccc_index:
   indexed_path: ~
   last_indexed: ~
   status: "none"
   staleness_threshold_hours: 24
+  file_count: ~
+  exclude_patterns: []
 
 # CCC index registry (tracks which source paths have been indexed for skill workflows)
 ccc_index_registry: []

package/src/forger/preferences.yaml

@@ -1,5 +1,5 @@
 # Ferris Sidecar: User Preferences
-# Created by setup-forge workflow on first run
+# Created by setup workflow on first run
 # Edit this file to customize Ferris behavior
 
 # Override detected tier (set to Quick, Forge, Forge+, or Deep to force a tier)
@@ -8,6 +8,12 @@ tier_override: ~
 # Passive context injection (set to false to skip snippet generation and CLAUDE.md updates during export)
 passive_context: true
 
+# Headless mode (set to true to skip confirmation gates in all workflows)
+headless_mode: false
+
+# Compact greeting (set to true to skip the full capabilities table on session start)
+compact_greeting: false
+
 # Reserved for future use — these fields are not yet consumed by any workflow step
 # output_language: ~
 # skill_format_version: ~

package/src/knowledge/agentskills-spec.md

@@ -40,7 +40,7 @@ description: >
 - `description`: 1-1024 characters, trigger-optimized for agent matching
   - **MUST use third-person voice.** The description is injected into the system prompt; inconsistent point-of-view causes discovery problems. Write "Processes Excel files and generates reports" — never "I can help you process Excel files" or "You can use this to process Excel files."
 
-**Body:** Free-form markdown — no structural restrictions, but Skill Forge follows a consistent section order (see skill-sections.md in create-skill/data/).
+**Body:** Free-form markdown — no structural restrictions, but Skill Forge follows a consistent section order (see skill-sections.md in create-skill/assets/).
 
 ### Optional: Supporting Directories
 

package/src/knowledge/architecture-verification.md

@@ -99,4 +99,4 @@ VS and RA are pre-code workflows. SS compose-mode synthesizes the implementation
 - [skill-lifecycle.md](skill-lifecycle.md) — end-to-end pipeline and workflow connections
 - [progressive-capability.md](progressive-capability.md) — tier philosophy for skill generation
 
-_Source: synthesized from verify-stack/workflow.md, refine-architecture/workflow.md, and create-stack-skill compose-mode-rules.md_
+_Source: synthesized from skf-verify-stack/SKILL.md, skf-refine-architecture/SKILL.md, and skf-create-stack-skill/references/compose-mode-rules.md_

package/src/knowledge/ccc-bridge.md

@@ -24,7 +24,7 @@ ccc is **required** at the Forge+ tier (it defines Forge+) and **optionally avai
 ## Availability
 
 ccc_bridge operations are available when:
-- `tools.ccc: true` in forge-tier.yaml (verified by `ccc --help` + `ccc doctor` in setup-forge)
+- `tools.ccc: true` in forge-tier.yaml (verified by `ccc --help` + `ccc doctor` in setup)
 - `ccc_index.status` is `"fresh"` or `"stale"` in forge-tier.yaml (an index exists for the project)
 
 When either condition is false, calling steps skip ccc discovery silently and proceed with direct ast-grep or source reading. This is standard Forge tier behavior — not a degradation.
@@ -43,7 +43,7 @@ Returns: list of `{file, score, snippet}` entries ranked by semantic relevance t
 
 **Resolves to:** Check `ccc_index.status` in forge-tier.yaml. If `"none"` or the indexed_path does not match, run `cd {path} && ccc init` then `ccc index` and update forge-tier.yaml. Note: `ccc init` takes no positional arguments — it initializes the index for the current working directory.
 
-**Usage context:** Called by setup-forge step-01b to ensure the project root is indexed. Called lazily by extraction steps when `ccc_index.status` is `"none"` but ccc is available.
+**Usage context:** Called by setup step-01b to ensure the project root is indexed. Called lazily by extraction steps when `ccc_index.status` is `"none"` but ccc is available.
 
 ### `ccc_bridge.status()`
 
@@ -51,7 +51,7 @@ Returns: list of `{file, score, snippet}` entries ranked by semantic relevance t
 1. `ccc --help` — confirms binary exists (exit 0)
 2. `ccc doctor` — confirms daemon is running, extracts version string, validates embedding model
 
-**Usage context:** Called exclusively by setup-forge step-01 during tool detection. Downstream workflows read the result from forge-tier.yaml — they do not re-verify.
+**Usage context:** Called exclusively by setup step-01 during tool detection. Downstream workflows read the result from forge-tier.yaml — they do not re-verify.
 
 ## Confidence
 
@@ -67,7 +67,7 @@ The ccc search is invisible in the output artifact. A Forge+ skill's citations a
 
 ### When Indexing Happens
 
-1. **setup-forge step-01b:** Indexes the project root when setup-forge runs. This is the primary indexing point.
+1. **setup step-01b:** Indexes the project root when setup runs. This is the primary indexing point.
 2. **Workflow discovery steps:** If `ccc_index.status` is `"stale"` or `"none"`, discovery steps trigger a re-index and warn the user. They do not block.
 3. **ccc daemon:** Incremental indexing means re-indexing unchanged files is a near-no-op.
 
@@ -75,13 +75,13 @@ The ccc search is invisible in the output artifact. A Forge+ skill's citations a
 
 - Staleness threshold: 24 hours (configurable via `ccc_index.staleness_threshold_hours` in forge-tier.yaml)
 - A stale index still produces useful results — the workflow proceeds with the stale index and notes the staleness
-- setup-forge is the designated refresh authority
+- setup is the designated refresh authority
 
 ### Exclusion Patterns
 
 CCC stores its configuration at `{project-root}/.cocoindex_code/settings.yml`. This file contains `exclude_patterns` and `include_patterns` arrays in glob format. `ccc init` creates the file with sensible defaults (excludes `node_modules`, `__pycache__`, hidden dirs, etc.).
 
-**SKF infrastructure exclusions:** setup-forge step-01b appends SKF-specific exclusion patterns after `ccc init` creates the default config. These patterns prevent indexing of framework and output directories that have zero value for source extraction:
+**SKF infrastructure exclusions:** setup step-01b appends SKF-specific exclusion patterns after `ccc init` creates the default config. These patterns prevent indexing of framework and output directories that have zero value for source extraction:
 
 | Pattern | Purpose |
 |---------|---------|
@@ -92,20 +92,21 @@ CCC stores its configuration at `{project-root}/.cocoindex_code/settings.yml`. T
 | `**/{skills_output_folder}` | Generated skill files (from manifest, default: `skills`) |
 | `**/{forge_data_folder}` | Compilation workspace (from manifest, default: `forge-data`) |
 
-The `skills_output_folder` and `forge_data_folder` values are read from `_bmad/_config/skf-manifest.yaml` when available, falling back to the defaults `skills` and `forge-data`. Patterns are appended only if not already present — user customizations to `settings.yml` are preserved.
+The `skills_output_folder` and `forge_data_folder` values are resolved from the workflow activation context (sourced from `_bmad/skf/config.yaml`), falling back to the defaults `skills` and `forge-data`. Patterns are appended only if not already present — user customizations to `settings.yml` are preserved.
 
 The configured exclusion patterns are stored in `ccc_index.exclude_patterns` in forge-tier.yaml for reference.
 
 ### Deferred Discovery (Remote Sources)
 
-For remote repository sources (GitHub URLs), CCC cannot operate during step-02b because no local code exists yet. The ephemeral clone happens in step-03. To provide CCC pre-ranking for remote sources:
+For remote repository sources (GitHub URLs), CCC cannot operate during step-02b because no local code exists yet. The workspace clone or ephemeral clone happens in step-03. To provide CCC pre-ranking for remote sources:
 
 1. **step-02b:** Detects remote source, sets `{ccc_discovery: []}`, displays deferred message
-2. **step-03:** After ephemeral clone succeeds, detects the deferred scenario (`tools.ccc == true AND {ccc_discovery} is empty AND ephemeral_clone_active == true AND tier is Forge+/Deep`)
-3. **step-03:** Runs `cd {temp_path} && ccc init` on the ephemeral clone, then applies brief `exclude_patterns` (if present) to `{temp_path}/.cocoindex_code/settings.yml` before running `ccc index` (extended timeout or background mode, verified via `ccc status`). This prevents CCC from indexing files the brief explicitly excludes, keeping search results focused on in-scope source code and reducing indexing time for large repositories.
-4. **step-03:** Executes CCC search and populates `{ccc_discovery}` before AST extraction begins
+2. **step-03:** After source resolution succeeds, detects the deferred scenario (`tools.ccc == true AND {ccc_discovery} is empty AND remote_clone_path is set AND tier is Forge+/Deep`)
+3. **step-03 (workspace fast path):** If `{remote_clone_path}/.cocoindex_code/` already exists (persisted workspace index), skips init/index and uses `ccc search --refresh` — CCC daemon re-indexes only if files changed since last index. This is near-instant for unchanged repos.
+4. **step-03 (first-time path):** If no existing CCC index, runs `cd {remote_clone_path} && ccc init`, applies standard build/dependency exclusions (node_modules, dist, .git, vendor, etc.) to `settings.yml`, then runs `ccc index`. Brief-specific `include_patterns`/`exclude_patterns` are NOT written to `settings.yml` — the CCC index is general-purpose. Filtering happens at search result time.
+5. **step-03:** Executes CCC search and populates `{ccc_discovery}` before AST extraction begins
 
-The ephemeral clone index is not registered in `ccc_index_registry` — the clone is deleted after extraction and the CCC daemon's own GC handles orphaned indexes.
+For workspace repos, the CCC index persists at `{workspace_repo_path}/.cocoindex_code/` and is reused across forges, projects, and sessions. For ephemeral fallback clones, the index is not registered in `ccc_index_registry` — the clone is deleted after extraction.
 
 ### Relationship to QMD Registry
 
@@ -113,7 +114,7 @@ ccc_index and qmd_collections are **orthogonal**:
 - `ccc_index` in forge-tier.yaml tracks the persistent source code index (one per project)
 - `qmd_collections[]` in forge-tier.yaml tracks per-skill workflow artifact collections
 - ccc indexes source code for semantic search; QMD indexes curated artifacts for temporal/knowledge search
-- The janitor role for QMD (setup-forge step-03) operates independently of ccc_index
+- The janitor role for QMD (setup step-03) operates independently of ccc_index
 
 ## Query Volume Bounds
 
@@ -130,8 +131,8 @@ To prevent excessive daemon calls, workflow steps cap ccc queries:
 - Running ccc_bridge.ensure_index() without checking ccc_index.status first — unnecessary re-indexing
 - Passing ccc results directly to the extraction inventory — they are candidates, not extractions
 - Listing ccc as "unavailable" in reports for Quick/Forge tiers — ccc is a Forge+ capability, not something Quick/Forge tiers are missing
-- Indexing without configuring SKF exclusions — framework and output directories pollute search results
-- Indexing an ephemeral clone without applying brief `exclude_patterns` — excluded files pollute CCC search results and waste indexing time on large repositories
+- Indexing without configuring exclusions — for project root indexes, apply SKF exclusions (framework/output directories); for workspace repo indexes, apply standard build artifact exclusions (node_modules, dist, .git, etc.)
+- Writing brief-specific `exclude_patterns` to a workspace repo's `settings.yml` — workspace indexes are general-purpose and serve multiple briefs. Apply brief patterns at search result time, not index time. (Exception: ephemeral fallback clones are single-use, so brief exclusions may be applied to their `settings.yml` to reduce indexing time.)
 - Skipping CCC discovery for remote sources without deferring to step-03 — remote repos deserve the same pre-ranking as local sources
 
 ## Related Fragments

package/src/knowledge/overview.md

@@ -2,11 +2,11 @@
 
 ## Principle
 
-Agent-level knowledge files capture cross-cutting principles and patterns that Ferris applies across multiple workflows. They are distinct from workflow `data/` files, which contain step-specific operational artifacts. Knowledge is loaded just-in-time when a workflow step directs — never preloaded into context.
+Agent-level knowledge files capture cross-cutting principles and patterns that Ferris applies across multiple workflows. They are distinct from workflow `references/` and `assets/` files, which contain step-specific operational artifacts. Knowledge is loaded just-in-time when a workflow step directs — never preloaded into context.
 
 ## Rationale
 
-The SKF module has 12 workflows containing numerous operational `data/` files embedded in step directories. These data files define schemas, templates, scoring formulas, and extraction rules tightly coupled to individual steps. But several principles — zero hallucination, confidence tiers, provenance — cut across multiple workflows and need a single authoritative source rather than fragmented repetition.
+The SKF module has 14 workflows containing operational `references/` and `assets/` files within each skill directory. References contain rules, patterns, and protocols for decision-making; assets contain templates, schemas, and output formats. Both are tightly coupled to individual steps. But several principles — zero hallucination, confidence tiers, provenance — cut across multiple workflows and need a single authoritative source rather than fragmented repetition.
 
 Without a knowledge folder:
 - Cross-cutting principles get duplicated across workflow steps
@@ -26,7 +26,7 @@ With knowledge files:
 | [confidence-tiers.md](confidence-tiers.md)                 | T1/T1-low/T2/T3 trust model and citation formats                  | AN, BS, CS, QS, SS, US, AS, TS, EX, RA, VS |
 | [progressive-capability.md](progressive-capability.md)     | Quick/Forge/Forge+/Deep tier philosophy and behavior adaptation          | SF, AN, BS, CS, QS, SS, US, AS, TS, EX, VS, RA |
 | [agentskills-spec.md](agentskills-spec.md)                 | agentskills.io output format principles and compliance            | CS, QS, SS, US, TS, EX             |
-| [skill-lifecycle.md](skill-lifecycle.md)                   | End-to-end pipeline, artifact flow, workflow selection            | All 12                             |
+| [skill-lifecycle.md](skill-lifecycle.md)                   | End-to-end pipeline — workflow connections, artifact flow, decision rules for workflow selection, pipeline invocation syntax and aliases | All 14                             |
 | [provenance-tracking.md](provenance-tracking.md)           | Provenance-map.json entries and file_entries, evidence reports, claim traceability | CS, QS, SS, US, AS, TS             |
 | [manual-section-integrity.md](manual-section-integrity.md) | \[MANUAL\] marker preservation and merge algorithm                | CS, US, AS, TS, EX                 |
 | [qmd-registry.md](qmd-registry.md)                         | Progressive QMD collection registry and collection gate principle | SF, BS, CS, US, AS                 |
@@ -43,17 +43,17 @@ With knowledge files:
 1. Ferris receives a task or workflow activation
 2. Consult `skf-knowledge-index.csv` to identify relevant knowledge fragments by tags or description. The `tier` column classifies fragments as `core` (always relevant when the domain applies) or `extended` (load only when the specific scenario is active — e.g., `doc-fetcher.md` only when `doc_urls` are present in the brief)
 3. Load only the files needed for the current task — never bulk-load all knowledge
-4. Apply knowledge principles during workflow execution alongside step-specific `data/` files
+4. Apply knowledge principles during workflow execution alongside step-specific `references/` and `assets/` files
 
 ## Knowledge vs. Data
 
-| Aspect    | Knowledge Files (`knowledge/`)       | Data Files (`data/`)                    |
-|-----------|--------------------------------------|-----------------------------------------|
-| Scope     | Cross-cutting, multi-workflow        | Single workflow, single step            |
-| Content   | Principles, patterns, judgment rules | Schemas, templates, scoring formulas    |
-| Loading   | JiT via index lookup                 | JiT via step instruction                |
-| Examples  | Zero hallucination, confidence tiers | skill-brief-schema.md, scoring-rules.md |
-| Stability | Rarely changes                       | Changes with workflow evolution         |
+| Aspect    | Knowledge Files (`knowledge/`)       | References (`references/`)              | Assets (`assets/`)                      |
+|-----------|--------------------------------------|-----------------------------------------|-----------------------------------------|
+| Scope     | Cross-cutting, multi-workflow        | Single workflow, single step            | Single workflow, single step            |
+| Content   | Principles, patterns, judgment rules | Rules, patterns, protocols, heuristics  | Templates, schemas, output formats      |
+| Loading   | JiT via index lookup                 | JiT via step instruction                | JiT via step instruction                |
+| Examples  | Zero hallucination, confidence tiers | scoring-rules.md, extraction-patterns.md | skill-brief-schema.md, skill-template.md |
+| Stability | Rarely changes                       | Changes with workflow evolution         | Changes with workflow evolution         |
 
 ## Related Fragments
 

package/src/knowledge/progressive-capability.md

@@ -31,7 +31,7 @@ With progressive capability:
 
 ### Example 1: Tool Detection and Tier Assignment
 
-**Context:** The setup-forge workflow detects available tools and assigns a tier.
+**Context:** The setup workflow detects available tools and assigns a tier.
 
 **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:
 
@@ -125,7 +125,7 @@ When source is remote (GitHub URL) and tier is Forge, Forge+, or Deep:
 ## Anti-Patterns
 
 - Describing Quick tier as "basic" or "limited" — it is fast and legitimate
-- Requiring ast-grep for workflows that work fine without it (setup-forge, brief-skill)
+- Requiring ast-grep for workflows that work fine without it (setup, brief-skill)
 - Mixing tier capabilities in a single extraction (e.g., T1 citations when only source reading was used)
 - Failing a workflow because the tier is "too low" — adapt behavior instead
 - Silent degradation when source is remote at Forge/Deep tier — always warn with actionable guidance
@@ -136,4 +136,4 @@ When source is remote (GitHub URL) and tier is Forge, Forge+, or Deep:
 - [skill-lifecycle.md](skill-lifecycle.md) — how tier affects workflow selection and artifact flow
 - [zero-hallucination.md](zero-hallucination.md) — Quick tier has lower confidence but the same integrity standard
 
-_Source: distilled from forge-tier.yaml, tier-rules.md, and setup-forge workflow_
+_Source: distilled from forge-tier.yaml, tier-rules.md, and setup workflow_

package/src/knowledge/provenance-tracking.md

@@ -36,7 +36,9 @@ With provenance tracking:
 **Implementation:**
 ```json
 {
+  "provenance_version": "2.0",
   "skill_name": "express-skill",
+  "skill_type": "single",
   "source_repo": "https://github.com/expressjs/express",
   "source_commit": "abc1234",
   "source_ref": "v0.5.0",
@@ -45,24 +47,28 @@ With provenance tracking:
     {
       "export_name": "createServer",
       "export_type": "function",
+      "source_library": "express",
       "params": ["options: ServerOptions"],
       "return_type": "Server",
       "source_file": "src/server.ts",
       "source_line": 23,
       "confidence": "T1",
       "extraction_method": "ast-grep",
-      "ast_node_type": "export_statement > function_declaration"
+      "ast_node_type": "export_statement > function_declaration",
+      "signature_source": "T1"
     },
     {
       "export_name": "parseConfig",
       "export_type": "function",
+      "source_library": "express",
       "params": ["input"],
       "return_type": null,
       "source_file": "src/config.ts",
       "source_line": 45,
       "confidence": "T1-low",
       "extraction_method": "source-read",
-      "ast_node_type": null
+      "ast_node_type": null,
+      "signature_source": "T1-low"
     }
   ]
 }
@@ -125,7 +131,7 @@ With provenance tracking:
 
 **Key Points:**
 - Provenance enables precise diffing — compare specific claims, not entire files
-- Severity classification uses the rules from audit-skill/data/severity-rules.md
+- Severity classification uses the rules from audit-skill/references/severity-rules.md
 - The drift report feeds into the update-skill workflow as re-extraction targets
 
 ### Example 4: Provenance Preservation During Updates

package/src/knowledge/qmd-registry.md

@@ -6,7 +6,7 @@ QMD collections in the Skill Forge follow a **progressive registry architecture*
 
 ## Rationale
 
-Early SKF versions used a blind auto-index strategy: setup-forge would scan all project directories and index them into QMD collections. This created three problems:
+Early SKF versions used a blind auto-index strategy: setup would scan all project directories and index them into QMD collections. This created three problems:
 
 - On fresh workspaces, auto-indexing found nothing — wasted work
 - Raw source code indexing produced low signal-to-noise search results
@@ -22,7 +22,7 @@ The progressive registry solves all three by indexing **curated workflow artifac
 | --- | --- | --- |
 | **Producer** | brief-skill, create-skill | Creates QMD collections from workflow artifacts and registers them in forge-tier.yaml |
 | **Consumer** | audit-skill, update-skill, create-stack-skill | Reads the registry, discovers collections by skill name and type, queries via qmd_bridge (see [tool-resolution.md](tool-resolution.md) for concrete resolution) |
-| **Janitor** | setup-forge | Cross-references live QMD collections against the registry, cleans orphans and stale entries |
+| **Janitor** | setup | Cross-references live QMD collections against the registry, cleans orphans and stale entries |
 
 ### Registry Schema
 
@@ -45,7 +45,7 @@ qmd_collections:
 
 **Optional field: `status`**
 
-The `status` field is only present when QMD embed verification fails during collection creation. When `status: "pending"` is set, the collection exists in QMD but vector embeddings may be incomplete — only BM25 keyword `search` is reliable. `vector_search` and `deep_search` may return no results until re-embedded. Collections without a `status` field are fully operational. The setup-forge janitor should flag `"pending"` collections for re-embedding.
+The `status` field is only present when QMD embed verification fails during collection creation. When `status: "pending"` is set, the collection exists in QMD but vector embeddings may be incomplete — only BM25 keyword `search` is reliable. `vector_search` and `deep_search` may return no results until re-embedded. Collections without a `status` field are fully operational. The setup janitor should flag `"pending"` collections for re-embedding.
 
 ### Collection Types
 
@@ -70,7 +70,7 @@ create-skill compiles skill → indexes {name}-extraction → registers in forge
 audit-skill reads registry → queries {name}-extraction for drift baseline
 update-skill reads registry → queries {name}-extraction for T2 enrichment
     ↓
-setup-forge reads registry + QMD state → cleans orphans, removes stale entries
+setup reads registry + QMD state → cleans orphans, removes stale entries
 ```
 
 ## Collection Gate
@@ -111,8 +111,8 @@ The `ccc_index_registry` array in forge-tier.yaml is a **parallel but separate**
 |--------|----------------|-------------------|
 | **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) |
+| **Lifecycle** | Per-skill: created by create-skill, consumed by audit/update-skill | Per-project: created by setup, verified by create-skill |
+| **Janitor** | setup step-03 (orphan/stale QMD collection cleanup) | setup 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.
@@ -139,7 +139,7 @@ Then append/replace the registry entry in forge-tier.yaml. Failures never block
 
 **Implementation:** Read `qmd_collections` from forge-tier.yaml. Find entry where `skill_name` matches AND `type` is `"extraction"`. If found, query via qmd_bridge. If not found, log and continue without T2 enrichment — not an error.
 
-### Example 3: Janitor Hygiene (setup-forge)
+### Example 3: Janitor Hygiene (setup)
 
 **Context:** Setup-forge verifies QMD health on every run.
 
@@ -151,4 +151,4 @@ Then append/replace the registry entry in forge-tier.yaml. Failures never block
 - [skill-lifecycle.md](skill-lifecycle.md) — end-to-end pipeline showing where producers and consumers sit
 - [provenance-tracking.md](provenance-tracking.md) — provenance map that provides file:line context without QMD
 
-_Source: progressive QMD registry architecture implemented across setup-forge, brief-skill, create-skill, audit-skill, and update-skill workflows_
+_Source: progressive QMD registry architecture implemented across setup, brief-skill, create-skill, audit-skill, and update-skill workflows_

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

@@ -1,11 +1,11 @@
 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
+overview,Knowledge Overview,"Entry point — knowledge map, JiT loading protocol, relationship to workflow references/ and assets/ 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/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
+skill-lifecycle,Skill Lifecycle,"End-to-end pipeline — workflow connections, artifact flow, decision rules for workflow selection, pipeline invocation syntax and aliases","lifecycle,pipeline,workflows,artifacts,chaining,headless",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
 manual-section-integrity,Manual Section Integrity,"[MANUAL] preservation — marker format, merge algorithm, orphan detection","manual,preservation,merge,markers",core,knowledge/manual-section-integrity.md
 qmd-registry,QMD Collection Registry,"Progressive registry architecture — producer/consumer/janitor roles, collection gate principle, forge-tier.yaml registry schema","qmd,registry,collections,deep,indexing",core,knowledge/qmd-registry.md

package/src/knowledge/skill-lifecycle.md

@@ -167,6 +167,21 @@ SS (compose) → SKILL.md (stack skill synthesized from individual skills + arch
 - SS detects integration patterns (e.g., "express + passport always used together for auth routes")
 - Individual skills track per-library provenance; stack skills track inter-library relationships
 
+## Pipeline Invocation
+
+Users can chain workflows by providing multiple codes to Ferris:
+
+```
+BS CS TS EX           — space-separated
+forge                 — alias for BS CS TS EX
+forge-quick           — alias for QS TS EX
+onboard               — alias for AN CS TS EX
+maintain              — alias for AS US TS EX
+CS[cocoindex] TS[min:80] EX  — with arguments and circuit breakers
+```
+
+Pipelines automatically activate headless mode. The forger passes data between workflows using the artifact flow described above. Circuit breakers halt the pipeline when output quality falls below a threshold (e.g., TS score < 60 blocks EX). See `shared/references/pipeline-contracts.md` for the full specification.
+
 ## Integration Points
 
 - **Setup Forge** must run before any other workflow — it establishes the tier
@@ -183,4 +198,4 @@ SS (compose) → SKILL.md (stack skill synthesized from individual skills + arch
 - [provenance-tracking.md](provenance-tracking.md) — how provenance flows through the pipeline
 - [version-paths.md](version-paths.md) — version-aware storage layout, path templates, and migration rules
 
-_Source: synthesized from all 12 workflow.md files (including VS, RA) and module-help.csv_
+_Source: synthesized from all 14 SKILL.md files (including VS, RA, RS, DS) and module-help.csv_

package/src/knowledge/split-body-strategy.md

@@ -50,6 +50,6 @@ Split-body affects only SKILL.md content movement to `references/`. The `scripts
 
 - [agentskills-spec.md](agentskills-spec.md) — 500-line guideline for SKILL.md body size and the `references/` directory structure
 - [skill-lifecycle.md](skill-lifecycle.md) — where split-body decisions fit in the compilation pipeline
-- `test-skill/data/scoring-rules.md` — tessl/split-body interaction and the pre-split baseline recommendation during test reporting
+- `test-skill/references/scoring-rules.md` — tessl/split-body interaction and the pre-split baseline recommendation during test reporting
 
 _Source: derived from agentskills.io split-body guidance and Vercel agent accuracy research (inline vs on-demand retrieval)_

package/src/knowledge/version-paths.md

@@ -35,16 +35,21 @@ All workflows MUST use these templates when constructing paths. Never hardcode p
 | `{forge_version}` | `{forge_data_folder}/{skill-name}/{version}/` | Version-specific workspace artifacts — provenance-map.json, evidence-report.md, extraction-rules.yaml, test-report |
 | `{forge_group}` | `{forge_data_folder}/{skill-name}/` | Parent directory — contains skill-brief.yaml (version-independent) and version subdirectories |
 
-### Platform Paths (Unchanged — Flat)
+### IDE Skill Root Paths (Unchanged — Flat)
 
-| Platform | Root Path |
-|----------|-----------|
-| `claude` | `.claude/skills/{skill-name}/` |
+Each IDE has its own skill root path derived from its `target_dir` in `platform-codes.yaml`. The snippet `root:` line uses this path. Examples:
+
+| IDE | Root Path |
+|-----|-----------|
+| `claude-code` | `.claude/skills/{skill-name}/` |
 | `cursor` | `.cursor/skills/{skill-name}/` |
-| `copilot` | `.agents/skills/{skill-name}/` |
-| _(legacy)_ | `skills/{skill-name}/` |
+| `github-copilot` | `.github/skills/{skill-name}/` |
+| `windsurf` | `.windsurf/skills/{skill-name}/` |
+| _(draft/legacy)_ | `skills/{skill-name}/` |
+
+See `skf-export-skill/assets/managed-section-format.md` for the complete IDE → Context File Mapping table with all 23 IDE root paths.
 
-Platform paths are **not versioned**. The export workflow resolves the active version from the manifest and references its `{skill_package}` when building the managed section. The snippet `root:` always uses the flat platform path.
+IDE skill root paths are **not versioned**. The export workflow resolves the active version from the manifest and references its `{skill_package}` when building the managed section. The snippet `root:` always uses the flat IDE skill root path.
 
 ## Directory Structure
 
@@ -139,12 +144,12 @@ The export manifest gains version awareness:
       "active_version": "0.6.0",
       "versions": {
         "0.5.0": {
-          "platforms": ["claude"],
+          "ides": ["claude-code"],
           "last_exported": "2026-03-15",
           "status": "archived"
         },
         "0.6.0": {
-          "platforms": ["claude", "copilot"],
+          "ides": ["claude-code", "github-copilot"],
           "last_exported": "2026-04-04",
           "status": "active"
         }
@@ -158,7 +163,7 @@ The export manifest gains version awareness:
 - `schema_version`: `"2"` — enables v1-to-v2 migration detection
 - `active_version`: The version whose `{skill_package}` supplies the context snippet for the managed section. Must match exactly one version with `status: "active"`
 - `versions.{v}.status`: `"active"` (currently exported), `"archived"` (previously exported, retained on disk), `"deprecated"` (dropped via drop-skill workflow, excluded from all exports), `"draft"` (created but never exported)
-- `versions.{v}.platforms`: Array of platforms this version was last exported to
+- `versions.{v}.ides`: Array of IDE identifiers from `config.yaml.ides` whose context file this version was last exported to (e.g. `["claude-code", "cursor"]`). NOT context file names, NOT skill root paths — the canonical IDE identifier used by the installer. Pre-rename manifests used `platforms` for this field; `skf-manifest-ops.py` silently upgrades them on read
 - `versions.{v}.last_exported`: ISO date of the last export
 
 **Only one version per skill can have `status: "active"` at any time.**
@@ -180,7 +185,7 @@ Renames a skill across all versions. Because the agentskills.io spec requires `n
 8. Export manifest: remove old key, add new key with same version data
 9. Platform context files (CLAUDE.md, AGENTS.md, .cursorrules): rebuild managed sections
 
-Rename is transactional — copy-verify-delete pattern. If any step fails, old skill remains intact. See `workflows/rename-skill/`.
+Rename is transactional — copy-verify-delete pattern. If any step fails, old skill remains intact. See `skf-rename-skill/`.
 
 ### Drop (DS - Drop Skill)
 
@@ -194,7 +199,7 @@ Drops a specific version or the entire skill with two modes:
 
 **Skill-level drop:** Removes the entire `{skill_group}` from the manifest. If purge, also deletes `{skill_group}` and `{forge_group}` directories.
 
-See `workflows/drop-skill/`.
+See `skf-drop-skill/`.
 
 ## Version Sanitization
 

package/src/module-help.csv

@@ -1,17 +1,18 @@
-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/Forge+/Deep)",,forge-tier.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,
-skf,anytime,Quick Skill,QS,,_bmad/skf/workflows/skillforge/quick-skill/workflow.md,skf_quick_skill,false,ferris,Create Mode,"Fast skill from a package name or GitHub URL — no brief needed",skills_output_folder,SKILL.md,
-skf,anytime,Stack Skill,SS,,_bmad/skf/workflows/skillforge/create-stack-skill/workflow.md,skf_create_stack_skill,false,ferris,Create Mode,"Consolidated project stack skill with integration patterns — code-mode (analyzes manifests) or compose-mode (synthesizes from existing skills + architecture doc)",skills_output_folder,SKILL.md,
-skf,anytime,Update Skill,US,,_bmad/skf/workflows/skillforge/update-skill/workflow.md,skf_update_skill,false,ferris,Surgeon Mode,"Smart regeneration preserving [MANUAL] sections after source changes",skills_output_folder,SKILL.md,
-skf,anytime,Audit Skill,AS,,_bmad/skf/workflows/skillforge/audit-skill/workflow.md,skf_audit_skill,false,ferris,Audit Mode,"Drift detection between skill and current source code",,"drift report",
-skf,anytime,Test Skill,TS,,_bmad/skf/workflows/skillforge/test-skill/workflow.md,skf_test_skill,false,ferris,Audit Mode,"Cognitive completeness verification — quality gate before export",,"completeness score",
-skf,anytime,Export Skill,EX,,_bmad/skf/workflows/skillforge/export-skill/workflow.md,skf_export_skill,false,ferris,Delivery Mode,"Package for distribution and inject context into CLAUDE.md/AGENTS.md/.cursorrules",skills_output_folder,"agentskills.io package",
-skf,anytime,Rename Skill,RS,,_bmad/skf/workflows/skillforge/rename-skill/workflow.md,skf_rename_skill,false,ferris,Management Mode,"Rename a skill across all its versions — transactional copy-verify-delete with platform context rebuild",skills_output_folder,"renamed skill group",
-skf,anytime,Drop Skill,DS,,_bmad/skf/workflows/skillforge/drop-skill/workflow.md,skf_drop_skill,false,ferris,Management Mode,"Drop a specific skill version or an entire skill — soft (deprecate) or hard (purge) with platform context rebuild",skills_output_folder,"updated manifest",
-skf,anytime,Verify Stack,VS,,_bmad/skf/workflows/skillforge/verify-stack/workflow.md,skf_verify_stack,false,ferris,Audit Mode,"Pre-code stack feasibility verification against architecture and PRD documents",forge_data_folder,"feasibility-report-{project_name}.md",
-skf,anytime,Refine Architecture,RA,,_bmad/skf/workflows/skillforge/refine-architecture/workflow.md,skf_refine_architecture,false,ferris,Architect Mode,"Improve architecture doc using verified skill data and VS feasibility findings",output_folder,"refined-architecture-{project_name}.md",
-skf,anytime,Workflow Status,WS,,,skf_workflow_status,false,ferris,Reference,"Show current lifecycle position, active skill briefs, and forge tier status",,lifecycle status,
-skf,anytime,Knowledge Index,KI,,_bmad/skf/knowledge/skf-knowledge-index.csv,skf_knowledge_index,false,ferris,Reference,"Cross-cutting principles and patterns — JiT loaded by workflows via index lookup",,"knowledge fragments",
+module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
+skf,skf-forger,Ferris — Skill Forge Agent,FF,"Skill compilation specialist — the forge master. Invoke to access all SKF workflows via guided menu.",,,anytime,,,false,,
+skf,skf-setup,Setup Forge,SF,"Initialize forge environment — detect tools and set capability tier (Quick/Forge/Forge+/Deep)",,,anytime,,"skf-analyze-source,skf-brief-skill,skf-quick-skill,skf-verify-stack",false,,forge-tier.yaml
+skf,skf-analyze-source,Analyze Source,AN,"Discover what to skill in a large repo — produces recommended skill briefs",,,anytime,skf-setup,skf-brief-skill,false,forge_data_folder,skill-brief.yaml
+skf,skf-brief-skill,Brief Skill,BS,"Design a skill scope through guided discovery",,,anytime,"skf-setup,skf-analyze-source",skf-create-skill,false,forge_data_folder,skill-brief.yaml
+skf,skf-create-skill,Create Skill,CS,"Compile a skill from a brief — supports --batch for multiple briefs",,--batch,anytime,skf-brief-skill,"skf-test-skill,skf-create-stack-skill",false,skills_output_folder,SKILL.md
+skf,skf-quick-skill,Quick Skill,QS,"Fast skill from a package name or GitHub URL — no brief needed",,<package-name | github-url>,anytime,skf-setup,skf-test-skill,false,skills_output_folder,SKILL.md
+skf,skf-create-stack-skill,Stack Skill,SS,"Consolidated project stack skill with integration patterns — code-mode or compose-mode",,,anytime,skf-create-skill,skf-test-skill,false,skills_output_folder,SKILL.md
+skf,skf-update-skill,Update Skill,US,"Smart regeneration preserving [MANUAL] sections after source changes",,,anytime,skf-export-skill,,false,skills_output_folder,SKILL.md
+skf,skf-audit-skill,Audit Skill,AS,"Drift detection between skill and current source code",,,anytime,skf-export-skill,,false,,drift report
+skf,skf-verify-stack,Verify Stack,VS,"Pre-code stack feasibility verification against architecture and PRD documents",,,anytime,skf-setup,skf-refine-architecture,false,forge_data_folder,feasibility-report-{project_name}.md
+skf,skf-refine-architecture,Refine Architecture,RA,"Improve architecture doc using verified skill data and VS feasibility findings",,,anytime,skf-verify-stack,,false,output_folder,refined-architecture-{project_name}.md
+skf,skf-test-skill,Test Skill,TS,"Cognitive completeness verification — quality gate before export",,,anytime,"skf-create-skill,skf-create-stack-skill,skf-quick-skill",skf-export-skill,false,,completeness score
+skf,skf-export-skill,Export Skill,EX,"Package for distribution and inject context into CLAUDE.md/AGENTS.md/.cursorrules",,,anytime,skf-test-skill,"skf-update-skill,skf-audit-skill,skf-rename-skill,skf-drop-skill",false,skills_output_folder,agentskills.io package
+skf,skf-rename-skill,Rename Skill,RS,"Rename a skill across all its versions — transactional copy-verify-delete with platform context rebuild",,,anytime,skf-export-skill,,false,skills_output_folder,renamed skill group
+skf,skf-drop-skill,Drop Skill,DS,"Drop a specific skill version or an entire skill — soft (deprecate) or hard (purge) with platform context rebuild",,,anytime,skf-export-skill,,false,skills_output_folder,updated manifest
+skf,skf-forger,Knowledge Index,KI,"Cross-cutting principles and patterns — JiT loaded by workflows via index lookup",,,anytime,,,false,,knowledge fragments
+skf,skf-forger,Workflow Status,WS,"Show current lifecycle position, active skill briefs, and forge tier status",,,anytime,,,false,,lifecycle status