authoring

Bundles Forge

中文

A toolkit for building bundle-plugins — AI coding plugins organized around collaborative skill workflows — across Claude Code, Cursor, Codex, OpenCode, Gemini CLI, and OpenClaw.

What is a Bundle-Plugin?

A single skill (SKILL.md) does one thing — an AI agent discovers it by its description field and loads it on demand. A bundle-plugin takes this further: multiple skills reference each other and form a workflow, where one skill's output feeds the next.

graph LR
    A["Skill A"] -->|output feeds| B["Skill B"]
    B -->|output feeds| C["Skill C"]
    C -->|validates| A

bundles-forge itself is a bundle-plugin — blueprinting produces a design, scaffolding generates a project from it, auditing validates the result, and optimizing iterates on issues found.

If your plugin has 3+ skills that form a workflow, you're building a bundle-plugin. This toolkit gives you scaffolding, quality gates, and multi-platform publishing for that pattern.

Quick Start

Install (Claude Code)

1. Add the marketplace:

   /plugin marketplace add OdradekAI/bundles-forge
   

2. Install the plugin:

   /plugin install bundles-forge@bundles-forge-dev
   

Or clone locally for development:

git clone https://github.com/OdradekAI/bundles-forge.git
cd bundles-forge

# Add your local marketplace
/plugin marketplace add ./

# Install the plugin
/plugin install bundles-forge@bundles-forge-dev

Other platforms: see Platform Support below.

Path A: Build a New Bundle-Plugin

bundles-forge:blueprinting

This starts a structured interview to design your project — scope, platform targets, skill decomposition. When the design is ready, the agent automatically chains into scaffolding (project generation) and then authoring (SKILL.md writing).

Path B: Audit an Existing Project

cd your-bundle-plugin-project
bundles-forge:auditing

Runs a 10-category quality assessment with pattern-based security checks across 7 file categories.

Concepts

Full explanations, design decisions, and architecture diagrams → Concepts Guide

Skills

The 8 skills cover the full lifecycle of a bundle-plugin project, organized into two layers:

• Orchestrators (blueprinting, optimizing, releasing) — diagnose, decide, and delegate. They chain multiple skills together to accomplish multi-step goals.
• Executors (scaffolding, authoring, auditing, testing) — single-responsibility workers. They can be invoked directly by users or dispatched by orchestrators.

flowchart LR
    Design["blueprinting"] --> Scaffold["scaffolding"]
    Design -->|"content authoring"| Write["authoring"]
    Design -->|"initial audit"| Audit["auditing"]
    Audit -->|issues| Optimize["optimizing"]
    Optimize -->|"delegate changes"| Write
    Optimize --> Audit
    Audit -->|pass| Test["testing"]
    Test -->|pass| Release["releasing"]

The bootstrap meta-skill using-bundles-forge provides a lightweight session prompt via hooks and full routing context on demand via the Skill tool.

Standalone use: authoring, auditing, and optimizing can be invoked independently on any existing project without going through the full lifecycle.

Guides

Each skill has a companion guide in docs/ with detailed usage, examples, and design rationale:

Agents

Invoking Skills

Skills are invoked automatically (the agent matches user intent to the skill's description field) or explicitly via bundles-forge:<skill-name> references — for example, bundles-forge:auditing or bundles-forge:blueprinting.

Auditing

Both auditing and optimizing accept local paths, GitHub URLs, and zip/tar.gz archives as input — the agent normalizes the target automatically.

Four audit scopes for different levels of granularity — the agent auto-detects scope from the target path:

Quick Start (Scripts)

bundles-forge audit-plugin .                                      # full project audit
bundles-forge audit-skill skills/authoring                         # sin