boiler-updatelisted

Triggered by the slash command /boiler-update <boilerplate-name|all> <description>. Updates a boilerplate's bank rule or skill, its cookbook, the bank index, and the on-disk skeleton in one pass, based on a description of what to change, add, remove, or restructure — keeping all four in sync so a convention change (e.g. "tests should live in __tests__ folders, not a root tests/ folder") takes effect the next time /boiler scaffolds from this boilerplate. `all` as the first argument applies the change to every boilerplate in the bank. If the scope is ambiguous (which boilerplate, or how many), asks for clarification before making any changes. Does NOT modify already-scaffolded live projects — that is always a separate, explicit request. Use whenever the user runs /boiler-update, mentions "update the boilerplate", "change the cookbook", "change a convention/rule for X boilerplate" or "for all boilerplates", "remove X from the template", "add Y to the boilerplate structure", or wants to evolve a boilerplate conve
orassayag/agentic-project-workflow · ★ 1 · AI & Automation · score 65

Install: claude install-skill orassayag/agentic-project-workflow

# /boiler-update — Boilerplate, Rule/Skill & Cookbook Updater ## Invocation ``` /boiler-update <boilerplate-name|all> <description of the change> /boiler-update --file <path-to-issues-file> ``` - `<boilerplate-name>` — apply only to that one boilerplate (e.g. `/boiler-update api-express tests should live in __tests__ folders next to their source file`). - `all` — apply to every boilerplate in the bank (e.g. `/boiler-update all tests should live in __tests__ folders next to their source file`). - `--file <path>` — batch mode: process a file of issue blocks, one at a time, each through the identical single-issue workflow. See "Batch File Mode" below. The first token is checked literally against this syntax before falling back to natural-language inference in Step 1 — so `all` as the first word always means "every boilerplate," not "always" in some looser sense. If the first token isn't `all` and doesn't match a known boilerplate name, fall through to Step 1's natural-language parsing (the command still works without the shorthand, e.g. "update the cookbook for api-express to..."). ## Batch File Mode ### Detection Before any single-description parsing, check for batch mode. The invocation is **batch mode** when either: - it is `/boiler-update --file <path>`, or - the first (and only) argument resolves to an existing file ending in `.txt` or `.md` (so `/boiler-update ./issues.md` works without the flag). Otherwise fall through **unchanged** to the single-descript