Skip to content

Releases

HankNDory 2.11

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 16:07
  • Hard spend cap in reference/cost.md: the user may set one, such as an amount over any rolling 28 days. Crush estimates the spend hourly, and when the cap is reached everything stops, Crush's own hourly run included, until the user says resume.
  • The strong tier prefers the model family with the lowest cost per unit of work, for example GPT-5.5 at high effort over Claude Opus, unless the charter names another. Helpers use a small, cheap model, for example GPT-6 Luna at medium effort.

Install: gh skill install ajaxdude/HankNDory hankndory@v2.11 --agent github-copilot --scope user --force

Rollback: gh skill install ajaxdude/HankNDory hankndory@v2.10 --agent github-copilot --scope user --force

HankNDory 2.10

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 15:33

A default cost policy, in the new reference/cost.md, because helpers and long conversations were most of the spend. The charter's new Cost line may change any of it.

  • Two model tiers. The conversation acting as Hank and every review gate that decides go or no-go (each Dory reviewer, critic round, and dory-pass, and Bruce's code review) run on a strong model at high effort, never the maximum unless the charter sets it. Every other sub-agent or child session, including building, tests, monitors, Bailey's spikes, Ray's acceptance tests, drafting, summarising, and Hank's checks, runs on a much cheaper model at medium effort. The charter names the actual models. A helper task that fails its checks twice goes back to Hank.
  • At most three helpers and reviewers run at once per voyage, counting sub-agents, background agents, and child sessions. It is the default for the charter's "Parallel streams" line.
  • Check at most once an hour. Wait for completion notices; a repeating timer or automation runs at most hourly. Reviewers that can't all run at once run in groups on the same commit.
  • A conversation whose context passes about 300,000 tokens writes a short handoff and carries on fresh, at any point in the voyage.

Install: gh skill install ajaxdude/HankNDory hankndory@v2.10 --agent github-copilot --scope user --force

Rollback: gh skill install ajaxdude/HankNDory hankndory@v2.9 --agent github-copilot --scope user --force

HankNDory 2.9

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 07:45

A hybrid for the age of AI. Code is cheap for agents, but coherence is expensive, so design first only what is hard to undo, design each stretch when it starts, and show working software at every milestone.

  • Two-way doors: a change that reverting its commits fully undoes, that changes no shared data or environment, publishes or deploys nothing, adds no paid resource, and touches nothing under "Always standard", is built first, at every pace, on a branch that is not shared or default, and written up as built. A one-way door is designed and approved first. Nothing merges or deploys until the Map is approved, the leg's acceptance tests pass, and its code review is clean. A change that is all two-way doors gets a short Map, builds at once, and is reviewed and approved as built. The new reference/map-and-legs.md holds the rules; core rules 3 and 7, sizing, "Pick the pace", and the template point to it.
  • The Map and its legs: before building, Detailed implementation holds the contracts that cross legs, the legs in order, one line each, and the first leg in full. Each later leg is written when it starts, from what earlier legs taught. A later one-way-door leg gets one review of Steps 6 and 7 scoped to it, with its own limit of one critic round (two at careful pace), and its own approval; a two-way-door leg is written as built and checked by the code review. Status tracks each leg's door and state. Merging stays reserved unless the charter delegates it. A finished leg shrinks to what later legs rely on. A design written before legs counts as one leg.
  • A demo at every milestone, in Dory's voice: what works now, how to try it, the checks that pass, Bailey's measures, the choices made and why, and what comes next. It is not a gate unless the charter's review points say so.
  • A retro when the voyage ends: three to six plain lines, recorded in the charter's history file and sent with the last update. Changes to this skill are proposals for the user.
  • Three new roles in the new reference/crew.md, each started as a stream when there is work for it. Ray writes each leg's acceptance tests from the design before seeing its code; the builder runs them and never changes them, a disputed test gets one exchange before Hank decides, and a leg is done only when they pass and its code review is clean. Bruce runs the mean code review as an attacker would, and checks no acceptance test was weakened. Bailey runs spikes and experiments, gathers the measures, and writes a one-page card for each spike, experiment, model, or dataset. New mode acceptance-tests.
  • README: a new section with the hybrid approach, the crew table, and a comparison with Agile, Shape Up, and waterfall.

Install: gh skill install ajaxdude/HankNDory hankndory@v2.9 --agent github-copilot --scope user --force

Rollback: gh skill install ajaxdude/HankNDory hankndory@v2.8 --agent github-copilot --scope user --force

HankNDory 2.8

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 06:21

A status you can scan for each project.

  • LGTM: going well and on course.
  • Blocked: some part of the plan can't go on until you act. If Marlin may take the recommended path, it does, and the project isn't Blocked.
  • Issues: something unforeseen needs a fix, and it's being worked on without you.

Crush lists Blocked projects first, then Issues, then LGTM.

Install: gh skill install ajaxdude/HankNDory hankndory --agent github-copilot --scope user --force
Rollback: gh skill install ajaxdude/HankNDory hankndory@v2.7 --agent github-copilot --scope user --force

HankNDory 2.7

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 06:07

One list of everything waiting on you.

  • Crush's report lists every open item still waiting on you, across all projects, not only new ones: decisions, approvals, and tasks only you can do. New items come first, marked new, and each shows how long it has waited.
  • An item leaves the list once it is answered, withdrawn, settled by its default, or its project ends.
  • Items that are only still waiting don't trigger a report, but you can ask Crush for the current list at any time.

Install: gh skill install ajaxdude/HankNDory hankndory --agent github-copilot --scope user --force
Rollback: gh skill install ajaxdude/HankNDory hankndory@v2.6 --agent github-copilot --scope user --force

HankNDory 2.6

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 06:04

You set when Crush posts.

  • The house rules set Crush's hourly slot, by default about five minutes past the hour.
  • If the scheduler can't repeat at a set minute, Crush books one run at a time for the next slot.

Install: gh skill install ajaxdude/HankNDory hankndory --agent github-copilot --scope user --force
Rollback: gh skill install ajaxdude/HankNDory hankndory@v2.5 --agent github-copilot --scope user --force

HankNDory 2.5

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 05:58

One place to read updates, once an hour, with how far along each project is.

  • Crush posts its combined report only at its hourly slot, never in between. Urgent machine news is still sent at once.
  • Updates go to Crush by default, so Crush's report is the one place you read them. A charter can name another place.
  • The skill creates your one Crush as its own top-level conversation when none exists, and every voyage finds and uses the same one.
  • Each update gains a Progress row: about how much is done and when it should finish. Crush's table shows them as Done and Finish.

Install: gh skill install ajaxdude/HankNDory hankndory --agent github-copilot --scope user --force
Rollback: gh skill install ajaxdude/HankNDory hankndory@v2.4 --agent github-copilot --scope user --force

HankNDory 2.4

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 03:25

Two changes.

Crush, the sea turtle who knows every lane. A new role, in reference/crush.md and the new crush mode: one long-running conversation per user, not part of any voyage.

  • It routes heavy work (model loads, GPU jobs, big memory, disk, or CPU jobs) onto the machines you share across projects, under house rules only you set: limits, disk floors, what Crush does alone, what stays yours, and a freeze switch for model loading and GPU work.
  • Sessions request, get granted or held, register, and report done; standing grants cover background helpers. Each machine's own record decides. A grant is machine time, never permission.
  • It gathers every workstream's update into one report: new or changed decisions waiting on you first, each once with plain context, then a row per workstream with news, then a line per machine where something changed.

Updates only when there is news. Dory's update (Just done, Happening now, Next) is posted only when there is new progress. Waiting, "still running", and "no change" are not progress, so the hourly check stays silent.

See CHANGELOG.md for the full list.

Install: gh skill install ajaxdude/HankNDory hankndory --agent github-copilot --scope user --force
Roll back to 2.3: gh skill install ajaxdude/HankNDory hankndory@v2.3 --agent github-copilot --scope user --force

HankNDory 2.3

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 02:29

Faster by default. At every pace, Marlin now starts at once all work the charter and current approvals allow, and runs independent work side by side in several sub-agents or sessions: research, drafts, tests, reviews, and building inside approved designs. Only work that depends on a reserved answer waits for it.

  • Streams start with the user's operating limits and the reserved list, are recorded in the charter's history file, and report back to the conversation acting as Hank.
  • Building streams each get their own branch and worktree; Hank merges them into one branch for the code review.
  • New charter field: an optional limit on parallel streams.
  • The hourly update's "Happening now" row names each stream and anything waiting on the user, and why.

See CHANGELOG.md for the full list.

Install: gh skill install ajaxdude/HankNDory hankndory --agent github-copilot --scope user --force
Roll back to 2.2: gh skill install ajaxdude/HankNDory hankndory@v2.2 --agent github-copilot --scope user --force

HankNDory 2.2

Choose a tag to compare

@ajaxdude ajaxdude released this 01 Oct 02:09

HankNDory 2.2: less of a black box.

  • Dory's hourly update. While a voyage runs, every hour the user gets a three-row table: Just done, Happening now, and Next. Each cell is one or two short sentences in plain words.
  • Plain words. Nothing addressed to the user uses internal labels such as document or review numbers, step codes, item IDs, or hashes. Each thing is named instead. reference/marlin.md has a good and a bad example.
  • Ask with context. Every question starts with the recommendation. Then come two to four plain sentences: what this is, why it needs deciding now, and what each option changes in time, money, or risk. The options come last.

See CHANGELOG.md for details.

Roll back to 2.1:

gh skill install ajaxdude/HankNDory hankndory@v2.1 --agent github-copilot --scope user --force