[ PORTABLE SKILL ]
software-factory
Use this skill when designing, configuring, or hardening a software factory — an AI developer workflow where agents iterate toward a goal — a goal an agent iterates toward on its own with a real verification gate, persistent state, and a stop condition. Invoke it when the user mentions "build a loop", "agentic loop", "self-iterating agent", "run this on a schedule/cron", "/loop or /goal", "Ralph loop", "maker-checker", "fleet of agents", "autonomous workflow", "AI developer workflow", "ADW", "software factory", "agentic SDLC", or wants an agent to keep working a goal unattended until it's verifiably done. Also use when scoping whether a loop is even worth building, when picking a verification gate, when deciding what a loop is allowed to touch (blast radius), or when a loop is burning tokens without producing accepted work.
PART OF
bopen-tools →Complete plugin installation is recommended so this skill keeps its agents, hooks, commands, and runtime context.
Runtime support:Claude pluginCodex pluginPortable skills
- PUBLISHER
- b-open-io
- RELATIONSHIP
- authored
- VERSION
- 0.0.5
- BENCHMARK
- unknown
[ RECOMMENDED INSTALL ]
Install bopen-tools
The complete plugin is the supported path. It preserves everything the publisher designed to work alongside this skill.
Codex
VERIFIED[ ADVANCED · INDIVIDUAL SKILL ]
Install only this skill
Use this narrower path only when you intentionally want the portable SKILL.md without the plugin’s surrounding capabilities.
Skills CLI
VERIFIED- Installs only the portable skill; it omits plugin hooks, agents, commands, apps/MCP configuration, and unlisted companion skills.
[ PROVENANCE ]
Trace it to the source.
- DISTRIBUTED SOURCE
- skills/software-factory/SKILL.md ↗
- UPSTREAM SOURCE
- No separate upstream declared
- DISTRIBUTED DIGEST
- sha256:e5e901178f760e9250a04dd508c81d09a361862bbe20fc5c838b72409de78c17
- LOCK HASH
- Not applicable
Companion skills
No required companion skills are declared.
Agents using this skill
Satchmo
Use this agent when the user asks to "design an agent", "build an AI agent", "wire up tool-calling", "add memory to my agent", "set up agent routing", or "deploy this as a ClawNet bot", or needs help with evals, resilient chat UIs, or visual workflow diagrams for a multi-agent system. Covers agent architecture using OpenAI/Vercel SDKs. Not for authoring individual Skills or slash commands (use prompt-engineer) or auditing an existing skill's accuracy (use trainer). <example> Context: User wants to build a new agent from scratch user: "I need an agent that can call tools, remember context across turns, and route to the right specialist." assistant: "I'll use the agent-builder agent to design the tool-calling and routing architecture, then wire up memory." <commentary> Agent architecture design — tool-calling, routing, memory — is agent-builder's core job. </commentary> </example>
Milton
This agent should be used when the user wants to track, analyze, or optimize spending across the org's services and APIs. Use when the user says "check our spend", "how much are we spending", "budget report", "cost analysis", "agent spend", "API costs", "usage tracking", "billing overview", "cost optimization", or "are we over budget". Milton is the financial oversight layer for the bOpen agent organization — he tracks Anthropic token usage, Vercel billing, Railway services, and per-agent cost efficiency. He does not handle payment integrations or Stripe work (use payments agent) or infrastructure deployments (use devops agent). <example> Context: User wants to understand current API spend user: "How much are we spending on Anthropic this month?" assistant: "I'll use the CFO agent — Milton pulls usage reports from the Anthropic Admin API and breaks down spend by model and date range." <commentary> Anthropic cost reporting against the Admin API is Milton's core function. </commentary> </example> <example> Context: User wants a consolidated cost overview user: "Give me a budget report across all our services" assistant: "Milton can pull a consolidated view from Anthropic and Vercel and present spend with trends." <commentary> Multi-platform cost consolidation is Milton's org-wide reporting function. </commentary> </example> <example> Context: User suspects costs are too high user: "I think our agent spend is out of control. Can you do a cost analysis and find where we can optimize?" assistant: "I'll bring in Milton to audit per-agent and per-model spend and surface optimization recommendations." <commentary> Cost anomaly detection and model-tier optimization recommendations are within Milton's remit. </commentary> </example>
Root
Use this agent when the user asks to "deploy this to Vercel", "set up CI/CD", "wire up a ClawNet bot deployment", "add satchmo-watch monitoring", or needs help with the Vercel+Railway+Bun stack, Bitcoin auth patterns, or Trail of Bits security scanning (Semgrep/CodeQL) in a pipeline. Not for code-level security audits (use code-auditor) or dependency/secrets scanning outside CI (use security-ops). <example> Context: User wants a ClawNet bot deployed as a Vercel Sandbox user: "Deploy this bot as a Vercel Sandbox and wire up the heartbeat cron." assistant: "I'll use the devops agent to deploy the sandbox and configure the CI pipeline." <commentary> ClawNet bot deployment and CI/CD setup on the Vercel+Railway+Bun stack is Root's core job. </commentary> </example>
Wags
This agent should be used when the user wants to plan, organize, or manage a project using Linear. Use when the user says "plan this in Linear", "create tickets for this", "set up our board", "break this into issues", "manage this project", "organize this work", "what should we build next", or wants to turn a description, spec, or codebase into actionable Linear issues. Also use when the user asks about the linear-sync plugin, wants to connect a repo to Linear, or needs to understand how Linear fits into their Claude Code workflow. Examples: <example> Context: User has a new feature they want to plan out user: "We need to add Stripe billing to the app. Can you plan this in Linear?" assistant: "I'll use the project-manager agent to break this down into well-structured Linear issues." <commentary> User wants to turn a feature description into Linear tickets — core project-manager use case. </commentary> </example> <example> Context: User wants to understand the Linear + Claude Code workflow user: "How does linear-sync work with the linear-planning skill? What's the difference?" assistant: "I'll use the project-manager agent to explain the full Linear workflow." <commentary> User is asking about the linear tooling ecosystem — project-manager has holistic knowledge of both tools. </commentary> </example> <example> Context: User wants to connect their repo to Linear user: "Set up Linear tracking for this repo" assistant: "I'll use the project-manager agent to walk through connecting this repo to Linear with linear-sync." <commentary> User wants to configure linear-sync for a repo — project-manager knows both the plugin and the planning workflow. </commentary> </example>
Jason
Use this agent when the user asks to "write tests", "add test coverage", "set up e2e/Playwright tests", "fix failing tests", or "add a CI coverage gate", or when a change needs unit/integration/e2e tests before merging. Covers mocking, coverage analysis, and CI test automation. Not for performance profiling (use optimizer) or security review (use code-auditor). <example> Context: User just wrote a new module and wants proper unit test coverage before merging. user: "Can you write tests for this utility module? It handles date parsing and formatting." assistant: "I'll use the tester agent to write unit tests covering the happy path, edge cases, and error conditions using the AAA pattern." <commentary> Unit test authorship with structured coverage — Jason's core output. </commentary> </example> <example> Context: User wants to add end-to-end tests for their checkout flow before a major release. user: "We need e2e tests for the checkout process — add to cart, payment, confirmation." assistant: "I'll use the tester agent to write Playwright tests for the full checkout flow using the Page Object Model." <commentary> E2E test implementation with Playwright — Jason handles this, not the developer or integration-expert. </commentary> </example> <example> Context: User's CI pipeline has no test coverage reporting and they want visibility before adding a coverage gate. user: "We have tests but no coverage metrics in CI. Can you wire that up?" assistant: "I'll use the tester agent to configure coverage reporting in the test runner and add a GitHub Actions step to publish the report." <commentary> CI/CD test automation and coverage reporting setup is Jason's responsibility. </commentary> </example>
Related skills
ALL BOPEN-TOOLS SKILLS →bopen-tools
advisor
Active when a Claude Code or Codex main session needs an independent, read-only second opinion at a commitment boundary. Use before substantive work on a hard task, when stuck or changing approach, at a final review gate, or when the user says "consult the advisor", "get a second opinion", "ask codex", "ask Fable", "ask a bigger model", or wants an advisor set up. Supports Claude-native advisor behavior, Codex-as-advisor, and a Codex-main to Claude Fable CLI channel. The advisor returns guidance; the main session retains execution and decision ownership.
authored0.0.3
bopen-tools
agent-auditor
Comprehensive audit skill for agents and skills across the plugin ecosystem. This skill should be used when the user asks to "audit agents", "review skill quality", "check skill health", "validate plugin skills", "audit our agents", "run a skill audit", or when performing periodic maintenance on agents and skills. Also use after creating or modifying multiple skills to verify ecosystem consistency.
authored0.1.2
bopen-tools
agent-decommissioning
This skill should be used when the user asks to "retire an agent", "decommission an agent", "remove an agent from the team", "shut down a bot", "remove a bot", "sunset an agent", or "take an agent offline permanently". This is a joint workflow between Satchmo (agent-builder) and Johnny (clawnet-bot:clawnet-mechanic). Satchmo handles plugin/code removal; Johnny handles infrastructure teardown (ClawNet bot, sandbox, BAP identity).
authored1.0.0
bopen-tools
agent-onboarding
Complete end-to-end checklist for adding a new agent to the bOpen team. Use when creating a new agent, onboarding a new team member, or need to remember the full agent deployment pipeline — design, write, avatar, plugin, Paperclip registration, roster, and optional ClawNet bot deployment.
authored1.1.1
bopen-tools
benchmark-skills
Use this skill when creating evals or assertions for a skill, running the skill benchmark harness, measuring skill effectiveness vs baseline, or writing evals.json files alongside skills. Invoke whenever someone asks to test, benchmark, or evaluate a skill's quality.
authored2.0.1
bopen-tools
charting
Full-stack data visualization and charting intelligence. This skill should be used when the user asks to "create a chart", "visualize this data", "build a dashboard", "plot this", "graph these metrics", "show me a chart of", "make a bar chart", "create a line graph", "build a heatmap", or needs help choosing the right chart type, selecting a charting library, or engineering the data pipeline from raw database state to rendered visualization. Covers chart selection, data transformation, library choice by scale, performance optimization, and accessibility.
authored1.0.0