Setup Forge
Overview
Initializes the forge environment by detecting available tools, determining the capability tier (Quick/Forge/Forge+/Deep), writing persistent configuration, and optionally indexing the project for deep search. This is a fully autonomous workflow — no user interaction is required during execution.
Role
You are a system executor performing environment resolution. Run each step in sequence, write configuration files, and report results at completion.
Workflow Rules
These rules apply to every step in this workflow:
- Fully autonomous — all steps auto-proceed with no user interaction until the final report
- Read each step file completely before taking any action
- Follow the mandatory sequence in each step exactly — do not skip, reorder, or optimize
- Only load one step file at a time — never preload future steps
- Always communicate in
{communication_language}
- If
{headless_mode} is true, auto-proceed through confirmation gates with their default action and log each auto-decision
Stages
| # |
Step |
File |
Auto-proceed |
| 1 |
Detect Tools & Set Tier |
steps-c/step-01-detect-and-tier.md |
Yes |
| 1b |
CCC Index |
steps-c/step-01b-ccc-index.md |
Yes |
| 2 |
Write Config |
steps-c/step-02-write-config.md |
Yes |
| 3 |
QMD Hygiene |
steps-c/step-03-auto-index.md |
Yes |
| 4 |
Report |
steps-c/step-04-report.md |
Yes |
| 5 |
Workflow Health Check |
steps-c/step-05-health-check.md |
Yes |
Invocation Contract
| Aspect |
Detail |
| Inputs |
(none — fully autonomous) |
| Gates |
One optional: orphaned QMD collection removal (step 3, Deep tier only; default: Keep) |
| Outputs |
forge-tier.yaml, preferences.yaml, forge-data directories |
| Headless |
All gates auto-resolve with default action when {headless_mode} is true |
On Activation
Load config from {project-root}/_bmad/skf/config.yaml and resolve:
project_name (from installer-generated config.yaml, not module.yaml), output_folder, user_name, communication_language, document_output_languageskills_output_folder, forge_data_folder, sidecar_path
Resolve {headless_mode}: true if --headless or -H was passed as an argument, or if headless_mode: true in preferences.yaml. Default: false.
Load, read the full file, and then execute ./steps-c/step-01-detect-and-tier.md to begin the workflow.
1---2name: skf-setup3description: Initialize forge environment, detect tools, and set capability tier (Quick/Forge/Forge+/Deep). Use when the user requests to "set up" or "initialize the forge."4---56# Setup Forge78## Overview910Initializes the forge environment by detecting available tools, determining the capability tier (Quick/Forge/Forge+/Deep), writing persistent configuration, and optionally indexing the project for deep search. This is a fully autonomous workflow — no user interaction is required during execution.1112## Role1314You are a system executor performing environment resolution. Run each step in sequence, write configuration files, and report results at completion.1516## Workflow Rules1718These rules apply to every step in this workflow:1920- Fully autonomous — all steps auto-proceed with no user interaction until the final report21- Read each step file completely before taking any action22- Follow the mandatory sequence in each step exactly — do not skip, reorder, or optimize23- Only load one step file at a time — never preload future steps24- Always communicate in `{communication_language}`25- If `{headless_mode}` is true, auto-proceed through confirmation gates with their default action and log each auto-decision2627## Stages2829| # | Step | File | Auto-proceed |30|---|------|------|--------------|31| 1 | Detect Tools & Set Tier | steps-c/step-01-detect-and-tier.md | Yes |32| 1b | CCC Index | steps-c/step-01b-ccc-index.md | Yes |33| 2 | Write Config | steps-c/step-02-write-config.md | Yes |34| 3 | QMD Hygiene | steps-c/step-03-auto-index.md | Yes |35| 4 | Report | steps-c/step-04-report.md | Yes |36| 5 | Workflow Health Check | steps-c/step-05-health-check.md | Yes |3738## Invocation Contract3940| Aspect | Detail |41|--------|--------|42| **Inputs** | (none — fully autonomous) |43| **Gates** | One optional: orphaned QMD collection removal (step 3, Deep tier only; default: Keep) |44| **Outputs** | forge-tier.yaml, preferences.yaml, forge-data directories |45| **Headless** | All gates auto-resolve with default action when `{headless_mode}` is true |4647## On Activation48491. Load config from `{project-root}/_bmad/skf/config.yaml` and resolve:50 - `project_name` (from installer-generated config.yaml, not module.yaml), `output_folder`, `user_name`, `communication_language`, `document_output_language`51 - `skills_output_folder`, `forge_data_folder`, `sidecar_path`52532. **Resolve `{headless_mode}`**: true if `--headless` or `-H` was passed as an argument, or if `headless_mode: true` in preferences.yaml. Default: false.54553. Load, read the full file, and then execute `./steps-c/step-01-detect-and-tier.md` to begin the workflow.
armelhbobdad