bmad-module-skill-forge 1.8.0 → 2.0.0

package/docs/index.md

@@ -60,8 +60,9 @@ npx bmad-module-skill-forge install
 Then generate your first skill:
 
 ```
-@Ferris SF              # Set up your forge
-@Ferris QS <package>    # Generate a skill in under a minute
+@Ferris SF                       # Set up your forge
+@Ferris forge-auto <repo-or-url>   # Zero-ceremony: a repo or doc URL → verified skill
+@Ferris QS <package>             # Or a fast skill from a package name in under a minute
 ```
 
-See [Getting Started](./getting-started/) for platform support, tier selection, and troubleshooting.
+[forge-auto](./forge-auto/) is the recommended starting point — one command, no configuration. See [Getting Started](./getting-started/) for platform support, tier selection, and troubleshooting.

package/docs/skill-model.md

@@ -92,7 +92,7 @@ This is useful for comparing skill quality across tiers for the same target:
 # 4. Reset to tier_override: ~ (auto-detect)
 ```
 
-Set `tier_override` to `Quick`, `Forge`, `Forge+`, or `Deep`. Set to `~` (null) to return to auto-detection. The override is respected by all tier-aware workflows (CS, SS, US, AS, TS).
+Set `tier_override` to `Quick`, `Forge`, `Forge+`, or `Deep`. Set to `~` (null) to return to auto-detection. The override is respected by all tier-aware workflows (AN, BS, CS, SS, US, AS, TS).
 
 ---
 

package/docs/troubleshooting.md

@@ -27,7 +27,7 @@ If setup reports that ast-grep was not detected, install it to unlock the Forge
 
 ### "No skill brief found"
 
-Run `@Ferris BS` first to create a skill brief, or use `@Ferris QS` for brief-less generation. `CS` requires either a brief or a direct invocation with scope arguments.
+Run `@Ferris BS` first to create a skill brief, or use `@Ferris QS` for brief-less generation. `CS` always requires a brief — either a `skill-brief.yaml` produced by `BS` (or `AN`), or pass the skill name so it resolves one from your forge-data folder. For brief-less generation use `QS`.
 
 ### "Ecosystem check: official skill exists"
 
@@ -41,6 +41,22 @@ Quick tier reads source without AST analysis, so signatures are read directly fr
 
 Install [cocoindex-code](https://github.com/cocoindex-io/cocoindex-code) to unlock the Forge+ tier. CCC indexes your codebase and pre-ranks files by semantic relevance before AST extraction, improving coverage on projects with 500+ files.
 
+### `@Ferris deepwiki` shows a deprecation notice
+
+The auto pipeline was briefly named `deepwiki`; it's now [`forge-auto`](../forge-auto/) — renamed to avoid confusion with the DeepWiki MCP, since the pipeline compiles a verified skill from source and does **not** call that MCP. `deepwiki` still works (it resolves to `forge-auto`) but prints a one-time notice. Switch your commands to `@Ferris forge-auto <repo-or-doc-url>`.
+
+### `@Ferris onboard` returns an error
+
+The `onboard` alias was removed. Its replacement is [`forge-auto`](../forge-auto/), which does everything `onboard` did plus auto-scope, auto-brief, and a stricter 90% quality gate. Run `@Ferris forge-auto <repo-or-doc-url>` instead.
+
+### forge-auto halted at the Test stage
+
+forge-auto runs Test Skill with a stricter **90% quality threshold** (vs the default 80%), so a skill that scores below 90% halts at TS with a gap report rather than exporting a weak skill. Run `@Ferris US` to address the gaps it lists, then `@Ferris TS EX` to re-test and export. If 90% is stricter than you need, run the individual workflows or `forge` instead, which use the default threshold.
+
+### My campaign stopped partway — how do I resume?
+
+Campaign is designed for exactly this. State lives in `_campaign-state.yaml` on disk, so context death, a session timeout, or a machine restart loses nothing. Run `@Ferris campaign resume` — Ferris validates the state file, skips completed skills, and picks up from the next incomplete skill in dependency order. If the state file is corrupted, Ferris falls back to the `.bak` copy automatically. To re-process one specific skill, use `@Ferris campaign resume --from=<skill>`.
+
 ---
 
 ## Still stuck?

package/docs/verifying-a-skill.md

@@ -61,7 +61,7 @@ Every file in the per-skill output carries a specific job. Here's the lookup tab
 | Which symbols are documented and where did each come from? | `forge-data/{name}/{version}/provenance-map.json` |
 | What AST patterns were used for extraction? | `forge-data/{name}/{version}/extraction-rules.yaml` |
 | What signatures, types, and examples did the extractor actually capture? | `forge-data/{name}/{version}/evidence-report.md` |
-| How was the skill scored? Show me the math. | `forge-data/{name}/{version}/test-report-{name}.md` |
+| How was the skill scored? Show me the math. | `forge-data/{name}/{version}/test-report-{name}-{run_id}.md` (per-run, run-id-suffixed — newest wins) |
 | How was the skill scoped, and what was deliberately left out? | `forge-data/{name}/skill-brief.yaml` |
 
 Everything a reader needs to reconstruct the compilation is in the two sibling directories: `skills/` ships to consumers, `forge-data/` is the audit trail.
@@ -156,16 +156,22 @@ Your forge tier determines which categories can be scored:
 
 When categories are skipped, their combined weight is redistributed proportionally to the remaining active categories. A Quick-tier skill and a Deep-tier skill both pass at the same 80% threshold — the score reflects what your tier can actually measure.
 
+### Hard gate
+
+Before scoring, a hard gate scans all findings for **Critical** and **High** severity. If any are present, the pipeline blocks immediately — no score is computed and the skill cannot pass regardless of coverage percentage. Medium, Low, and Info findings pass through to scoring.
+
 ### Pass/fail
 
 ```
