Distribution Strategy

Distribution Strategy

Cool Workflow should be MCP-first, CLI-backed, skill-packaged, and runtime-compatible.

The universal product is not the skill file.

The universal product is:

workflow engine + CLI + MCP server + adapter manifests

Skills are distribution wrappers. They teach an agent host when and how to use CW, but they should not own core workflow logic.

Architecture Boundary

Do not let core logic grow inside one platform's skill, plugin, app wrapper, or manifest.

Core logic should stay in:

• the workflow engine
• the CLI
• the MCP server

Claude, Codex, Cursor, VS Code, Windsurf, and ChatGPT-style apps should be front doors into the same runtime.

Layers

cool-workflow runtime
  TypeScript workflow engine
  state machine
  pipeline contracts
  verifier gates
  scheduler

CLI
  list / plan / dispatch / result / report / schedule / routine

MCP
  tools
  resources
  prompts

skills and adapters
  Codex plugin
  Claude skill
  Cursor / VS Code / Windsurf MCP config
  future app wrappers

CLI As Baseline

Every serious coding agent can run shell commands.

node scripts/cw.js list
node scripts/cw.js plan architecture-review --repo /path/to/repo --question "Is this architecture sound?"
node scripts/cw.js dispatch <run-id> --limit 6
node scripts/cw.js report <run-id>

MCP As Cross-App Protocol

MCP should remain the main structured integration surface:

• tools for actions
• resources for run state and reports
• prompts for reusable workflow entry points

Runtime Target

CW is Node-compatible TypeScript compiled to CommonJS runtime JavaScript.

Bun can be supported as a fast development/runtime option, but CW should not be Bun-only while broad host compatibility is the goal.

Product Principle

One kernel.
Many front doors.
No duplicated workflow logic.