Ship a change
The loop every piece of work follows, from branch to merged PR, with the records that keep a repo ready for the next agent.
Every change, however small, goes through the same loop. It keeps each repository ready for another agent or person to take over with no context.
Before you start#
- Run
git status -sb. If another session works in the same folder, make your own worktree:git worktree add ../<Repo>.<task> -b <branch> origin/main. - Read the repo's
AGENTS.md, and the knowledge page for each technology involved. - Check for a skill that covers the job.
While you work#
- Test it yourself before asking anyone: run it, play-test it, or check it in a browser at desktop and phone width.
- If a skill step was wrong, fix the skill as part of the task.
Before you merge#
- Add an entry to
release-notes.json, then runnode tools/changelog.cjs. - Update
roadmap.json(status, evidence with links), then runnode tools/roadmap.cjs. - Update
README.mdandAGENTS.mdif behaviour or layout changed. - If the project has a site, run its sync with
--check. - Commit on the branch, open a PR, and merge once verified. The owner has approved agents merging verified work; ask first before force-pushes, history rewrites or deleting anything the owner made.
After#
- Anything you learned that applies beyond this project becomes a lesson or a skill fix in Agent-Toolkit, the same day.
See also: repo-handover, roadmap-upkeep, release-and-changelog.