engineering / Build & debug
cloud-factory
Convert the current GitHub repository into a cloud software factory by installing agent skills, docs, labels, specs directories, and GitHub Actions workflow templates.
Put it to work.
Ask your agent to use cloud-factory, or let it load the skill when your task matches the description.
Use the cloud-factory skill [repo path] [--agent codex|claude|all]Invocation syntax varies by agent. Use the skill name in your prompt, or your agent’s supported slash command.
About this skill
Convert a GitHub repository into a cloud software factory with agent skills, workflow triggers, labels, and domain-doc placeholders.
Install
npx skills@latest add smeltery/skills --skill cloud-factory --agent codex --yesUsage
/cloud-factoryThe skill installs the reusable assets from smeltery/cloud-factory into the current repository and verifies the factory scaffold.
Factory flow
flowchart LR
Issue["New GitHub issue"] --> Triage["Triage agent"]
Triage --> Decision{"Readiness"}
Decision -->|ready-to-implement| Implement["Implementation agent"]
Decision -->|ready-to-spec| Spec["Spec agent"]
Decision -->|needs-info| Human["Human follow-up"]
Decision -->|wait-to-implement| Park["Parked"]
Spec --> SpecPR["PRODUCT.md + TECH.md PR"]
SpecPR --> Implement
Implement --> PR["Implementation PR"]
PR --> Review["Review agent"]
Review --> HumanReview["Human review"]
HumanReview --> Improve["Review-skill improvement loop"]
Improve --> ReviewFiles
SKILL.md— canonical skill definition.
Read the full SKILL.md
Cloud Factory
Convert a repository into a software factory.
Default command
From the target repository root, run:
gh api repos/smeltery/cloud-factory/contents/scripts/install-cloud-factory.sh \
--jq .content | base64 --decode | bashFor per-agent installation, set CLOUD_FACTORY_AGENT to a comma-separated list:
CLOUD_FACTORY_AGENT=codex,claude \
bash scripts/install-cloud-factory.shWhen using the remote installer with multiple agent targets:
CLOUD_FACTORY_AGENT=codex,claude \
bash -c "$(gh api repos/smeltery/cloud-factory/contents/scripts/install-cloud-factory.sh --jq .content | base64 --decode)"Workflow
- Resolve the target repository. Use the current working directory unless the user provided a path.
- Confirm it is a Git repository.
- Run the installer with the requested agent target. Default to
codexwhen unspecified. Use authenticatedgh apifor the private canonical repo. - Verify these files exist:
.agents/skills/triage/SKILL.md.agents/skills/spec/SKILL.md.agents/skills/implementation/SKILL.md.agents/skills/review-pr/SKILL.md.agents/skills/improve-review-pr/SKILL.md.github/workflows/triage-issues.yml.github/workflows/spec-ready-issues.yml.github/workflows/implement-ready-issues.yml.github/workflows/review-pull-requests.yml.github/workflows/improve-review-pr.ymldocs/agents/issue-tracker.mddocs/agents/triage-labels.mddocs/agents/domain.md
- Report what changed and what still needs human configuration.
Human setup checklist
- Create GitHub labels:
needs-triageready-to-implementready-to-specneeds-infowait-to-implement
- Set the cloud-runner API key secret required by the installed workflows.
- Edit
vision.md,roadmap.md, andCONTEXT.mdso triage has real product and domain context.
Guardrails
- Do not overwrite secrets or
.envfiles. - Do not enable auto-merge.
- Do not remove existing repository instructions.
- If files already exist, keep user changes and only replace Cloud Factory files when the user explicitly asks for a refresh.