The people who run the process should be the ones who review it.
SOPs, job descriptions, and the policies they depend on. The team flags what is stale. Agent connect updates the file.
The docs you produce now
Process docs go stale in the steps nobody updated, and job descriptions collect requirements from everyone who was in the room. The reviewers are the people who do the work, not another tool.
What you can review with Gander
Fernhollow
SOPs and process docs
The team that runs the process flags a stale step. A lead uses agent connect to remove it and renumber. Read more →
Halcyra
Job descriptions and interview kits
The team and the recruiter comment on the draft. The recruiter uses agent connect to cut the list to five must-haves. Read more →
Juniperline
Privacy policies, terms, and internal policies
Security and product read the same draft. Someone uses agent connect to fix a retention period the product does not keep. Read more →
A week with Gander
You watch a returns SOP and a job description on the same day. The warehouse lead and the hiring manager each get a link.
On the SOP, a teammate leaves a human thread on a photo step. The warehouse lead uses agent connect: "@agent we stopped doing step 5 in August, remove it and renumber." The agent edits the file and replies. On the job description, the recruiter uses agent connect to cut the requirements to five must-haves. The policy both docs point at has its own team link when legal is involved.
What you need
One person on your team runs an agent that writes markdown to a file on their machine (macOS, Linux, or Windows through WSL) and installs the Gander CLI. That person is the author. Everyone else opens the link in a browser. No install, no agent account.
Agents that fit
The process doc should be reviewed by the people who run it, on the file the agent can still edit.