mise-en-place-scaffoldlisted

Fill-only repo scaffold against the packaged standards — use whenever the ask is "scaffold this repo", "run mise-en-place", "fill the audit gaps", "set up a new repo to the standard", or any request to create the missing meta-structure the compliance audit flags. Runs the bundled script from the repo root: `--plan` (default) prints planned creations, conflicts, and non-mechanical items per checklist ID and writes nothing; `--apply` creates only the planned items; `--init-manifest` writes the commented `_meta/mise-en-place.yml` variance template. Additive-only: it NEVER overwrites, merges, edits, deletes, or moves an existing file, never provisions GitHub-side objects, and never authors README/CLAUDE.md/AGENTS.md content. Not for measuring compliance (repo-compliance-audit) or for questions about what the standard says (repo-meta-structure / project-memory skills).
hsb3/dotfiles-agents · ★ 0 · Code & Development · score 70

Install: claude install-skill hsb3/dotfiles-agents

# Mise-en-place scaffold Resolve `<plugin-root>` to the installed package directory containing this skill's `skills/` parent, using the loaded skill's absolute path. Do not assume a shell variable is set by the client. Substitute that absolute path in the commands below; both Claude Code and Codex can run them from the target repository. The pair to the read-only compliance audit: the audit measures, this fills the gaps. One code path serves brownfield compliance and new-repo setup — against a fresh `git init` with a filled manifest, one `--apply` produces the full standard. ## The loop (audit → plan → review → apply → re-audit) 1. **Run the audit first** (repo-compliance-audit skill) — or use its latest output — and review the gap table with the owner. 2. If per-repo variance or GitHub-side knobs are needed: `--init-manifest`, fill the fields, commit (see `references/manifest.md`). 3. **Plan, and present the plan before applying** (from the target repo's root): ```bash python3 "<plugin-root>/skills/mise-en-place-scaffold/scripts/scaffold.py" --plugin-root "<plugin-root>" --plan ``` Show the table verbatim: planned creations, conflicts (with diffs), and manual items, per checklist ID. Do not skip this gate. 4. **Apply** only after the plan is reviewed: ```bash python3 "<plugin-root>/skills/mise-en-place-scaffold/scripts/scaffold.py" --plugin-root "<plugin-root>" --apply ``` 5. **Re-run the audit** — created rows PASS; conflict and deferre