Menu
Use when `aiwf check` reports an `ids-unique` finding (two entities share an id, typically after a branch merge). Runs `aiwf reallocate` to renumber one of them and rewrite all references.
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.
Based on SOC occupation classification
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-reallocate |
| description | Use when `aiwf check` reports an `ids-unique` finding (two entities share an id, typically after a branch merge). Runs `aiwf reallocate` to renumber one of them and rewrite all references. |
The aiwf reallocate verb resolves id collisions by picking the next free id, git mv-ing the colliding entity, and walking every other entity's frontmatter to rewrite reference fields. Body-prose mentions are surfaced as findings — humans review those.
aiwf check reported ids-unique (or the pre-push hook blocked a push for the same reason). Two files claim the same id — almost always because two branches independently allocated the id and were then merged.
aiwf reallocate <id>
# or, when the id is ambiguous (both entities share it):
aiwf reallocate <path>
When passing an id and two entities share it, aiwf runs the trunk-ancestry tiebreaker:
aiwf refuses with an "ambiguous" error listing both candidate paths and the diagnostic. Pass a path to disambiguate.Sandbox repos with no trunk in scope skip the tiebreaker — operators always pass a path there.
The id format never gets a suffix (no M-007a); collision recovery always picks max + 1 against the working tree ∪ trunk.
max + 1 at call time, scanning the working tree ∪ the configured trunk ref so the new id can't collide with trunk either).git mv the colliding file or directory to its new path.parent, a gap's addressed_by).prior_ids: frontmatter list (oldest-first). The list is the tree-level source of truth for lineage; tree-only readers (aiwf show, the HTML render, future projections) read it directly without shelling out to git log.aiwf-verb: reallocate, aiwf-entity: <new-id>, aiwf-prior-entity: <old-id>, aiwf-actor: <actor>.aiwf history <old-id> still works after a renumber: the cmd dispatcher resolves the queried id through prior_ids, walks the full chain (every prior id plus the current id), and runs one git log grep against the union. Both the original id and the current id return the same chronological timeline — pre-rename commits, the rename commit, and post-rename commits, in order.
ids-unique finding exists; renumbering otherwise rewrites history for no benefit.