// Coding factory — transforms a spec into a reviewed PR via BUILD → INSPECT pipeline with adversarial review. Use when you need to implement a spec end-to-end with independent code review, or when the user invokes /factory run <spec-path>.
| name | factory |
| description | Coding factory — transforms a spec into a reviewed PR via BUILD → INSPECT pipeline with adversarial review. Use when you need to implement a spec end-to-end with independent code review, or when the user invokes /factory run <spec-path>. |
Linear BUILD → INSPECT pipeline for spec-driven development. Rework up to 3 times if INSPECT finds issues.
/factory run <spec-path>
Example:
/factory run specs/044-factory-skill-mvp/README.md
This skill is orchestrated by the pipeline engine. When invoked, execute:
synodic harness run --pipeline factory --spec <spec-path>
Pipeline definition: .harness/pipelines/factory.yml
Prompt templates: skills/factory/prompts/
Output schemas: schemas/build-report.json, schemas/inspect-verdict.json
.harness/factory.governance.jsonlGenerative-adversarial coordination — locks a generator and critic agent in an escalating quality loop. The critic actively tries to break the generator's output with increasing sophistication. Quality emerges from adversarial pressure, not checklist compliance. Use when you need deep quality hardening beyond standard review, or when the user invokes /adversarial run <spec-path>.
Fractal decomposition — recursively split a complex task into orthogonal sub-specs, solve each leaf independently via subagents, then reunify results bottom-up. Use when a task is too large for a single agent pass, when you need to decompose a problem into independently-solvable pieces, or when the user invokes /fractal decompose <task-or-spec-path>.
Speculative swarm — forks N agents to explore divergent strategies for the same task, cross-pollinates insights at checkpoints, prunes convergent branches, and fuses the best fragments into a composite result. Use when a problem has multiple viable approaches and you want to explore them simultaneously, or when the user invokes /swarm run <spec-path>.