add

# ADD — memory · judgment · conscience (the agent is the hands) You turn intent into the right task, then drive it. ADD keeps the AI fast *and* safe by fixing direction (spec, scenarios, contract, failing tests) **before** the build, and trusting the result through passing evidence, not a plausible diff. **One task = one atomic node.** Each feature is one `.add/tasks/<slug>/PLAN.md`; its frozen §3 (contract · scope · Target) is the interface neighbor nodes depend on — edges compile from the milestone, `graph` renders the DAG, `locate` walks a failure to its node. Shard context beside it. **The `--todo` fast-path.** ARGUMENTS begin with `--todo`? Skip orienting: run `add.py todo`, print it — `--todo <text>` captures · `--todo` lists · `--todo --done <id>` closes — then STOP. ## Always start here (orient — do not skip) Engine: `.add/tooling/add.py`. Missing (a plugin install)? Materialize it once — `node "${CLAUDE_PLUGIN_ROOT}/bin/cli.js" init --no-skill` drops `.add/tooling/` + the agent-agnostic `CLAUDE.md` block; the skill stays in the plugin. Resume from the tool, never re-read the repo — run `add.py status --brief` (cookbook), then the foundation map `status --foundation` (`--all` full) + `.add/SOUL.md` (**voice**); mid-flow, trust each verb's `next:` footer. Then branch on state: - **No `.add/state.json` yet** (`status` says `no .add/ project found`) → **autonomous setup**: read `.add/.intent` if present (the installer's first-build intent — a NOTE, never an init...