Workbench scaffold

Turn a folder into a workbench: the operating agreement, the desk file, the lint, the check, the hook and the two session skills. This skill is installed globally because it runs in folders that hold nothing yet: either as a symlink from the user's skills directory to skills/workbench-scaffold inside a clone of ai-workbench, or as a copy with WORKBENCH_HOME pointing at that clone. Everything it writes comes from the clone, never from memory.

1. Resolve the source

First hit wins:

1. $WORKBENCH_HOME, if it contains templates/AGENTS.md and scripts/workbench_lint.py.
2. This skill's own directory with symlinks resolved (realpath), walked upward until a directory holds both.
3. Neither: stop, say the ai-workbench clone is missing, and name both options as the fix.

Say which source was used and its path before going on; a stale clone copies stale files.

2. Pick the mode

Take the first case that fits and say which, and why, before touching anything:

• scripts/workbench_lint.py exists → audit.
• AGENTS.md exists, or the folder has content → adopt.
• Otherwise → fresh.

Audit. Compare the repo against the source and report, in this order:

1. Drift in every copied file, using cmp and diff -u against the source: scripts/workbench_lint.py, scripts/check, .githooks/pre-commit, .claude/skills/session-open/SKILL.md, .claude/skills/session-close/SKILL.md. Offer to re-copy each drifted file; offer nothing else for it. Local changes to these files are the drift, not a customisation.
2. scripts/check output; every finding is an audit item.
3. AGENTS.md sections missing against templates/AGENTS.md, and any placeholder (<...>) still unfilled.
4. Whether git config core.hooksPath prints .githooks.

Offer each fix separately and change nothing without a yes.

Adopt. Report what already exists. Ask only what the missing pieces need, reading answers off the repo wherever it already states them. Write only what is missing. Never overwrite an existing file.

Fresh. Interview, then write.

3. Interview

One question at a time, and only these:

1. Project name.
2. Purpose, in two to four lines: what the repo is and produces, and the one thing an agent would get wrong without being told.
3. The tracker, if any: where issues live. This becomes a line under ## Context.
4. Which existing folders are non-obvious enough to earn a line under ## Layout.
5. The commands that matter, and which of them write or cost money.

Leave the domain rules placeholder empty. Rules get earned by mistakes.

4. Write

If the folder is not a git repository yet, run git init first.

Create no other folders. Git does not hold empty directories, and the layout section documents what appears on first use.

5. Prove it and commit

Run git config core.hooksPath .githooks, then scripts/check. Show the output and confirm it ends in check: clean. In fresh mode the scaffold is the repository's first commit, on its default branch; there is nothing to open a pull request against yet. In adopt mode, and for every fix accepted in an audit, commit on a branch and open a pull request like any other change. The commit message names the scaffold. Close by naming session-open as the command for the next session.