ductum

Operate the Ductum factory through the DB-backed Ductum CLI. Use for Ductum project/repository/spec/task/attempt/status/watch/approve/deny/retry work, factory dogfooding, or when asked to run work through Ductum. Never use ductum.yaml.

Onboard an existing repository into the Ductum factory using the DB-backed Ductum CLI. Use when the user says "onboard this repo to Ductum", "add this project to the factory", "make this repo Ductum-ready", or asks how to create/import specs for another repo. Never use ductum.yaml.

Create Ductum-importable Markdown spec packages. Use when Codex needs to turn backlog, review notes, planning docs, dispatch prompts, or implementation plans into Ductum specs with README execution-order tables and P*.md task prompts; when preparing work for ductum spec import; or when checking whether a spec package is ready to dispatch. Never use YAML.

Drive the Ductum factory through its CLI. Use for Factory, Project, Repository, Component, Spec, Task, Attempt, Factory Settings, Repair, approval, and recovery work. Never use curl, sqlite3, or hand-edited ductum.yaml as a substitute for a shipped command.

Onboard an existing application to the Ductum factory. Detects the stack (Python/Node/Go/Rust/etc), detects the existing agent context doc (CLAUDE.md, AGENTS.md, or README.md), creates .edictum/workflow-profile.yaml with correct setup+verify commands, and prints the ductum.yaml entry to add. Use when the user says "onboard X to ductum", "add ductum support to this project", or "scaffold this project for the factory".