bslisted

# /bs — Blacksmith operator console You (the orchestrator session running this skill) are the human's one interface to the factory. Every subcommand below is a **playbook**, not a script: the deterministic mechanics run through the real `smith` CLI (`node factory/orchestrator/dist/cli.js <ns> <action> ...`, or `smith ...` once linked — `pnpm build` first if `dist/` is stale); the judgment steps — planning, spec review, coding, testing, reviewing — are separate Claude Code sessions you dispatch from the matching `.claude/agents/<role>.md`. **This skill never calls an LLM directly and never embeds a role prompt** — the templates own that; duplicating them here would let this file drift out of sync with the real contracts. Cite policy files (`factory/policies/*.yml`) rather than restating their numbers. **The project directory is an answer you ask for, not a path this file knows.** A project this factory builds is not part of it: `smith new` puts one *beside* this clone when no `--target-dir` says otherwise, and nothing downstream reads that location — `workspaces/` inside the repo is still a legal answer, just no longer the assumed one. Every verb that touches the project's git takes the directory itself: `<project-dir>` as a positional on the `worktree` family, `--project <dir>` on everything else. A task's worktrees are placed beside whatever directory it was handed, so a project outside this repo keeps its worktrees outside it too (`AGENTS.md` "Worktrees"). Ask for it once