skf-campaign

Orchestrate multi-skill SKF pipelines with durable state and machine-readable outputs.

91|9|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/armelhbobdad/bmad-module-skill-forge --skill skf-campaign
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skf-campaign
Source: https://github.com/armelhbobdad/bmad-module-skill-forge/tree/main/src/skf-campaign
Command: npx skills add https://github.com/armelhbobdad/bmad-module-skill-forge --skill skf-campaign

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, jsonschema, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Campaign orchestration coordinates end-to-end skill pipelines across multiple libraries, managing dependencies, and preserving state for reliable resume after interruptions.

Core Features & Use Cases

  • Dependency-aware planning and execution order for multi-skill campaigns.
  • Durable, file-based state so progress survives context death and re-entry.
  • Full SKF pipeline orchestration (brief, generate, compile, test, export) across multiple skills.
  • Headless mode and machine-readable outputs for automated workflows.
  • Use cases include coordinating complex cross-library campaigns and producing an actionable campaign summary.

Quick Start

Launch a campaign by providing either a campaign brief or a manifest to seed targets, and SKF will orchestrate all stages end-to-end.

Frequently Asked Questions about skf-campaign

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate workflow orchestration across multiple libraries with resumable state?

Workflow orchestration across multiple libraries is automated by coordinating end-to-end skill pipelines and preserving file-based state. This approach manages dependencies and persists progress to enable reliable resume after interruptions.

What is the best way to manage dependencies in a multi-step automation campaign?

Dependency management in an automation campaign is handled through dependency-aware planning that determines the execution order for multi-skill pipelines. This ensures steps are sequenced safely and deterministically across all targeted libraries.

How do I resume an interrupted pipeline without losing previous progress?

You resume an interrupted pipeline by relying on durable, file-based state management that survives context death and re-entry. The orchestration workflow persists progress automatically, allowing the pipeline to continue safely from the last completed step.

Can I run headless automation and get machine-readable results for downstream tooling?

Headless automation is fully supported and emits machine-readable outputs for downstream tooling. The orchestration validates pins and provenance while executing the pipeline, producing deterministic results suitable for automated workflows.

Do I need a manifest to start coordinating cross-library campaigns?

You do not strictly need a manifest to start coordinating cross-library campaigns. You can launch the orchestration by providing either a campaign brief or a manifest to seed targets, and the workflow will orchestrate all stages end-to-end.