Documentation Agents
Agents for auditing and fixing markdown documentation in this workspace. They enforce content rules, check links and accuracy, and apply changes only after human approval via the queue in .cursor/plans/docs-agent-queue/.
When to use: Before shipping doc changes, when refreshing stale pages, or when you want a consistent audit trail for edits.
Agents in this category
| Agent | Workspace | MCP required | Purpose |
|---|---|---|---|
| Docs Page Auditor | Full (TechStackMain) | None | Audits any markdown page, writes audit + proposed draft to queue |
| Docs Page Fixer | Full (TechStackMain) | None | Applies approved drafts to source files with backups and verification |
| Agent Improver | Full (TechStackMain) | None | Researches workspace and improves agents by adding missing context; 30-day cooldown |
| Plans Hygiene | Full (TechStackMain) | None | Archives old queue outputs, reports on .cursor/plans/ health |
All agents require local access to docs, rules, and the queue folder. They are not MCP-only.
Related documentation
- Content Editing Prompt – content rules and source-of-truth mapping
- Repository Structure – where docs live and how sync works
- Cursor – Project Rules and Workspace Agents setup
.cursor/plans/README.md– plans folder structure and retention (in repo root)