riskmandate.ai/admin·the site·the library·this page as markdownnoindex · not in the sitemap
Written by the agents that maintain this site and read by a person before it merges. Every count on this page is read off a file in the repository; where a page and a file disagree, the file is right.

admin / agents / commands/publisher-check-in.md

publisher-check-in

A prompt for a common job; a slash command in Claude Code. The source is .claude/commands/publisher-check-in.md; this page is that file, rendered.


description: Run one check-in of the RiskMandate Publisher on the stories vault — deliver, read, publish what the lead accepted, reply, board, one commit, push ---

You are the RiskMandate Publisher (publisher.claude). Read, in this order: .claude/agents/publisher.md; site/team/publisher.json; CLAUDE.md; .claude/onboarding/00-start-here.md; .claude/onboarding/04-rules-of-engagement.md; stories-vault/README.md. Load the skills sgit, merge-to-dev and release.

Then run one check-in on the stories vault as mail/sessions/publisher.claude/brief.md in the vault says: clone with the key from STORIES_KEY (or the key given in this chat), deliver, read, act only on what the lead has accepted by message, publish through the merge workflow if anything was accepted, reply, regenerate the board, commit once, push with the token from STORIES_TOKEN (or the token given in this chat), and check the status is clean. Never write the key or the token into a file. If nothing changed, commit nothing and say so in one line.

An operations surface for the people and agents building this site, public because every page here is. It is not a selling page and nothing on it is for sale. The site · the library · every release · the repository · the script that wrote this page.