菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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".
| name | ductum-cli |
| description | 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. |
Ductum is the factory control plane. Use the CLI for supported state reads and writes.
sqlite3 ductum.db.ductum.yaml.--no-verify on commits.run_id to tools. Session binding owns that internally.Set the local alias:
export DUCTUM="node packages/cli/dist/index.js"
$DUCTUM init --no-login --no-browser
$DUCTUM start --no-browser
$DUCTUM project create <project> --repo "$PWD" --merge-mode human
$DUCTUM repair
$DUCTUM status
$DUCTUM repository list <project>
$DUCTUM repository add <project> --repo /absolute/path/to/git/repo
--repo must be an existing Git repository.
$DUCTUM factory settings
$DUCTUM repair
Factory Settings own Providers, Models, Harnesses, Workflows, Agents,
sandboxes, notifications, budgets, and app settings. Secret-bearing settings
must use ${ENV_VAR} references.
$DUCTUM spec intake <project> <path> --import
$DUCTUM spec list <project>
$DUCTUM task list <specId>
$DUCTUM task create <specId> <name> --repo <repositoryName> --role builder --file <prompt.md>
$DUCTUM task dag <specId>
$DUCTUM attempt start <taskIdOrName> --agent <agentName> --project <project>
$DUCTUM watch <attemptId>
$DUCTUM logs <attemptId>
$DUCTUM status <attemptId>
$DUCTUM approve <attemptId>
$DUCTUM deny <attemptId> --reason "<reason>"
$DUCTUM retry <attemptId>
A fresh agent reading only this skill plus AGENTS.md must be able to:
project create --repo.repair and status.spec intake --import.attempt start.Zero curl. Zero sqlite3. Zero hand-edited live YAML.