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

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

@@ -1,254 +0,0 @@
----
-name: 'step-06-validate'
-description: 'Validate compiled skill content against agentskills.io spec via skill-check'
-nextStepFile: './step-07-generate-artifacts.md'
----
-
-# Step 6: Validate
-
-## STEP GOAL:
-
-To validate the compiled SKILL.md content against the agentskills.io specification using skill-check, auto-fix any validation failures, and confirm spec compliance before artifact generation.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🎯 ALWAYS follow the exact instructions in the step file
-- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a tool you do not have access to, you MUST still achieve the outcome in your main context thread
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a skill compilation engine performing quality assurance
-- ✅ Validation ensures spec compliance — it does not modify content semantics
-- ✅ Tool unavailability means skip validation, not halt workflow
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on validating compiled content against spec
-- 🚫 FORBIDDEN to add new content — only fix spec compliance issues
-- 💾 Validation and auto-fix modify files in the staging directory (`_bmad-output/{name}/`)
-- 💬 If auto-fix fails, report issues clearly but proceed (warn, don't halt)
-- ⚙️ If skill-check unavailable: skip validation, add warning to evidence report
-- ⚠️ Ignore non-zero exit codes from `skill-check` if the JSON output shows 0 errors — parse JSON output, not exit codes
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow MANDATORY SEQUENCE exactly
-- 💾 Validation results are added to evidence-report content in context
-- 📖 Auto-fix pattern: validate → fix → re-validate (once)
-- 🚫 Maximum one auto-fix attempt per validation failure
-- ⏸️ **Conditional interaction:** If tessl returns suggestions (section 6b), halt for user input. Otherwise auto-proceed. This is a conditional gate step, not a pure auto-proceed step.
-
-## CONTEXT BOUNDARIES:
-
-- Available: All compiled content from step-05 (SKILL.md, metadata.json, etc.)
-- Focus: Spec compliance validation and auto-fix
-- Limits: Do NOT add new content or modify extraction data
-- Dependencies: Compiled content must exist from step-05
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-### 1. Check Tool Availability
-
-Run: `npx skill-check -h`
-
-- If succeeds: Continue to automated validation (section 2)
-- If fails: Perform manual fallback (section 3); add note to evidence-report: "Spec validation performed manually — skill-check tool unavailable"
-
-**Important:** Do not assume availability — empirical check required.
-
-### 2. Validate & Auto-Fix (skill-check check --fix)
-
-Run the external skill-check tool against the compiled skill staging directory:
-
-```bash
-npx skill-check check <staging-skill-dir> --fix --format json --no-security-scan
-```
-
-This performs frontmatter validation, description quality checks, body limit enforcement, local link resolution, file formatting, auto-fix of deterministic issues, and quality scoring (0-100) across five weighted categories.
-
-**Parse the JSON output** for: `qualityScore` (0-100), `diagnostics[]` (remaining issues), `fixed[]` (auto-corrected issues).
-
-**Context sync after --fix:** If `fixed[]` is non-empty (i.e., `--fix` modified files on disk), re-read the modified SKILL.md to update the in-context copy. Verify the re-read content matches expectations before proceeding. This prevents silent divergence between the in-context SKILL.md and the on-disk version that step-07 will use for artifact generation.
-
-**Description preservation after --fix:** After re-reading the modified SKILL.md, compare the frontmatter `description` field against the original step-05 compiled description. If `--fix` replaced the description with a generic or truncated version, restore the original description to the on-disk file and update the in-context copy. The step-05 compiled description is authoritative — auto-fix tools must not replace trigger-optimized descriptions.
-
-**Note:** `skill-check` may return non-zero exit code even when `errorCount` is 0. Always rely on parsed JSON, not the shell exit code.
-
-- **Score ≥ 70:** Record "Schema: PASS (score: {score}/100)" in evidence-report
-- **Score < 70:** Log remaining diagnostics as warnings, record "Schema: WARN — score {score}/100, {count} remaining issues", proceed
-- **Unfixable errors:** Record specific rule IDs and suggestions, proceed with warnings
-
-### 3. Validate Frontmatter (Fallback)
-
-**If skill-check was available:** Skip — already validated in step 2.
-
-**If skill-check NOT available (fallback):** Perform manual frontmatter compliance check:
-
-- [ ] Frontmatter present — file starts with `---` and has closing `---`
-- [ ] `name` field — present, non-empty, lowercase alphanumeric + hyphens only, 1-64 chars
-- [ ] `name` matches skill output directory name
-- [ ] `description` field — present, non-empty, 1-1024 characters
-- [ ] No unknown fields — only `name`, `description`, `license`, `compatibility`, `metadata`, `allowed-tools` permitted
-- [ ] `version` and `author` are NOT in frontmatter (they belong in metadata.json)
-
-If fails: auto-fix (deterministic), re-validate once, record result. If passes: record "Frontmatter: PASS".
-
-### 4. Split Oversized Body (if needed)
-
-**If step 2 reported `body.max_lines` failure:**
-
-**Description preservation:** Before any split operation, capture the current SKILL.md frontmatter `description` field. After the split completes, verify the `description` was not modified. If it was replaced with a generic placeholder, restore the original immediately.
-
-**Mandatory approach — selective split:** Identify Tier 2 sections by their `## Full` heading prefix (e.g., `## Full API Reference`, `## Full Type Definitions`, `## Full Integration Patterns`). Extract ONLY those sections to `references/`, starting with the largest. Keep ALL Tier 1 content and any smaller sections inline. Inline passive context achieves 100% task accuracy vs 79% for on-demand retrieval (per Vercel research).
-
-**FORBIDDEN:** Running `npx skill-check split-body --write` without prior selective extraction. The `split-body --write` command extracts ALL `##` sections top-to-bottom, destroying Tier 1 inline content that the two-tier design depends on. This command is a LAST RESORT only after selective split has been attempted and proven insufficient.
-
-**If selective split alone does not bring body under the limit** (rare — typically only occurs when Tier 1 itself exceeds 300 lines): reduce Tier 1 Key API Summary and Architecture at a Glance sections to fit within limits. Do NOT fall back to automated `split-body --write` to solve a Tier 1 sizing problem.
-
-**Tier 1 preservation check:** After ANY split operation, verify that ALL of the following sections remain inline in SKILL.md (not moved to references/): Overview, Quick Start, Common Workflows, Key API Summary, Migration & Deprecation Warnings (if present), Key Types, Architecture at a Glance, CLI (if present), Scripts & Assets (if present), Manual Sections. If any Tier 1 section was moved to references/, restore it immediately and re-split targeting only Tier 2 sections.
-
-**Anchor validation and remediation:** After any split, verify that context-snippet section anchors (`#quick-start`, `#key-types`) still resolve to headings in SKILL.md. If an anchor no longer resolves (section was split out), restore that section to SKILL.md inline content — the context-snippet must always reference sections that exist in the main file.
-
-Then re-validate: `npx skill-check check <staging-skill-dir> --format json --no-security-scan`
-
-**If skill-check unavailable or no body size issue:** Skip.
-
-### 5. Security Scan
-
-**If skill-check available:**
-
-```bash
-npx skill-check check <staging-skill-dir> --format json
-```
-
-(Security scan enabled by default when `--no-security-scan` omitted. The scan uses [Snyk Agent Scan](https://github.com/snyk/agent-scan) to check for prompt injection risks, sensitive data exposure, and unsafe tool permissions.)
-
-Record any security warnings in evidence-report. Security findings are advisory — they do not block artifact generation. If the full validation re-run produces a different quality score than section 2, update the evidence-report with the newer score.
-
-**If security scan fails due to missing SNYK_TOKEN:**
-
-Display: "Security scan requires a Snyk Enterprise API token ([docs](https://docs.snyk.io/snyk-api/authentication-for-api)). Set `SNYK_TOKEN=your-token` in environment or `.env`, then re-run [SF] Setup Forge. Without Enterprise, use `--no-security-scan` to skip. Security scanning is optional and does not block skill compilation."
-
-Record: "Security scan skipped — SNYK_TOKEN not configured"
-
-**If skill-check unavailable:** Skip with note: "Security scan skipped — skill-check tool unavailable"
-
-### 6. Content Quality Review (tessl)
-
-**If tessl available**, run: `npx -y tessl skill review <staging-skill-dir>`
-
-Parse output for: `description_score`, `content_score`, `average_score`, `validation_result`, `judge_suggestions[]`.
-
-- **Content score < 70%:** Record warning: "Content quality warning: tessl scored content at {score}%."
-- **Unavailable:** Skip with note: "Content quality review skipped — tessl tool unavailable"
-
-> **EXPECTED BEHAVIOR — Two-Tier Scoring:** The Skill Forge two-tier design (Tier 1 Key API Summary + Tier 2 Full API Reference) intentionally includes progressive disclosure. tessl's `conciseness` scorer will flag this as redundancy (typically scoring 2/3), which is **expected behavior — not a defect**. tessl may also suggest removing `[MANUAL]` markers, moving Full API Reference to a separate file, or consolidating duplicate parameter documentation — **all three suggestions conflict with SKF design principles and must be dismissed.** Acceptable threshold: content scores >= 60% are normal for two-tier skills. Do NOT consolidate Tier 1 and Tier 2 content to improve the score — the two-tier structure is a deliberate design choice for standalone usability.
-
-tessl installs automatically via `npx`. A missing tool is not an error — graceful skip.
-
-#### 6b. User Decision Gate (conditional)
-
-**If tessl returned no suggestions OR tessl was unavailable:** Skip this gate — auto-proceed.
-
-**If tessl returned suggestions**, present them to the user:
-
-"**Content quality review: {score}%**
-
-tessl suggestions:
-{numbered list of judge_suggestions}
-
-**Select an option:**
-- **[S] Skip** — proceed with current content as-is (default)
-- **[A] Apply structural fixes** — apply only structural suggestions (split sections, consolidate duplicates). No new content generated.
-- **[R] Review all** — show each suggestion with proposed changes before applying"
-
-#### Gate Rules:
-
-- **Structural suggestions** (split reference section, consolidate duplicates, reorder sections) can be applied without zero-hallucination risk — they restructure existing content
-- **Semantic suggestions** (add examples, add error handling, add validation checkpoints) introduce content not verified from source code. If the user chooses to apply these:
-  - Warn: "This adds content not verified from source code."
-  - Mark applied content with `<!-- [TESSL:auto-fix] -->` markers
-  - Cite as `[TESSL:suggestion]` in the provenance map with `confidence: "TESSL"` (below T3)
-  - Record in evidence report: "TESSL-suggested content applied: {count} items (unverified)"
-- **If user selects [S]:** Record "tessl suggestions: skipped by user" in evidence report. Proceed to section 7.
-- **If user selects [A]:** Apply structural fixes only, re-run tessl to capture updated score, record results. Proceed to section 7.
-- **If user selects [R]:** Show each suggestion with the proposed change. For each, user confirms or skips. Apply confirmed changes, record results. Proceed to section 7.
-
-### 7. Validate metadata.json
-
-Cross-check metadata.json against extraction inventory:
-- `stats.exports_documented` / `stats.exports_public_api` / `stats.exports_internal` / `stats.exports_total` are accurate
-- `stats.public_api_coverage` and `stats.total_coverage` are correctly computed (null when denominator is 0)
-- `confidence_distribution.t1`, `confidence_distribution.t1_low`, `confidence_distribution.t2`, `confidence_distribution.t3` match actual counts
-- `spec_version` is "1.3"
-- If `scripts[]` or `assets[]` arrays present: verify `stats.scripts_count`/`stats.assets_count` match array lengths; verify `file_entries` count in provenance-map.json matches
-
-Auto-fix any discrepancies (these are computed values).
-
-### 8. Update Evidence Report
-
-Add validation results to evidence-report content in context:
-
-```markdown
-## Validation Results
-- Schema: {pass/fail} (quality score: {score}/100)
-- Frontmatter: {pass/fail}
-- Body: {pass/fail} {split-body applied if applicable}
-- Security: {pass/warn/skipped}
-- Content Quality (tessl): {pass/warn/skipped} (score: {score}%)
-- Metadata: {pass/fail}
-
-## Quality Score Breakdown
-- Frontmatter (30%): {score} | Description (30%): {score} | Body (20%): {score} | Links (10%): {score} | File (10%): {score}
-
-## Auto-Fixed Issues
-- {list of issues automatically corrected by --fix}
-
-## Remaining Warnings / Security Findings / Content Quality (tessl)
-- {warnings, security results, tessl scores and suggestions — or "skipped"}
-```
-
-### 9. Menu Handling Logic
-
-**Conditional interaction step.** If tessl produced suggestions, section 6b halts for user input. Otherwise, auto-proceed.
-
-After validation completes (including any user decisions from section 6b), immediately load, read entire file, then execute `{nextStepFile}`.
-
-- Tool unavailability is a skip, not a halt
-- Validation failures are warnings — proceed to artifact generation
-- tessl gate only triggers when suggestions exist — no gate for clean reviews or unavailable tools
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN validation is complete (or skipped) and evidence-report content is updated will you proceed to load `{nextStepFile}` for artifact generation.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- `npx skill-check check --fix --format json` executed (or skipped with warning if unavailable)
-- Quality score captured and recorded; auto-fix applied for deterministic issues
-- Split-body applied if `body.max_lines` failed; security scan executed (or skipped with warning)
-- `npx -y tessl skill review` executed (or skipped); content quality warning raised if score < 70%
-- tessl suggestions presented to user when available; user decision recorded
-- TESSL-applied content marked with `<!-- [TESSL:auto-fix] -->` and cited as `[TESSL:suggestion]`
-- Metadata cross-check performed; evidence report updated with structured results
-- Proceeded to step-07 (auto or after user gate)
-
-### ❌ SYSTEM FAILURE:
-
-- Halting on validation failure or skill-check unavailability (should warn and proceed)
-- Adding new content during validation without user approval via the tessl gate
-- Applying semantic tessl suggestions without warning the user about unverified content
-- Not recording quality score; skipping security scan without recording the skip
-- Attempting more than one auto-fix cycle per failure
-
-**Master Rule:** Validation informs, it does not block. Record results, fix what's deterministic, scan for security issues, warn about the rest, and proceed.

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

@@ -1,179 +0,0 @@
----
-name: 'step-08-report'
-description: 'Display compilation summary with confidence tiers, suggest next steps'
-nextStepFile: '../../shared/health-check.md'
----
-
-# Step 8: Report
-
-## STEP GOAL:
-
-To display the final compilation summary — skill name, version, source, export count, confidence distribution, tier used, file list, and any warnings — and suggest next steps for the user.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🎯 ALWAYS follow the exact instructions in the step file
-- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a tool you do not have access to, you MUST still achieve the outcome in your main context thread
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a skill compilation engine delivering the final report
-- ✅ This is the completion step — celebrate the forged skill
-- ✅ Positive capability framing — describe what was achieved
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on reporting compilation results
-- 🚫 FORBIDDEN to modify any files — reporting only
-- 🚫 FORBIDDEN to re-run extraction or compilation
-- 💬 Deliver structured report with confidence breakdown
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow MANDATORY SEQUENCE exactly
-- 💾 No file operations — display only
-- 📖 This is the final step — no next step to load
-- 🚫 Do not modify any output files
-
-## CONTEXT BOUNDARIES:
-
-- Available: All data from previous steps — brief, extraction, enrichment, compilation, validation, artifacts
-- Focus: Summarizing and reporting
-- Limits: Do NOT modify files or re-run any previous step
-- Dependencies: All artifacts must have been generated in step-07
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-### 1. Display Forge Completion Banner
-
-"**Skill forged: {name} v{version} — {export_count} functions, {primary_confidence} confidence.**"
-
-Where `{primary_confidence}` is the predominant confidence tier (T1 if Forge/Deep, T1-low if Quick).
-
-### 2. Display Compilation Summary
-
-"**Compilation Summary**
-
-| Field | Value |
-|-------|-------|
-| **Skill** | {name} v{version} |
-| **Source** | {source_repo} @ {branch} ({commit_short}) |
-| **Language** | {language} |
-| **Forge Tier** | {tier} — {tier_description} |
-| **Files Scanned** | {file_count} |
-| **Exports Documented** | {documented_count} public API ({public_api_coverage}%) / {total_count} total ({total_coverage}%) |
-
-**Confidence Distribution:**
-| Tier | Count | Description |
-|------|-------|-------------|
-| T1 (AST) | {t1_count} | Structurally verified via ast-grep |
-| T1-low (Source) | {t1_low_count} | Inferred from source reading |
-| T2 (QMD) | {t2_count} | QMD-enriched semantic context |
-| T3 (External) | {t3_count} | Sourced from external documentation URLs |
-
-**Output Files:**
-- `{skill_package}/SKILL.md` — Active skill with trigger-based usage
-- `{skill_package}/context-snippet.md` — Passive context snippet (used by export-skill)
-- `{skill_package}/metadata.json` — Machine-readable birth certificate
-- `{skill_package}/references/` — Progressive disclosure ({ref_count} files)
-- `{forge_version}/provenance-map.json` — Source map with AST bindings
-- `{forge_version}/evidence-report.md` — Build audit trail
-- `{forge_version}/extraction-rules.yaml` — Reproducible extraction schema
-- `{skill_group}/active` -> `{version}` — Symlink to current version"
-
-### 3. Display Warnings (If Any)
-
-If there were warnings from extraction, validation, or enrichment, display them:
-
-"**Warnings:**
-- {warning_1}
-- {warning_2}
-- ..."
-
-If no warnings, omit this section entirely.
-
-### 4. Suggest Next Steps
-
-"**Recommended next steps:**
-- **[TS] Test Skill** — verify completeness and accuracy before export
-- **[EX] Export Skill** — publish to your skill library or agentskills.io
-- **[US] Update Skill** — edit specific sections or add manual content
-
-To use this skill immediately, add the context snippet to your CLAUDE.md:
-```
-{context_snippet_content}
-```"
-
-### 5. Batch Mode Status (If Applicable)
-
-**If running in --batch mode:**
-
-"**Batch progress:** {completed_count} of {total_count} skills compiled.
-
-{If more remaining:} Proceeding to next brief: {next_skill_name}..."
-
-Update the batch checkpoint in `{sidecar_path}/batch-state.yaml` with:
-
-```yaml
-batch_active: true
-brief_list: [{full list of brief paths}]
-current_index: {index of next brief to process, 0-based}
-completed: [{list of completed skill names}]
-last_updated: {ISO timestamp}
-```
-
-Then loop back to step-01 for the next brief. Step-01 detects an active batch via `batch-state.yaml` and loads the brief at `current_index`.
-
-**If all batch briefs complete:**
-
-Set `batch_active: false` in `{sidecar_path}/batch-state.yaml` to prevent stale state. Display: "Batch complete. {completed_count} skills compiled."
-
-**If not batch mode:**
-
-End workflow. No further steps.
-
-### 6. Workflow Health Check
-
-**If not batch mode (or all batch briefs complete):**
-
-Load and execute `{nextStepFile}` for workflow self-improvement check.
-
-**If batch mode with remaining briefs:** Skip health check — loop back to step-01 for the next brief. Health check runs after the final brief in the batch.
-
-## CRITICAL STEP COMPLETION NOTE
-
-This step chains to the shared health check (unless batch mode loops back to step-01). After the health check completes, the create-skill workflow is fully done.
-
-For batch mode: loop back to step-01 for remaining briefs via sidecar checkpoint. Health check runs only after the last brief.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Forge completion banner displayed with skill name, version, export count
-- Full compilation summary with confidence distribution
-- All output file paths listed
-- Warnings displayed (if any)
-- Next steps suggested (test-skill, export-skill, update-skill)
-- Context snippet provided for immediate use
-- Batch progress updated (if applicable)
-- Workflow ended gracefully
-
-### ❌ SYSTEM FAILURE:
-
-- Not displaying the forge completion banner
-- Missing confidence distribution in summary
-- Modifying any files during the report step
-- Not listing all output file paths
-- Not suggesting next steps
-- Not ending the workflow (attempting to load nonexistent next step)
-
-**Master Rule:** This step reports and celebrates. It does not modify, re-extract, or re-compile. The skill is forged.

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

@@ -1,53 +0,0 @@
----
-name: create-skill
-description: Compile a skill from a brief. Supports --batch for multiple briefs.
-web_bundle: true
-installed_path: '{project-root}/_bmad/skf/workflows/skillforge/create-skill'
----
-
-# Create Skill
-
-**Goal:** Compile a verified agent skill from a skill-brief.yaml and source code, producing an agentskills.io-compliant SKILL.md with provenance map, evidence report, and progressive disclosure references.
-
-**Your Role:** You are operating in **Ferris Architect mode** — a skill compilation engine performing structural extraction and assembly. This workflow is mostly autonomous with three interaction points — one after ecosystem check (if a match is found), one after source extraction (to confirm findings before compilation), and one after content quality review (when tessl produces suggestions). All other steps auto-proceed. Apply zero hallucination tolerance: every instruction in the output must trace to source code with a confidence tier citation.
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere to 1 file as directed at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **Tier-Aware Execution**: Steps adapt behavior based on forge tier (Quick/Forge/Forge+/Deep) loaded from sidecar at init
-- **Zero Hallucination**: Every claim requires a provenance citation — uncitable content is excluded, not guessed
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: At confirmation gates (steps 02 and 03), halt and wait for user selection
-4. **AUTO-PROCEED**: All other steps proceed to the next automatically after completion
-5. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- 📋 **NEVER** create mental todo lists from future steps
-- ⚒️ **NEVER** include content in SKILL.md that cannot be cited to source code
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Module Configuration Loading
-
-Load and read full config from {project-root}/_bmad/skf/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `sidecar_path`, `skills_output_folder`, `forge_data_folder`
-
-### 2. First Step Execution
-
-Load, read the full file and then execute ./steps-c/step-01-load-brief.md to begin the workflow.