Audit the decisions in .ank/ against the current code and report what no longer holds. Use when asked whether ADRs, specs, or tasks are still accurate, after a milestone, or when the corpus and the code seem to disagree.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Decisions age. The corpus says what was true when each one was ratified; the code says what is true now. This skill compares the two and reports. It never rewrites.
The ank skill is the contract and applies here in full. This file adds the audit policy only.
ank review what is proposed, and which scopes have gone dead
ank check what is already known to be wrong
ank find --type adr the decisions; --type spec, the rules
ank graph an order that may no longer make sense
ank log <id> what executors recorded against the entity
Logs are the richest source: a discrepancy entry is a finding somebody already made for you, recorded mid-task and read by nobody since.
Then read the code each scope covers. ank scope <path> names what claims to govern a file; the file says whether the claim still holds.
For each accepted decision, three questions:
Evidence or it is not a finding. Name the entity, quote the assumption, point at the code, test or log that breaks it.
Findings ordered by impact, each in this shape:
ADR-xxxx assumed: what the decision took as true
measured: what the repository shows now
evidence: file, test, or log entry
recommend: supersede, keep, or needs a decision
Never edit an accepted entity and never write the superseding one uninvited. Superseding is planning: hand the findings to the human, and what they decide enters through ank-plan.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Read a repository's tasks and binding constraints, claim work, and finish it with proof. Use when working in a repo that has a .ank/ directory.
The English summary is being prepared. Showing the original description.
Work a defect back to its cause before changing anything, and close it with a regression test. Use when a claimed task's criterion names a defect in a repository with a .ank/ directory.
The English summary is being prepared. Showing the original description.
Orchestrate several ank agents in parallel, each on its own task, worktree and branch. Use only inside a herdr pane, when asked to fan ank tasks out across agents in a repository with a .ank/ directory.
The English summary is being prepared. Showing the original description.
Work through the open tasks in .ank/ without supervision, one claim at a time. Use when asked to work the backlog, chain tasks, or run autonomously in a repository with a .ank/ directory.
The English summary is being prepared. Showing the original description.
Interview a goal into decisions and tasks recorded in .ank/. Use when someone brings a feature, change, or problem to plan before implementation in a repository with a .ank/ directory.
The English summary is being prepared. Showing the original description.
Drive an implementation test-first, red before green, against a claimed task's frozen criterion. Use when implementing a task in a repository with a .ank/ directory.
The English summary is being prepared. Showing the original description.