TDSchreur/tds-factory

TDS Factory is a small software factory. It installs skills into Claude, Codex and Copilot. One of them, factory, takes a piece of work from idea to pull request.
New here? Read the install guide to set the Factory up, then the usage guide to run your first piece of work. Before a first Run, run tds-factory doctor in the project. It checks whether the project is ready and changes nothing.
## Setup
You need Node 20 or newer. One line installs the latest Release and its skills.
macOS and Linux:
sh
curl -fsSL https://github.com/TDSchreur/tds-factory/releases/latest/download/install.sh | sh
Windows (PowerShell):
powershell
powershell -c "irm https://github.com/TDSchreur/tds-factory/releases/latest/download/install.ps1 | iex"
Each script checks Node and npm, installs the Release with npm and runs tds-factory install. Run the same line again to update. To read the script before you run it, download and open it. You can also run the two commands yourself, the same on macOS, Linux and Windows:
sh
npm install -g --allow-remote=root https://github.com/TDSchreur/tds-factory/releases/latest/download/tds-factory.tgz
tds-factory install
npm 12 refuses URL installs by default, so the command needs --allow-remote=root. tds-factory --version shows the installed version. Skills are not installed automatically by npm install. tds-factory install installs them, and you must run it again after every update, because the installed factory Skill must use the same Run commands as the CLI. tds-factory update and the one-line scripts do both steps.
To update, run tds-factory update. It installs the latest Release when yours is older and checks the download against the Release's checksum. Then it runs tds-factory install --force, which replaces agent files and skills you edited with the defaults. It also replaces any skill folder of the same name that tds-factory did not install. Use tds-factory update --no-force to keep them. The one-line scripts keep them too. Set TDSFACTORYFORCE=1 to replace them, or TDSFACTORYSKIPSKILLS=1 to install only the CLI.
Maintainers publish Releases manually. See the release guide. To work on the Factory itself, see the development guide. The install guide describes the install options (--agent, --project, --force, --dry-run).
## The flow
A Run is one pass through four Stages, after a Preflight (tds-factory doctor runs its checks). Start it with the factory skill (/factory).
mermaid
flowchart TB
subgraph Preflight
P[conventions and Verify command, asks you if it is missing]
end
subgraph Define
A[grill-with-docs] --> B[to-spec] --> C[to-tickets]
end
subgraph Build
E[implement-spec with tdd]
end
subgraph Check
F[code-review, security-scan, infrastructure]
end
subgraph Finish
G[pr] --> H[unslop]
end
P --> A
C --> E --> F
F -->|problems found, fewer than 4 loops so far| E
F -->|clean| G
F -.->|not clean, or loop cap reached: ask first| G
Each Stage produces one result.
Define writes a Spec in docs/specs/ and a Ticket per task in the project's Issue tracker.
Build finishes every Ticket test-first, with one commit each. It builds what the Ticket asks and names any smaller option in one line in build.md.