Release Manager
Gets each release ready: a readiness checklist with a go or no-go call, the changelog entry and plain-language release notes from merged pull requests, and a s…
Starter catalog · engineering
Template source · Subscribe: JSON Feed · Update subscriptions
This is public source history at 3326d161b836. Changes on main may not be released or installed on your team. Entries are commit summaries, not claims that a bot has updated itself. Check published releases for availability.
Changelog
Approvals: sweep backlog test, refuse asks on ended tasks, match recipients loosely
playbooks/rollout.md
Bot instructions: mail sending is turned on in Tico by a person; bot.yaml only asks (#351)
AGENT.mdbot.yaml
Only unrelated history holds a bot's turns; scrub tokens from turn failures
software/rollout.py
Engineering bots write plain notes, ask real people, and release one way
AGENT.md
Bot moves, template clones, reserved credential names, turn failure causes
bot.yamlknowledge/rollout.example.jsonplaybooks/rollout.mdsoftware/rollout.py
Fix main: Usage after Runs with Learnings between; no company name in the release-notes template (#137)
bot.yaml
Update-scoped service keys and the Release Manager's rollout (#129)
.claude/settings.jsonAGENT.mdbot.yamlcard.yamlknowledge/rollout.example.jsonplaybooks/rollout.mdsoftware/.gitkeepsoftware/rollout.py
Add task tags, templates and versioned tag APIs
playbooks/release-readiness.md
Docs: Credentials and grants everywhere, current menu paths, architecture and harness corrections, regenerated screenshots
.env.example
Bots, tasks, routines and runs: template bots build, Reopen and Undo, event routines keep their trigger, 24h windows, SQL Docs/Files; starters act without required approvals
AGENT.mdbot.yamlcard.yamlplaybooks/onboarding.mdplaybooks/weekly-release-notes.md
Bot instructions and docs use the new tool, command, file and route names
AGENT.mdknowledge/README.mdplaybooks/onboarding.mdplaybooks/release-readiness.mdplaybooks/weekly-release-notes.md
Bot files and settings: bot.yaml, routines:, tools:, HUB_BOT, needs_setup, groups.yaml, bot-<slug>
bot.yamlcard.yaml
MCP tools and hub CLI: hub_<thing>_<action> names, per-caller tool lists, hidden old spellings
bot.yaml
Bot templates words: team, human, setup, computer, credential
.env.exampleAGENT.mdcard.yamlemployee.yamlknowledge/README.mdknowledge/examples/release-notes.mdplaybooks/classify-a-change.mdplaybooks/onboarding.mdplaybooks/weekly-release-notes.mdstate.md
Setup turns the bot on: the first routine goes on with Start setup and go-live
AGENT.mdcard.yamlemployee.yamlplaybooks/onboarding.mdstate.md
Catalog: the Engineering department
.claude/settings.jsonAGENT.mdcard.yamlemployee.yamlplaybooks/release-readiness.md
Catalog: Engineering pack adds Engineering Lead, PR Reviewer, Release Notes, Incident Scribe, Docs Writer and Product Researcher
.claude/settings.json.env.example.gitignoreAGENT.mdcard.yamlemployee.yamlknowledge/README.mdknowledge/examples/release-notes.mdmemory/decisions.mdmemory/learnings.mdplaybooks/README.mdplaybooks/classify-a-change.mdplaybooks/onboarding.mdplaybooks/weekly-release-notes.mdreports/.gitkeepskills/.gitkeepsoftware/.gitkeepstate.md