dark-factory-build

Dark Factory Build — end-to-end orchestrator

Overview

This skill runs a complete Dark Factory build: intent → semantics → design → tests → code → verification → live proof → shipped + documented. It is the conductor; the per-stage df-* skills do the work. Everything is modeled through the data-transform lens (data nodes + pure/effect transforms + validation rules + authority), built test-first, verified adversarially (never on a self-report), executed autonomously in dev/non-prod, and documented as tickets + DF spec docs + memory at every step.

It is the generalization of a real run: a DEX arbitrage bot taken from half-finished to a liquidity-aware arbitrage engine with 5 DF docs, TDD + ~290k-case adversarial fuzz, and a live on-chain no-overshoot proof — all ticketed and committed.

When to use

• "Build this the dark factory way" / "run a DF build" / "do this end-to-end autonomously."
• A spec or half-built project needs to be finished with docs + TDD + verification + tickets.
• Any non-trivial feature where you want the full discipline: semantics first, blind-verified, evidence-backed.

For a single stage only (just the PO doc, just TDD), invoke that df-* skill directly instead.

The pipeline

Run the stages in order. Each stage has an owning df-* skill, a concrete artifact, and a ticket. Earlier stages gate later ones (a cold reader must be able to build the next stage from the previous artifact alone).

You MUST call the owning skill before producing that stage's artifact. Reading this table is not running the stage. The table tells you which skill owns the stage; the skill itself carries the checklist, the required artifact shape, and the verification steps — none of which are reproduced here, and all of which are silently skipped if you write the doc directly.