system-forge
/system-forge
Design a multi-capability system as a swarm, vertical, or plugin; compile it only when a Foundry runtime is available. Use when several skills or agents need explicit topology, shared state, conflict resolution, termination, deployment adapters, and cross-surface packaging.
- Author
- frankxai ↗
- Repository
- starlight-intelligence-system ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design a multi-capability system as a swarm, vertical, or plugin; compile it only when a Foundry runtime is available. Use when several skills or agents need explicit topology, shared state, conflict resolution, termination, deployment adapters, and cross-surface packaging.
Original author description
Design a multi-capability system as a swarm, vertical, or plugin; compile it only when a Foundry runtime is available. Use when several skills or agents need explicit topology, shared state, conflict resolution, termination, deployment adapters, and cross-surface packaging.
How it works
- Outcome
- Choose the smallest system shape
- Procedure
- Plugin rule
- Quality gates
- Return
SKILL.md preview
---
name: system-forge
description: Design a multi-capability system as a swarm, vertical, or plugin; compile it only when a Foundry runtime is available. Use when several skills or agents need explicit topology, shared state, conflict resolution, termination, deployment adapters, and cross-surface packaging.
---
# System Forge
## Outcome
Design a bounded system whose topology, authority, shared state, and proof obligations are visible before execution, then compile it when a Foundry runtime is present.
## Choose the smallest system shape
- **Skill composition:** one actor can perform the work sequentially.
- **Swarm:** independent or specialized workers need explicit coordination.
- **Vertical:** domain rules, audiences, taste, and evaluation recur across several capabilities.
- **Plugin:** a set of validated skills and optional MCP connectivity must be distributed to ChatGPT and Codex.
Do not create a swarm merely to make a workflow sound advanced. Parallelism is justified only for genuinely separable work, independent evaluation, latency reduction, or permission isolation.
## Procedure
1. Start with a Task Envelope.
- Include deliverables, stakes, autonomy, capability selection, permissions, required evidence lanes, and deployment targets.
2. Resolve capabilities.
- Prefer registered skills and agents.
- Treat lexical graph suggestions as discovery hints, never silent routing decisions.
3. Choose topology.
- `manager-workers`: one owner decomposes and synthesizes.
- `handoff`: ownership moves between specialists.
- `agents-as-tools`: one agent retains control and invokes bounded specialists.
- `parallel-merge`: separable outputs join under a deterministic merge.
- `debate-synthesize`: independent hypotheses are judged and synthesized.
4. Define authority and state.
- Give every role non-overlapping decision rights.
- Choose manager-only, append-only, or partitioned shared-state writes.
- Name the conflict owner and evidence-based resolution method.
5. Define termination before dispatch.
- Write success conditions, stop conditions, maximum rounds, cost or latency ceilings, and escalation points.
6. Keep builder, critic, and verifier separate when stakes or ambiguity justify it.
7. Select the execution mode.
- **Foundry runtime available:** only when `tools/foundry/cli.mjs` and `foundry/contracts/` exist in the current workspace, compile the appropriate pack:
```bash
node tools/foundry/cli.mjs forge \
--envelope <task-envelope.json> \
--pack <swarm-pack.json|vertical-pack.json|plugin-pack.json> \
--out <package-directory>
```
- **Portable skills-only install:** read `references/portable-contracts.md`, then author the Task Envelope and chosen pack with those field names. Mark compilation and proof `pending-runtime`; do not invent emitted host artifacts or an Evidence Receipt. Provide the command above as an optional handoff for a later SIS workspace run.
8. Prove static structure before live orchestration.
- Validate topology, capabilities, permissions, state policy, termination, and plugin shape.
- Run behavioral and economic lanes before increasing autonomy or fan-out.
## Plugin rule
A skills-only plugin is a valid first release. Add an MCP server only when a real deployed endpoint, authentication model, privacy contract, and tool-level tests exist. Never invent a future endpoint in the manifest.
## Quality gates
- Every role owns a distinct output or policy boundary.
- The synthesizer is named.
- Conflict resolution is explicit.
- Shared-state writes cannot silently overwrite another role.
- Termination and budget ceilings are machine-readable.
- Deployment claims match surfaces that were actually packaged and tested.
## Return
Return the system-shape decision, topology, capability resolution, pack, execution mode, and the smallest blocked next step. Include compiled artifacts and an Evidence Receipt only when they were actually produced.
Files in this package (3)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
- references/portable-contracts.md 2 KB
Versions
The database has no other skills named system-forge.
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version c93e75fa7bb0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100deploy-multi-agent-swarm
Deploy Multi-Agent Swarm — configure decentralized agent topology, bidding protocol, consensus voting, parallel execution, conflict resolution, swarm state store. Use when: deploy, provision swarm. - 100skill-forge
Forge a reusable, portable skill from a proven workflow or capability brief. Use when the work needs repeatable instructions, triggers, guardrails, and evidence tests but does not need a persistent autonomous identity. - 100agent-forge
Design an agent only when a durable autonomy boundary is justified; compile it only when a Foundry runtime is available. Use for persistent decision rights, distinct memory, constrained tools, ownership transfer, or an ongoing schedule, channel, or API trigger. - 100skf-setup
Initialize forge environment, detect tools, and set capability tier (Quick/Forge/Forge+/Deep). Use when the user requests to "set up the forge" or "initialize the forge". - 90forge-catalog
Use when choosing which Forge agent, skill, command, bundle, or workflow should handle a request; when comparing Forge capabilities; when building a focused install surface; or when a user asks "what should I use?" before starting work. Routes to the smallest useful Forge… - 100forge-install
This skill should be used when the user wants to "install the Forge plugin", "set up Forge", "install forge-agent-lens-for-claude-code", "configure Forge for the first time", "get started with Forge tracing", or needs to complete the initial setup of the Forge Agent Lens for…