Menu
Use when the user wants to rename an entity's slug (the human-readable suffix in the file/dir name). Runs `aiwf rename` so the id is preserved and references stay valid.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Closes an aiwf epic — verifies all milestones done, scaffolds a wrap artefact, harvests ADR candidates, runs scoped doc-lint, merges the epic branch into mainline with a trailered merge commit, promotes the epic to done. Use when the user says "wrap E-NN" or "close the auth epic" and every milestone in the epic is wrapped. Commit and push require explicit human approval.
Closes an aiwf milestone — verifies all ACs met, runs scoped doc-lint, finalizes the milestone spec's wrap-side sections, promotes status to done, prepares the wrap commit. Use when the user says "wrap M-NNNN" or "finish the cache milestone" and the readiness check per `aiwfx-start-milestone` has passed. Commit and push require explicit human approval.
The aiwf per-repo code-health ritual — the whole-codebase companion to wf-review-code's per-diff gate. A stack-agnostic field guide of code-health principles: module boundaries, contracts, data discipline, tests that pin behavior, errors/logs/audit, reasoning aids, operational properties. Use when designing a new module, planning a refactor, reviewing a non-trivial diff, writing a spec that introduces new boundaries, or scoring an inherited codebase Strong/Weak/Missing with file:line evidence. These are advisory forces, not rules — consult them, don't enforce them; the project's own conventions win.
Sets up and begins an aiwf milestone — preflight checks, branch setup, status promotion to in_progress, then iterative TDD via wf-tdd-cycle. Use when the user says "start milestone M-NNNN" or "implement M-NNNN" and a draft milestone spec exists. Commits and pushes require explicit human approval.
Use when terminal-status entities have accumulated in the active tree and the operator wants to sweep them into per-kind `archive/` subdirs, or when `aiwf check` reports `archive-sweep-pending`. Explains dry-run vs `--apply`, the no-reverse rule, the `archive.sweep_threshold` knob, merge edge cases, and the per-kind storage layout.
Use when the user wants to edit (rewrite or replace) the markdown body of an existing entity — goal/scope/context prose, AC body sections inside a milestone, ADR rationale, gap problem statement, etc. Runs `aiwf edit-body` so the change rides through a verb route with proper trailers, instead of a plain `git commit` that triggers a `provenance-untrailered-entity-commit` warning.
| name | aiwf-rename |
| description | Use when the user wants to rename an entity's slug (the human-readable suffix in the file/dir name). Runs `aiwf rename` so the id is preserved and references stay valid. |
The aiwf rename verb changes the slug portion of an entity's path while preserving the id. References to the entity (which use the id) keep working.
A slug set this way is durable. It no longer matches the one the title would derive, so a later aiwf retitle preserves it rather than re-deriving over it — which is what makes this the right verb for an entity whose descriptive title makes an unwieldy path.
Looking to change a title? For changing an entity's title (the prose label, distinct from the slug), use
aiwf retitle <id> <new-title>— that is the dedicated verb for title mutations. This skill covers slug renames only. (The two verbs stay separate by design — single-mutation rule keeps reasoning local.)
The user wants the file or directory name to read better but the entity itself isn't changing identity. Examples: a milestone was named M-003-things and they want it to be M-003-acceptance-criteria.
aiwf rename <id> <new-slug>
aiwf normalizes the new slug into kebab-case (lowercases, ASCII-only, runs of non-alphanumerics collapse into single hyphens, trailing hyphens trimmed). "Acceptance Criteria!" becomes acceptance-criteria. The verb refuses when normalization yields the empty string. A slug identical to the current one is not a refusal: there is nothing to rename, so it reports that at exit 0 and commits nothing.
<dir>/<id>-<new-slug>.md or <dir>/<id>-<new-slug>/).git mv the file or directory to the new path.aiwf-verb: rename, aiwf-entity: <id>, aiwf-actor: <actor>.The frontmatter id does not change. The frontmatter title does not change either; if the user wants the displayed title updated too, edit it separately.
git mv by hand — you'll skip the trailer and aiwf history won't show the rename.addressed_by or relates_to.aiwf reallocate for that.