armelhbobdad/oh-my-skills / .claude/skills/skf-campaign
skf-campaign
VerifiedCampaign orchestration — multi-library skill production with dependency tracking, file-based state, and resume. Use when the user asks to "run a campaign" or "orchestrate skills."
templates/campaign-brief-template.yaml
View on GitHub# Machine-generated campaign brief: resume context for fresh sessions
# Written by campaign-state.py init from the parsed targets
# Campaign identifier
campaign_name: ""
# ISO-8601 timestamp of campaign creation
created_at: ""
# Target skills for this campaign run
targets: []
# Each target entry:
# name: ""
# repo_url: ""
# tier: "A" # A (full pipeline) or B (batch)
# pin: null # version pin, or null for latest
# depends_on: [] # list of skill names this target depends on
# plus any other field the target's source gave it, such as a language or
# scope hint
# Quality thresholds applied to all skills in this campaign
quality_gate:
hard: "zero-critical-high"
soft_target: 90
soft_fallback: 80
# Optional path to the architecture document the verify (Stage 7) and refine
# (Stage 8) stages consume. Empty string means those stages discover it at
# runtime (docs/architecture.md, then _bmad-output/planning-artifacts/architecture.md).
architecture_doc_path: ""
# Operator-provided context or directives for this campaign
notes: ""
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |