ce-setup
Compound Engineering Setup
Non-interactive runs
Run non-interactively when the arguments contain mode:non-interactive, or when the request makes unattended intent unmistakable, such as a scheduled or CI job, or a caller asking for a run "headless", "unattended", or "without questions". "Automatically" alone is not that signal: it says when setup runs, not whether anyone can answer. When the signal is absent or unclear, run interactively. Strip the token before reading the rest of the arguments. A non-interactive run asks nothing and follows references/non-interactive.md, which replaces every offer, question, and approval in this file and its references.
Interaction Method
In an interactive run, ask each question below with the host's blocking question tool, and never silently skip or auto-configure. Read references/communication.md from this skill's directory before your first offer. It says how to reach that tool and what each offer, question, and preview must tell the user.
Pack Scaffold
When the invocation names a Compound Pack to add, create, or scaffold (the pack:<id> argument, or the same request in words), read references/pack-scaffold.md from this skill's directory and follow it in place of Phases 1-2: it writes the pack and its config entry only after the user approves, runs the health check itself, and reports into Phase 3 (Summary).
Review Docs
When the invocation asks to draft, refresh, or update coding standards or review docs (the standards argument, or the same request in words), read references/project-docs.md and follow it in place of Phases 1-2, drafting the whole set of files even when the request names one. Report into Phase 3.