Installs just this skill. Get the whole plugin for auto-invocation.
โก How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/skill-factory
๐๏ธ Context preview
The summary Claude sees to decide when to auto-load this skill.
Run a full build-and-ship pipeline from a spec โ use for hands-off project generation
๐ Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
๐ฆ Ships with octo
</> SKILL.md
skill-factory.SKILL.md
---name: skill-factory
aliases:
- factory
- dark-factory
- build-from-spec
- autonomous-build
description: "Run a full build-and-ship pipeline from a spec โ use for hands-off project generation"
execution_mode: enforced
validation_gates:
- spec_file_validated
- orchestrate_sh_executed
- factory_report_exists
invocation: human_only
---# STOP - SKILL ALREADY LOADED
DO NOT call Skill() again. Execute directly.
## EXECUTION CONTRACT (MANDATORY โ 8-step sequence, CANNOT SKIP)
### STEP 1: Clarifying Questions (MANDATORY)
Ask via AskUserQuestion BEFORE any other action:
1. Spec location โ path to NLSpec file, or paste inline
2. Satisfaction target override (Use spec default / Custom 0.80-0.99)
3. Cost approval โ ~$0.50-2.00 for ~20-30 agent calls (Approve / Approve --ci / Decline)
If spec path provided inline with the command, use it but still ask remaining questions.
If user says "skip", use defaults and proceed.
DO NOT proceed to Step 2 until answered.
### STEP 2: Display Visual Indicators (MANDATORY โ BLOCKING)
Validation: All external providers unavailable โ continue with Claude-only (warn user about reduced diversity). At least one available โ proceed normally.
**Before committing to the expensive embrace phase (~$0.50-2.00), verify that generated scenarios actually cover the spec's edge cases.** A quick cross-provider challenge here can prevent wasting an entire factory run on incomplete scenario coverage.
**After orchestrate.sh parses the spec (Phase 1-2) and before embrace execution (Phase 4), dispatch a scenario coverage review:**
If a second provider is available, dispatch the challenge through Octopus routing:
```bash
# Read the spec to extract behaviors and constraints