-threshold = custom_threshold OR 80% (default)
+threshold = pipeline_default OR custom_threshold OR 80% (default)
 
 score >= threshold  →  PASS  →  Recommend export-skill
 score <  threshold  →  FAIL  →  Recommend update-skill
 ```
 
-The default is 80%. You can override it by specifying a custom threshold when invoking the workflow (e.g., "test this skill with a 70% threshold").
+The default threshold is **80%**. Pipeline aliases declare their own defaults: `forge-auto` targets **90%**, `forge` and `forge-quick` target **80%**. You can override any default with a custom threshold (e.g., `TS[min:85]`).
+
+When a skill scores between 80% and its target threshold (e.g., 82% against a 90% target), the soft gate falls back to the 80% floor — the skill passes, but an evidence report is written to `forge-data/{skill}/{version}/evidence-report-fallback.md` documenting the quality compromise.
 
 ### Gap severities
 

package/docs/why-skf.md

@@ -52,7 +52,7 @@ See the [Verifying a Skill](../verifying-a-skill/) page for the full three-step
 
 ### The curious developer
 
-Your agent just hallucinated a method that doesn't exist, again. You want this to stop, and you don't want to read a 569-line architecture page before running your first command.
+Your agent just hallucinated a method that doesn't exist, again. You want this to stop, and you don't want to read a long architecture reference before running your first command.
 → Start with [Getting Started](../getting-started/).
 
 ### The BMAD user

package/docs/workflows.md

@@ -1,6 +1,6 @@
 ---
 title: Workflows
-description: All 14 SKF workflows with commands, steps, and connection diagram
+description: All 15 SKF workflows with commands, steps, and connection diagram
 ---
 
 Trigger workflows by typing commands to [Ferris](../agents/). See [Concepts](../concepts/) for definitions.
@@ -24,7 +24,10 @@ Trigger workflows by typing commands to [Ferris](../agents/). See [Concepts](../
 **Flags:**
 
 - `--require-tier=<Quick|Forge|Forge+|Deep>` — fail-fast for CI: if the calculated tier does not satisfy the requested tier (tool-prerequisite check, not a name comparison — Deep does NOT subsume Forge+ because Deep does not require ccc), the workflow halts with a "REQUIRED TIER NOT MET" block and exits without chaining to the health check. Pipelines branch on the JSON envelope's `require_tier_satisfied` field.
-- `--headless` / `-H` — see [Headless Mode](#headless-mode) below. For `/skf-setup` specifically, headless mode emits a single-line `SKF_SETUP_RESULT_JSON: {…}` envelope to stdout (schema-locked, includes `tier`, `previous_tier`, `tier_changed`, `tools`, `tools_added`/`removed`, `files_written`, `warnings`, `error`) and SUPPRESSES the human-readable banner — the entire payload pipelines need is on one parseable line.
+- `--orphan-action=<keep|remove>` — resolve the orphan QMD-collection removal gate non-interactively, even outside `--headless`.
+- `--ccc-skip-index` — skip CCC indexing (envelope `ccc_index.status` becomes `"skipped"`) — the fast re-probe lane to refresh the detected tier without paying the full re-index cost.
+- `--quiet` — suppress the human-readable FORGE STATUS banner and emit the envelope only.
+- `--headless` / `-H` — see [Headless Mode](#headless-mode) below. For `/skf-setup` specifically, headless mode emits a single-line `SKF_SETUP_RESULT_JSON: {…}` envelope to stdout (schema-locked, includes `status` — the primary branch field — plus `tier`, `previous_tier`, `tier_changed`, `tools`, `tools_added`/`removed`, `files_written`, `warnings`, `error`) and SUPPRESSES the human-readable banner — the entire payload pipelines need is on one parseable line.
 
 **Agent:** Ferris (Architect mode)
 
@@ -52,7 +55,7 @@ Trigger workflows by typing commands to [Ferris](../agents/). See [Concepts](../
 
 **When to Use:** After Brief Skill, or with an existing skill-brief.yaml.
 
-**Key Steps:** Load brief → Ecosystem check → Extract (AST + scripts/assets) → QMD enrich (Deep) → Compile → Validate → Generate
+**Key Steps:** Load brief → Ecosystem check → Extract (AST + scripts/assets) → QMD enrich (Deep) → Compile → Doc sources → Auto-shard → Doc-rot → Validate → Generate
 
 **Agent:** Ferris (Architect mode)
 
@@ -80,6 +83,8 @@ Trigger workflows by typing commands to [Ferris](../agents/). See [Concepts](../
 
 **Purpose:** Brief-less fast skill with package-to-repo resolution.
 
+**Note:** QS is **tier-unaware** — it always runs at community tier and does not use ast-grep, CCC, or QMD even when your forge is configured at Forge+/Deep. For tier-aware compilation, use `BS → CS`, `forge`, or `forge-auto`. See [Skill Model](../skill-model/).
+
 **When to Use:** When you need a skill quickly — no brief needed. Accepts package names or GitHub URLs. Append `@version` to target a specific version (e.g., `@Ferris QS cognee@1.0.0`).
 
 **Key Steps:** Resolve target → Ecosystem check → Quick extract → Compile → Validate → Write
@@ -141,7 +146,7 @@ Trigger workflows by typing commands to [Ferris](../agents/). See [Concepts](../
 
 **When to Use:** To check if a skill has fallen out of date with its source code. Works for both individual skills and stack skills.
 
-**Key Steps:** Load skill → Re-index source → Structural diff (incl. script/asset drift) → Semantic diff (Deep) → Classify severity → Report
+**Key Steps:** Load skill → Re-index source → Structural diff (incl. script/asset drift) → Semantic diff (Deep) → Classify severity → Doc drift → Report
 
 **Stack skill support:** Code-mode stacks are audited per-library against their sources. Compose-mode stacks check constituent freshness via metadata hash comparison — if a constituent skill was updated after the stack was composed, audit flags it as constituent drift. Stack skills that need updating are redirected to `@Ferris SS` for re-composition (surgical update is not supported for stacks).
 
@@ -157,9 +162,9 @@ Trigger workflows by typing commands to [Ferris](../agents/). See [Concepts](../
 
 **When to Use:** After creating or updating a skill, before exporting.
 
-**Key Steps:** Load skill → Detect mode → Coverage check → Coherence check → External validation (skill-check, tessl) → Score → Gap report
+**Key Steps:** Load skill → Detect mode → Coverage check → Coherence check → External validation (skill-check, tessl) → Hard gate → Score → Gap report
 
-**Scored Categories:** Export Coverage (36%), Signature Accuracy (22%), Type Coverage (14%), Coherence (18%), External Validation (10%). Default pass threshold: **80%**. Pass routes to Export Skill; fail routes to Update Skill with a gap report. See [Completeness Scoring](../verifying-a-skill/#how-the-score-is-computed) for the full formula and tier adjustments.
+**Scored Categories:** Export Coverage (36%), Signature Accuracy (22%), Type Coverage (14%), Coherence (18%), External Validation (10%). Default pass threshold: **80%** (per-pipeline defaults: forge-auto 90%, forge 80%). Pass routes to Export Skill; fail routes to Update Skill with a gap report. See [Completeness Scoring](../verifying-a-skill/#how-the-score-is-computed) for the full formula and tier adjustments.
 
 **Agent:** Ferris (Audit mode)
 
@@ -211,6 +216,22 @@ Trigger workflows by typing commands to [Ferris](../agents/). See [Concepts](../
 
 ---
 
+## Orchestration Workflows
+
+### Campaign Orchestration
+
+**Command:** `@Ferris campaign`
+
+**Purpose:** Orchestrate multi-library skill production across sessions with dependency tracking and resume.
+
+**When to Use:** When you need to produce 15+ coordinated skills with dependency ordering — too many for manual one-at-a-time pipeline runs.
+
+**Key Steps:** Setup → Strategy → Pin Validation → Provenance → Skill Loop → Tier B Batch → Capstone → Verify → Refine → Export → Maintenance
+
+**Agent:** Ferris (Management mode)
+
+---
+
 ## Management Workflows
 
 ### Rename Skill (RS)
@@ -280,21 +301,36 @@ flowchart TD
     TS --> EX[Export Skill]
 ```
 
