sandboxlisted

Do WRITING pre-work for a clarify item that is blocked by a knowledge gap - a missing measurement, a mockup, or a feasibility proof - WITHOUT touching production code, without git, and without disturbing the task / build agent. Use when a 1_clarify item cannot be answered by a product decision alone but needs something built or measured first; when working in the plan / clarify role and a clarify question needs evidence; and for isolated read-and-write pre-work in autonomous / AFK runs. Triggers on clarify pre-work such as "measure this before we decide", "build a quick mockup to clarify", "prove this is feasible", "sandbox this", "Messung / Mockup / Machbarkeit vor der Klaerung", "bau eine Sandbox dafuer". Do NOT use for a pure product decision (nothing to measure - that is answered by asking the user), and never for production code or commits.
Marcel-Bich/marcel-bich-claude-marketplace · ★ 13 · AI & Automation · score 80

Install: claude install-skill Marcel-Bich/marcel-bich-claude-marketplace

# sandbox - writing pre-work for clarify items Clarify items often hang on a knowledge gap that is NOT a product decision: a missing measurement, a mockup, or a proof that something is feasible. The plan / clarify role (`role-plan`) must not touch production code and must not commit. The sandbox gives it a place to do writing pre-work OFF to the side - no production code, no git, no interference with the task / build agent - so the clarify question can be answered with evidence instead of guesswork. ## Two folders - `.credo/sandbox-tmp/` = UNVERSIONED work in progress. One folder per item: `.credo/sandbox-tmp/<id>-<slug>/` with a `README.md`. This is where pre-work is built. - `.credo/sandbox/` = the PROMOTION TARGET for accepted, version-worthy artifacts. It follows the credo folder-versioning policy: in an untracked repo it stays local; in a version-tracked repo (`CREDO_VERSION_TRACKED=1`) it IS versioned. - `docs/` is NOT the promotion target. Extracting a promoted artifact into `docs/` is a SEPARATE step the user prompts for explicitly; it never happens automatically. ### exclude behavior (owned by credo-init) The git-exclude is managed by `credo-init` in a single managed block in `.git/info/exclude` (see the credo-init policy). Do not write that block from anywhere else. - Default (untracked, `CREDO_VERSION_TRACKED` unset): all of `.credo/**` is excluded, so both `sandbox-tmp/` and `sandbox/` stay local. Nothing extra is needed. - Tracked (`CREDO_VERSION_