scaffolding-scriptslisted

# scaffolding-scripts Scaffold a new automation script under the monorepo's `scripts/*` workspace — the _greenfield_ entry point for a **net-new** consumer that has no `scripts/<name>/` directory yet. The heavy lifting is deterministic: the generator `pnpm scaffold:script <name>` emits every file from `templates/script/` (package manifest, tsconfigs, the modular `src/` skeleton, the ADR-0022 §8 config smoke test, a README, and the contract page under `docs/reference/scripts/`) and wires the root tsconfig project reference. The skill's job is the orchestration around it: the pre-work gate, the required parameters, install/build/smoke, doc fill-in, index regeneration, and hand-off. The fleet conventions are ratified in [ADR-0022](../../../docs/adr/0022-reintroduce-scripts-workspace.md); the API the script builds against is [`docs/reference/core/script.md`](../../../docs/reference/core/script.md); the CI backstop is `pnpm check:script-scaffold`, which verifies every script package against the same shared manifest (`bin/lib/script-scaffold.mjs`) the generator emits from. ## Role boundaries (hub-and-spoke) This skill runs in the **hub** (main agent) and only lays down the scaffold seam — the generated skeleton whose step bodies do nothing real yet. It does **not** implement the script's business logic or review it: implementation is handed to the `implementing-scripts` skill, whose spokes (`test-author` RED, `code-implementer` GREEN, `code-reviewer` + `security-reviewer` review