-> **One workflow per session** (unless using pipeline mode). Each arrow in the diagrams above represents a new conversation session. Clear your context between workflows for best results — or use pipeline mode to chain them automatically. See [Pipeline Mode](#pipeline-mode) below.
+**Campaign orchestration path:**
+
+```mermaid
+flowchart TD
+    CAMPAIGN[Campaign Orchestration] --> SETUP[Setup + Strategy]
+    SETUP --> PINS[Pin Validation + Provenance]
+    PINS --> LOOP["Skill Loop<br/>(BS → CS → TS → EX per skill)"]
+    LOOP --> BATCH[Tier B Batch]
+    BATCH --> CAP[Capstone — Stack Skill]
+    CAP --> VER[Verify + Refine]
+    VER --> EXPORT[Export — write-gate HALT]
+    EXPORT --> MAINT[Maintenance + Campaign Report]
+```
+
+> **One workflow per session** (unless using pipeline mode or campaign). Each arrow in the standard and compose-mode diagrams represents a new conversation session. Campaign manages its own multi-session orchestration internally — see [Campaign Orchestration](../campaign/). Clear your context between workflows for best results — or use pipeline mode to chain them automatically. See [Pipeline Mode](#pipeline-mode) below.
 
 ---
 
 ## Workflow Categories
 
-| Category                  | Workflows      | Description                                                                                                                      |
-| ------------------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| Core                      | SF, BS, CS, US | Setup, brief, create, and update skills                                                                                          |
-| Feature                   | QS, SS, AN     | Quick skill, stack skill, and analyze source                                                                                     |
-| Quality                   | AS, TS         | Detect skill drift (AS) and verify skill completeness (TS)                                                                       |
-| Architecture Verification | VS, RA         | Pre-code architecture feasibility and refinement                                                                                 |
-| Management                | RS, DS         | Rename and drop skill versions with transactional safety                                                                         |
-| Utility                   | EX             | Package and export for consumption                                                                                               |
-| In-Agent                  | WS, KI         | WS: show lifecycle position, active briefs, and forge tier; KI: list knowledge fragments (both in-agent, no file-based workflow) |
+| Category                  | Workflows         | Description                                                                                                                      |
+| ------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| Core                      | SF, BS, CS, US    | Setup, brief, create, and update skills                                                                                          |
+| Feature                   | QS, SS, AN        | Quick skill, stack skill, and analyze source                                                                                     |
+| Quality                   | AS, TS            | Detect skill drift (AS) and verify skill completeness (TS)                                                                       |
+| Architecture Verification | VS, RA            | Pre-code architecture feasibility and refinement                                                                                 |
+| Orchestration             | Campaign          | Multi-library skill production with dependency tracking and resume                                                               |
+| Management                | RS, DS            | Rename and drop skill versions with transactional safety                                                                         |
+| Utility                   | EX                | Package and export for consumption                                                                                               |
+| In-Agent                  | WS, KI            | WS: show lifecycle position, active briefs, and forge tier; KI: list knowledge fragments (both in-agent, no file-based workflow) |
 
 ---
 
@@ -313,12 +349,14 @@ Instead of running one workflow per session, you can chain multiple workflows in
 
 ### Pipeline Aliases
 
-| Alias         | Expands To    | First Workflow | Required Target                              |
-| ------------- | ------------- | -------------- | -------------------------------------------- |
-| `forge`       | `BS CS TS EX` | BS             | GitHub URL or local path **+** skill name    |
-| `forge-quick` | `QS TS EX`    | QS             | GitHub URL **or** package name               |
-| `onboard`     | `AN CS TS EX` | AN             | Project path (defaults to current directory) |
-| `maintain`    | `AS US TS EX` | AS             | Existing skill name                          |
+The `forge-auto` alias is the recommended way to create skills — one command, zero configuration. It chains five workflows with auto-mode flags so you get a verified skill without touching a brief or scope file.
+
+| Alias         | Expands To                             | First Workflow | Required Target                              |
+| ------------- | -------------------------------------- | -------------- | -------------------------------------------- |
+| `forge-auto`    | `AN[auto] BS[auto] CS TS[min:90] EX`  | AN             | GitHub URL, doc URL, or `--pin <version>`    |
+| `forge`       | `BS CS TS EX`                          | BS             | GitHub URL or local path **+** skill name    |
+| `forge-quick` | `QS TS EX`                            | QS             | GitHub URL **or** package name               |
+| `maintain`    | `AS US TS EX`                          | AS             | Existing skill name                          |
 
 **The first workflow's input contract defines what arguments the pipeline needs.** A bare package name works for `forge-quick` (QS resolves packages via the registry) but **not** for `forge` — BS requires both an unambiguous target (URL or path) and a skill name.
 
@@ -334,11 +372,13 @@ Instead of running one workflow per session, you can chain multiple workflows in
 ### Examples
 
 ```
+@Ferris forge-auto https://github.com/honojs/hono                     — zero-ceremony skill
+@Ferris forge-auto https://docs.example.com                            — docs-only skill
+@Ferris forge-auto https://github.com/honojs/hono --pin v4.6.0         — pinned version
 @Ferris forge-quick @tanstack/query                                  — QS + TS + EX for TanStack Query
 @Ferris forge https://github.com/topoteretes/cognee cognee           — BS + CS + TS + EX, explicit URL + name
 @Ferris forge https://github.com/topoteretes/cognee cognee "public API only"   — with scope hint
 @Ferris maintain cocoindex                                           — AS + US + TS + EX for an existing cocoindex skill
-@Ferris onboard                                                      — AN + CS + TS + EX on the current project
 ```
 
 ---
@@ -358,10 +398,10 @@ You can also set `headless_mode: true` in your forge preferences (`_bmad/_memory
 **Exception — `/skf-setup` headless emits a single-line JSON envelope.** Unlike other workflows, headless `/skf-setup` SUPPRESSES the human-readable status banner entirely and emits exactly one prefixed line on stdout:
 
 ```
-SKF_SETUP_RESULT_JSON: {"skf_setup":{"tier":"Deep","previous_tier":"Forge","tier_changed":true,"tools":{...},"tools_added":[...],"tools_removed":[],"config_path":"...","ccc_index":{...},"files_written":[...],"tier_override_active":false,"tier_override_invalid":false,"require_tier_satisfied":null,"warnings":[],"error":null}}
+SKF_SETUP_RESULT_JSON: {"skf_setup":{"status":"success","tier":"Deep","previous_tier":"Forge","tier_changed":true,"tools":{...},"tools_added":[...],"tools_removed":[],"config_path":"...","ccc_index":{...},"files_written":[...],"tier_override_active":false,"tier_override_invalid":false,"require_tier_satisfied":null,"warnings":[],"error":null}}
 ```
 
-Parent skills and CI pipelines `grep` one line out of the workflow log to learn the outcome — no ASCII-art parsing, no race against the [`forge-tier.yaml`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/skf-setup/references/write-config.md) writer. The envelope schema is versioned at [`src/shared/scripts/schemas/skf-setup-result-envelope.v1.json`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/shared/scripts/schemas/skf-setup-result-envelope.v1.json) and asserted against on every emit.
+Parent skills and CI pipelines `grep` one line out of the workflow log to learn the outcome — no ASCII-art parsing, no race against the [`forge-tier.yaml`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/skf-setup/references/write-config.md) writer. Branch on the top-level `status` field (`success`, `tier_failure`, `write_failure`, or `blocked`) rather than composing the outcome from `require_tier_satisfied` + `error`. The envelope schema is versioned at [`src/shared/scripts/schemas/skf-setup-result-envelope.v1.json`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/shared/scripts/schemas/skf-setup-result-envelope.v1.json) and asserted against on every emit.
 
 **Exception — `/skf-quick-skill` headless emits structured progress + result envelopes.** Headless `/skf-quick-skill` runs are first-class building blocks for batch automators. Three operational contracts beyond per-gate auto-proceed:
 
@@ -383,7 +423,7 @@ Parent skills and CI pipelines `grep` one line out of the workflow log to learn
    | 3    | resolution-failure  |
    | 4    | write-failure       |
    | 5    | overwrite-cancelled |
-   | 6    | compile-cancelled   |
+   | 6    | user-cancelled      |
    | 7    | finalize-blocked    |
 
 3. **Error-variant result contract on every HARD HALT.** A `SKF_QUICK_SKILL_RESULT_JSON: {…}` envelope is emitted on `stderr` (always) and copied to `{skill_package}/quick-skill-result-latest.json` when the skill package is known (HALTs at step 5 §1 onward). The schema and full population rules live in [`src/skf-quick-skill/SKILL.md`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/skf-quick-skill/SKILL.md) § "Result Contract on HARD HALT".
@@ -409,11 +449,17 @@ Parent skills and CI pipelines `grep` one line out of the workflow log to learn
 
 **Presets (`--preset <name>`).** Loads `{sidecar_path}/brief-presets/{name}.yaml` and merges its keys as defaults at step 1 §8; explicit headless args override preset values. The preset file is YAML containing any subset of the headless args above; unknown fields are ignored with a warning. Useful for repeated patterns — e.g. briefing 5 SaaS SDKs that all share `source_authority=community`, `scope_type=full-library`, `scripts_intent=skip`.
 
+**Exception — the management and verification workflows emit structured result envelopes too.** Beyond per-gate auto-proceed, Drop Skill, Rename Skill, and Refine Architecture each emit a single-line `SKF_*_RESULT_JSON: {…}` envelope on every terminal exit (`status: "success"` on the happy path, `status: "error"` with a typed `halt_reason` on any HARD HALT) and exit with a stable code so automators branch on the failure class without grepping message text. All three honour the universal `cancel`/`exit`/`:q` affordance at any prompt (exit `6`, `halt_reason: "user-cancelled"`).
+
+- **`/skf-drop-skill` (DS)** — exit `2` `input-missing`/`input-invalid`, `4` `write-failure` (covers manifest-write, context-rebuild, and full-purge `delete-failed`), `5` state-conflict (active-version guard). Schema and `halt_reason` list in [`src/skf-drop-skill/SKILL.md`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/skf-drop-skill/SKILL.md) § "Exit Codes" / "Result Contract (Headless)".
+- **`/skf-rename-skill` (RS)** — exit `2` `input-missing`/`input-invalid`, `4` `write-failure` (`copy-failed`, `write-failed`, `manifest-write-failed`; the §7 context rebuild is best-effort and never halts), `5` state-conflict (name-collision, source-authority, concurrent-run lock). Schema in [`src/skf-rename-skill/SKILL.md`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/skf-rename-skill/SKILL.md) § "Exit Codes" / "Result Contract (Headless)".
+- **`/skf-refine-architecture` (RA)** — exit `2` `input-missing`/`input-invalid`, `4` `write-failure`, `7` `inventory-unreliable`, `8` `recovery-failed` (durability state insufficient to reconstruct findings, or the compiled doc is missing its `## Refinement Summary`). Schema in [`src/skf-refine-architecture/SKILL.md`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/skf-refine-architecture/SKILL.md) § "Exit Codes" / "Result Contract (Headless)".
+
 ---
 
 ## Terminal Step: Health Check
 
-All 14 workflows above share the same final step — a **health check** defined in [`src/shared/health-check.md`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/shared/health-check.md). This isn't a workflow you invoke directly; there's no command code and no menu entry. Each workflow ends with a dedicated local `step-NN-health-check.md` whose `nextStepFile` points at the shared file, so the health check fires automatically once the main work is done. After the main work is done, Ferris reflects internally on the execution:
+All 15 workflows above share the same final step — a **health check** defined in [`src/shared/health-check.md`](https://github.com/armelhbobdad/bmad-module-skill-forge/blob/main/src/shared/health-check.md). This isn't a workflow you invoke directly; there's no command code and no menu entry. Each workflow ends with a dedicated local `step-NN-health-check.md` whose `nextStepFile` points at the shared file, so the health check fires automatically once the main work is done. After the main work is done, Ferris reflects internally on the execution:
 
 - Did any step instruction lead the agent astray or cause unnecessary back-and-forth?
 - Was any step ambiguous, forcing the agent to guess?

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-module-skill-forge",
-  "version": "1.8.0",
+  "version": "2.0.0",
   "description": "BMAD module — Turn code and docs into instructions AI agents can actually follow. Progressive capability tiers (Quick/Forge/Forge+/Deep).",
   "keywords": [
     "bmad",
@@ -53,7 +53,7 @@
     "test:cli": "node test/test-cli-integration.js",
     "test:install": "node test/test-installation-components.js",
     "test:knowledge": "node test/test-knowledge-base.js",
-    "test:python": "uv run --with pytest --with pyyaml --with jsonschema pytest test/test-compute-score-contract.py test/test-skf-preflight.py test/test-skf-skill-inventory.py test/test-skf-validate-output.py test/test-skf-validate-frontmatter.py test/test-skf-manifest-ops.py test/test-skf-rebuild-managed-sections.py test/test-skf-atomic-write.py test/test-skf-severity-classify.py test/test-skf-structural-diff.py test/test-skf-detect-tools.py test/test-skf-forge-tier-rw.py test/test-skf-emit-result-envelope.py test/test-skf-qmd-classify-collections.py test/test-skf-merge-ccc-exclusions.py test/test-skf-resolve-package.py test/test-skf-extract-public-api.py test/test-skf-render-quick-metadata.py test/test-skf-validate-brief-inputs.py test/test-skf-emit-brief-result-envelope.py test/test-skf-write-skill-brief.py test/test-skf-detect-workspaces.py test/test-skf-recommend-scope-type.py test/test-skf-detect-language.py test/test-skf-description-guard.py test/test-skf-detect-scripts-assets.py test/test-skf-hash-content.py test/test-skf-validate-brief-schema.py test/test-skf-check-workspace-drift.py test/test-skf-update-active-symlink.py test/test-skf-build-change-manifest.py test/test-skf-provenance-gap-dispatch.py test/test-skf-resolve-authoritative-files.py test/test-skf-scan-manifests.py test/test-skf-pair-intersect.py test/test-skf-enumerate-stack-skills.py test/test-skf-compare-file-hashes.py test/test-skf-load-provenance.py test/test-skf-scan-skill-md-structure.py test/test-skf-disqualify-candidates.py test/test-skf-chain-reachability.py -v",
+    "test:python": "uv run --with pytest --with pyyaml --with jsonschema pytest test/test-compute-score-contract.py test/test-skf-preflight.py test/test-skf-skill-inventory.py test/test-skf-validate-output.py test/test-skf-validate-frontmatter.py test/test-skf-manifest-ops.py test/test-skf-rebuild-managed-sections.py test/test-skf-atomic-write.py test/test-skf-severity-classify.py test/test-skf-structural-diff.py test/test-skf-detect-tools.py test/test-skf-forge-tier-rw.py test/test-skf-emit-result-envelope.py test/test-skf-qmd-classify-collections.py test/test-skf-merge-ccc-exclusions.py test/test-skf-resolve-package.py test/test-skf-extract-public-api.py test/test-skf-render-quick-metadata.py test/test-skf-validate-brief-inputs.py test/test-skf-emit-brief-result-envelope.py test/test-skf-write-skill-brief.py test/test-skf-detect-workspaces.py test/test-skf-recommend-scope-type.py test/test-skf-detect-language.py test/test-skf-language-corpora.py test/test-skf-merge-doc-urls.py test/test-skf-derive-assembly-shape.py test/test-skf-description-guard.py test/test-skf-detect-scripts-assets.py test/test-skf-hash-content.py test/test-skf-validate-brief-schema.py test/test-skf-check-workspace-drift.py test/test-skf-update-active-symlink.py test/test-skf-build-change-manifest.py test/test-skf-provenance-gap-dispatch.py test/test-skf-resolve-authoritative-files.py test/test-skf-scan-manifests.py test/test-skf-pair-intersect.py test/test-skf-enumerate-stack-skills.py test/test-skf-compare-file-hashes.py test/test-skf-load-provenance.py test/test-skf-scan-skill-md-structure.py test/test-skf-disqualify-candidates.py test/test-skf-chain-reachability.py test/test-skf-shape-detect.py test/test-skf-detect-docs.py test/test-skf-step-doc-sources.py test/test-skf-step-doc-drift.py test/test-skf-step-hard-gate.py test/test-skf-per-pipeline-thresholds.py test/test-skf-evidence-report-fallback.py test/test-skf-validate-pins.py test/test-skf-auto-shard.py test/test-skf-preapply.py test/test-skf-step-doc-rot.py test/test-skf-campaign-state.py test/test-skf-campaign-pins.py test/test-skf-campaign-deps.py test/test-skf-campaign-report.py test/test-skf-campaign-stepfiles.py test/test-skf-campaign-validate-state.py test/test-skf-campaign-provenance.py test/test-skf-campaign-parse-manifest.py test/test-skf-campaign-render-kickoff.py -v",
     "test:schemas": "node test/test-agent-schema.js",
     "test:workflow": "node test/test-workflow-state.js",
     "validate:refs": "node tools/validate-file-refs.js --strict",

package/src/module-help.csv

@@ -1,6 +1,7 @@
 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-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,skf-campaign",false,,forge-tier.yaml
+skf,skf-campaign,Campaign,CA,"Orchestrate multi-library skill production across sessions — dependency tracking, file-based state, and resume",,resume [--from=<skill>],anytime,skf-setup,,false,forge_data_folder,_campaign-state.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

package/src/shared/_known-workarounds.yaml

@@ -0,0 +1,155 @@
+version: 1
+workarounds:
+  - fingerprint: "```api\nGET /api/v1/skills/compile"
+    fix: "```\nskf compile --target <skill-dir>"
+    source: gmc-batch-2024-q4
+    severity: high
+    description: Hallucinated REST API endpoint replaced with correct CLI invocation
+
+  - fingerprint: 'requires-python = ">=3.8"'
+    fix: 'requires-python = ">=3.9"'
+    source: gmc-batch-2024-q4
+    severity: medium
+    description: Stale Python 3.8 minimum version updated to 3.9 baseline
+
+  - fingerprint: "## outputs\n\n## steps"
+    fix: "## Outputs\n\n## Steps"
+    source: gmc-batch-2025-q1
+    severity: high
+    description: Lowercase heading violates skill-sections spec capitalization rules
+
+  - fingerprint: "confidence: unverified"
+    fix: "confidence: T1-inferred"
+    source: gmc-batch-2025-q1
+    severity: medium
+    description: Missing provenance tier replaced with correct T1 annotation
+
+  - fingerprint: "[source: unknown]"
+    fix: "[source: repo-readme]"
+    source: gmc-batch-2024-q4
+    severity: low
+    description: Placeholder source attribution replaced with actual provenance
+
+  - fingerprint: "See [API Reference](./api-reference.md)"
+    fix: "See the API reference in the repository documentation."
+    source: gmc-batch-2025-q1
+    severity: high
+    description: Broken cross-reference to non-existent api-reference.md file
+
+  - fingerprint: "## Steps\n## Outputs"
+    fix: "## Steps\n\n## Outputs"
+    source: gmc-batch-2024-q4
+    severity: low
+    description: Missing blank line between heading sections fails markdown lint
+
+  - fingerprint: "(v1.0.0+)"
+    fix: ""
+    source: gmc-batch-2025-q1
+    severity: low
+    description: Inline version stamp removed per documentation conventions
+
+  - fingerprint: "tier: gold"
+    fix: "tier: verified"
+    source: gmc-batch-2024-q4
+    severity: medium
+    description: Non-standard tier label replaced with canonical tier vocabulary
+
+  - fingerprint: "```javascript\nfetch('/api/skill"
+    fix: "```bash\nskf"
+    source: gmc-batch-2025-q1
+    severity: high
+    description: Hallucinated JavaScript fetch call replaced with CLI command
+
+  - fingerprint: "## References\n## Steps"
+    fix: "## Steps"
+    source: gmc-batch-2024-q4
+    severity: high
+    description: References section misplaced before Steps violates section ordering
+
+  - fingerprint: "source: (generated)"
+    fix: "source: compilation-output"
+    source: gmc-batch-2025-q1
+    severity: low
+    description: Vague generated marker replaced with specific compilation-output source
+
+  - fingerprint: "# Skill Name\n# Overview"
+    fix: "# Skill Name\n\n## Overview"
+    source: gmc-batch-2024-q4
+    severity: high
+    description: Duplicate H1 heading replaced with correct H2 for Overview section
+
+  - fingerprint: "[ref: SKILL-SPEC-2.0](./spec.md)"
+    fix: "See the skill specification."
+    source: gmc-batch-2025-q1
+    severity: medium
+    description: Broken spec reference link to non-existent file
+
+  - fingerprint: "version: 0.9-draft"
+    fix: "version: 1"
+    source: gmc-batch-2024-q4
+    severity: medium
+    description: Draft version string replaced with release version
+
+  - fingerprint: "\\bconfidence:\\s*(?:none|n/a|unset)\\b"
+    fix: "confidence: T1-inferred"
+    source: gmc-batch-2025-q1
+    severity: medium
+    description: Empty or null confidence values normalized to T1-inferred
+    regex: true
+
+  - fingerprint: "  - tool: compile-skill\n    endpoint: /compile"
+    fix: "  - tool: skf-compile\n    invocation: CLI"
+    source: gmc-batch-2024-q4
+    severity: high
+    description: Hallucinated tool entry with REST endpoint replaced with correct CLI tool
+
+  - fingerprint: "## setup\n"
+    fix: "## Setup\n"
+    source: gmc-batch-2025-q1
+    severity: low
+    description: Lowercase Setup heading fails skill-check validation
+
+  - fingerprint: "\\[citation needed\\]"
+    fix: ""
+    source: gmc-batch-2024-q4
+    severity: low
+    description: Wikipedia-style citation placeholder removed from compiled output
+    regex: true
+
+  - fingerprint: "Last updated: 2023"
+    fix: ""
+    source: gmc-batch-2025-q1
+    severity: low
+    description: Stale 2023 date stamp removed from compiled skill content
+
+  - fingerprint: "## Inputs\n## inputs"
+    fix: "## Inputs"
+    source: gmc-batch-2024-q4
+    severity: medium
+    description: Duplicate Inputs section with inconsistent casing collapsed
+
+  - fingerprint: "\\bsee also:\\s*\\[.*\\]\\(https?://internal\\..*\\)"
+    fix: ""
+    source: gmc-batch-2025-q1
+    severity: high
+    description: Internal-only URL references removed from public skill output
+    regex: true
+
+  - fingerprint: "provenance: []\n"
+    fix: "provenance:\n  - source: compilation-output\n    confidence: T1-inferred\n"
+    source: gmc-batch-2024-q4
+    severity: medium
+    description: Empty provenance array populated with minimal compilation metadata
+
+  - fingerprint: "## Steps\n\n\n\n## Outputs"
+    fix: "## Steps\n\n## Outputs"
+    source: gmc-batch-2025-q1
+    severity: low
+    description: Excessive blank lines between sections reduced to standard single blank
+
+  - fingerprint: "\\|\\s*Step\\s*\\|\\s*Status\\s*\\|\\n\\|[-\\s|]+\\|\\n(?=\\|\\s*Step)"
+    fix: ""
+    source: gmc-batch-2024-q4
+    severity: medium
+    description: Duplicated markdown table header removed from compiled output
+    regex: true

package/src/shared/data/language-corpora.json

@@ -0,0 +1,32 @@
+{
+  "_comment": "Canonical companion prose corpora for whole-language skills (issue #427). A language-reference repo (a compiler/interpreter such as rust-lang/rust) carries the language's CODE; its value as a skill comes from the language's PROSE — the guide/Book, the standard/library API docs, and idioms. README detection (skf-detect-docs.py) is the primary source; this registry guarantees the canonical corpora for well-known languages even when the repo's README does not link them. Keyed by lowercase language id (as emitted by skf-detect-language.py / step-auto-scope.md). URLs are version-agnostic, point at maintained latest-stable aliases, and were verified live. Consumed by skf-language-corpora.py, which emits the brief doc_urls contract {url, label, source} with source fixed to 'language-registry' (issue #432).",
+  "rust": [
+    { "url": "https://doc.rust-lang.org/book/", "label": "The Rust Programming Language (Book)" },
+    { "url": "https://doc.rust-lang.org/std/", "label": "Rust Standard Library" },
+    { "url": "https://doc.rust-lang.org/reference/", "label": "The Rust Reference" }
+  ],
+  "python": [
+    { "url": "https://docs.python.org/3/tutorial/", "label": "The Python Tutorial" },
+    { "url": "https://docs.python.org/3/library/", "label": "Python Standard Library" },
+    { "url": "https://docs.python.org/3/reference/", "label": "Python Language Reference" },
+    { "url": "https://docs.python.org/3/howto/", "label": "Python HOWTOs (idioms)" }
+  ],
+  "go": [
+    { "url": "https://go.dev/tour/", "label": "A Tour of Go" },
+    { "url": "https://go.dev/doc/effective_go", "label": "Effective Go" },
+    { "url": "https://go.dev/ref/spec", "label": "The Go Language Specification" },
+    { "url": "https://pkg.go.dev/std", "label": "Go Standard Library" }
+  ],
+  "typescript": [
+    { "url": "https://www.typescriptlang.org/docs/handbook/intro.html", "label": "TypeScript Handbook" },
+    { "url": "https://www.typescriptlang.org/docs/", "label": "TypeScript Documentation (Reference)" }
+  ],
+  "javascript": [
+    { "url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide", "label": "MDN JavaScript Guide" },
+    { "url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference", "label": "MDN JavaScript Reference" }
+  ],
+  "ruby": [
+    { "url": "https://www.ruby-lang.org/en/documentation/quickstart/", "label": "Ruby in Twenty Minutes" },
+    { "url": "https://docs.ruby-lang.org/en/master/", "label": "Ruby Core & Standard Library API" }
+  ]
+}

package/src/shared/references/pipeline-contracts.md

@@ -19,11 +19,15 @@ The forger also accepts common pipeline aliases:
 
 | Alias | Expands To | Description |
 |-------|-----------|-------------|
+| `forge-auto` | `AN[auto] BS[auto] CS TS[min:90] EX` | Zero-ceremony auto-compile pipeline (bare repo/doc URL → verified skill) |
 | `forge` | `BS CS TS EX` | Full skill creation pipeline (brief through export) |
 | `forge-quick` | `QS TS EX` | Quick skill pipeline |
-| `onboard` | `AN CS TS EX` | Full brownfield onboarding (AN generates briefs, CS consumes them directly) |
 | `maintain` | `AS US TS EX` | Maintenance cycle (audit → update → test → export) |
 
+**Deprecated alias:** `deepwiki` resolves to `forge-auto` (renamed to avoid collision with the DeepWiki MCP — the pipeline auto-forges a verified skill and does not call that MCP). It still works but emits a one-time deprecation notice.
+
+**Note:** `campaign` is a standalone workflow invoked via `@Ferris campaign`, not a pipeline alias. It orchestrates its own multi-stage pipeline internally with dependency tracking and resume.
+
 ## Pipeline Rules
 
 1. **Left to right execution** — each workflow completes before the next begins
@@ -33,12 +37,17 @@ The forger also accepts common pipeline aliases:
 5. **Error halts propagate** — if any workflow hard-halts, the pipeline stops immediately
 6. **Progress reporting** — the forger reports completion of each workflow before starting the next
 
+## Pipeline Arguments
+
+Pipeline-level arguments (e.g., `--pin <version>`) are passed to the first workflow's data context. The workflow decides how to consume them. For the `forge-auto` pipeline, `--pin` flows to AN, where `step-auto-scope.md §0b` uses it for pin resolution.
+
 ## Data Flow
 
 How outputs from one workflow become inputs to the next:
 
 | From | To | Data Passed | How |
 |------|-----|------------|-----|
+| AN | BS | `brief_path` from generated brief | Forger passes the `brief_path` from AN's output to BS[auto], which loads and enriches the brief |
 | AN | CS | `skill-brief.yaml` paths from generated briefs | Forger passes each `brief_path` written by AN to CS; in batch mode, CS processes all sequentially |
 | BS | CS | `skill-brief.yaml` path | Forger passes the brief path written by BS as `brief_path` to CS |
 | CS | TS | skill name (derived from brief) | Forger passes the `skill_name` from the completed CS to TS |
@@ -57,7 +66,7 @@ Circuit breakers halt the pipeline when a workflow's output doesn't meet a quali
 |----------|-------|-------------------|----------------|
 | AN | recommended units count | min: 1 | Zero skillable units found |
 | CS | compilation success | must complete | Hard error during compilation |
-| TS | completeness score | min: 60 | Score below threshold |
+| TS | completeness score | min: 60 (per-pipeline defaults apply — see init.md §1b) | Score below 80% floor (scores between 80% and per-pipeline threshold produce a fallback PASS with evidence report — pipeline continues) |
 | AS | drift score | not CRITICAL | Critical drift found |
 | VS | feasibility verdict | not BLOCKED | All integrations blocked |
 
@@ -68,6 +77,7 @@ Override syntax: `TS[min:80]` sets the test-skill threshold to 80 for this pipel
 Brackets after a workflow code (`CODE[value]`) are parsed as follows:
 
 - **Circuit breaker override**: `min:N` where N is a number — e.g., `TS[min:80]` sets the threshold for that workflow
+- **Mode flag**: `auto` — e.g., `AN[auto]` activates auto mode for that workflow. The workflow's first step reads the flag from pipeline data context and routes to the appropriate auto-mode step file.
 - **Target argument**: any other value — e.g., `CS[cocoindex]` passes "cocoindex" as the target to CS
 
 Only workflows with a circuit breaker entry (AN, CS, TS, AS, VS) accept `min:N` overrides. All other workflows ignore `min:N` brackets. Target arguments are valid for any workflow that accepts a named input (CS, QS, BS, US, etc.).
@@ -78,12 +88,14 @@ The forger tracks pipeline state in memory during execution:
 
 ```yaml
 pipeline:
+  alias: "forge"          # pipeline alias name, or null for ad-hoc sequences
   workflows: [AN, CS, TS, EX]
   current_index: 1
   completed:
     - {code: AN, status: ok, output: {units: 3, briefs: [...]}}
   pending: [CS, TS, EX]
   data:
+    pipeline_alias: "forge" # forwarded to each workflow's data context (consumed by TS init.md §1b for per-pipeline threshold lookup)
     skill_name: "cocoindex"
     brief_path: "/path/to/skill-brief.yaml"
     target: "cocoindex"