Menú
Use when the user asks "what happened to <entity>" or wants the timeline of an aiwf entity (or acceptance criterion). Runs `aiwf history` which reads `git log` filtered by structured commit trailers.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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-history |
| description | Use when the user asks "what happened to <entity>" or wants the timeline of an aiwf entity (or acceptance criterion). Runs `aiwf history` which reads `git log` filtered by structured commit trailers. |
The aiwf history verb answers "what happened to this entity?" by filtering git log for the entity's commit trailers. There is no separate event log; the git log is the time machine, made queryable by aiwf-verb / aiwf-entity / aiwf-prior-entity / aiwf-to / aiwf-force / aiwf-audit-only and the I2.5 provenance trailers (aiwf-principal, aiwf-on-behalf-of, aiwf-authorized-by, aiwf-scope, aiwf-scope-ends, aiwf-reason).
The user wants the lifecycle of one entity. Example phrasings: "when was M-NNNN created?", "show me what happened to E-NNNN", "why is this gap closed?", "show the TDD cycle for M-NNNN/AC-N", "who authorized this work?".
aiwf history <id> # one line per event
aiwf history <M-id>/AC-N # composite id — just that AC's events
aiwf history <id> --show-authorization # expand the auth-SHA column inline
aiwf history <id> --format=json # full trailer set in JSON
The output is one event per line:
DATE ACTOR VERB TO DETAIL COMMIT [chips...]
principal is present and differs from the actor (the agent-acts-for-human pattern), the column renders principal via agent. Direct human acts show the actor verbatim.aiwf-to: (→ active, → green); dash when absent.[scope: opened] on aiwf authorize rows, [<scope-entity> <auth-short>] on scope-authorized agent verbs, [<scope-entity> ended] per scope ended by a terminal-promote.[forced: <reason>], [audit-only: <reason>], [reason: <text>] for the corresponding trailers, then any commit body prose.aiwf history M-NNNN shows the milestone's own events PLUS every AC's events (M-NNNN/AC-N). The match is anchored on the literal / boundary so M-NNNN/ cannot prefix-match M-MMMM/.aiwf history M-NNNN/AC-N shows only that AC's events.By default scope chips abbreviate the auth-SHA to 7 characters: [E-NNNN 4b13a0f]. With --show-authorization, the full SHA is inlined: [E-NNNN 4b13a0fdeadbeef...]. Useful when copy-pasting into another aiwf invocation that needs the full SHA. JSON output always carries the full SHA in authorized_by.
prior_ids lineage to its current canonical entity. The chain is the queried id, plus every id in the canonical entity's prior_ids, plus the canonical entity's current id when distinct from all of those.git log with greps for aiwf-entity: <id> OR aiwf-prior-entity: <id> trailers for every id in the chain (so a single query weaves pre-rename, rename, and post-rename commits into one timeline). For bare milestone ids, additionally greps for <id>/AC-\d+ so the milestone view includes its ACs.authSHA → scope-entity map for chip rendering.After two reallocates, all queries against the old id, intermediate id, and current id return the same chronological timeline.
aiwf history shows only verb-driven events. Hand-edits to the markdown file won't have trailers and won't appear here. aiwf check flags such commits as provenance-untrailered-entity-commit (warning) at push time so the audit gap is visible; aiwf <verb> --audit-only --reason "..." is the repair path.aiwf-to:; the column renders as a dash. No retroactive fill.prior_ids shipped) don't carry the lineage in frontmatter. Querying the old id still surfaces the rename event via the existing aiwf-prior-entity: trailer, but post-rename history surfaces only when querying the new id. New reallocates fill prior_ids automatically; legacy chains can be backfilled manually if needed.git log is authoritative.[forced: ...] or [audit-only: ...] chip — they signal a sovereign override and rarely come without context worth surfacing to the user.