| name | swarm-coding-skill |
| description | Autonomous multi-agent code generation. Planner creates manifest, specialized roles execute tasks. Generates complete projects with tests, Docker, CI, and decision logs. |
| requiredEnv | ["OPENROUTER_API_KEY"] |
| optionalEnv | ["OPENROUTER_MODEL","MOCK"] |
| warnings | ["Writes to parent workspace (swarm-projects/, .learnings/). Run in isolated workspace.","Stores prompts and agent reasoning in DECISIONS.md and .learnings/. Do not include sensitive data.","Auto-includes Privy/web3 auth when prompts mention blockchain. Review generated code."] |
| autonomy | orchestrator-driven-code-generation |
| outputPaths | ["swarm-projects/{timestamp}/",".learnings/","DECISIONS.md","SWARM_SUMMARY.md"] |
| externalServices | [{"name":"OpenRouter","purpose":"LLM inference for planning and code generation","scope":"API key sent with requests"}] |
| capabilities | ["code-generation","multi-agent-orchestration","project-scaffolding","docker-ci","testing","knowledge-grounded-decisions","continuous-improvement"] |
Swarm Coding Skill
Fully autonomous multi-agent software development. Given a plain-English prompt, the swarm designs, implements, tests, and delivers a complete project end-to-end.
Core capability: Code generation via OpenRouter's qwen3-coder model. The orchestrator drives a Planner to create a manifest, then executes specialized worker roles (BackendDev, FrontendDev, QA, DevOps, etc.) in dependency order. All code is written to files; no interactive sessions.
Important: This skill generates code for review and deployment by the user. It does not make business decisions or operate autonomously in production. The user remains responsible for security, compliance, and operational decisions.
How It Works
- Orchestrator (
Planner role) analyzes your prompt, decides tech stack and architecture, and creates a swarm.yaml manifest with tasks and dependencies.
- Worker agents (
BackendDev, FrontendDev, QA, DevOps) are spawned as sub-sessions. Each has a clear persona and works on its assigned files in a shared workspace.
- Coordination: The orchestrator tracks task completion and dependencies. When a task finishes, it marks it done and starts any unblocked downstream tasks.
- Conflict avoidance: Files are partitioned by role (Backend owns
server/, Frontend owns client/, etc.). If two roles need the same file, the manifest assigns an owner.
- Quality gates: QA must pass tests before integration; DevOps ensures containerization; no merge without green tests.
- Deliverable: You get a complete project directory with README, tests, Dockerfile, and optionally a GitHub repo or zip.
Usage
/trigger swarm-code "Build a dashboard that shows Moltbook stats and ClawCredit status"
The skill will:
- Spawn the orchestrator in an isolated session
- Orchestrator spawns workers sequentially or in parallel (based on dependencies)
- Output a final summary and path to the completed project
Requirements
- Node.js v18+
- Environment variables (in
.env at workspace root):
