customer-support-agent.md
Current version: v12
Workflow rule
Escalate refund requests over £500 before drafting a customer response.
Comments
8 open threads
Review links
Stakeholder review
AI-ready
Clean Markdown
AI workflow Markdown
Manage AI workflow Markdown without forcing everyone into GitHub.
Edith gives AI-forward teams one place to review, version and share the Markdown behind prompts, agents, SOPs, product specs and internal AI processes.
The problem
The review process is scattered.
AI workflows increasingly depend on Markdown, but the review process is scattered across GitHub, AI chats, Google Docs, Slack and exported files.
What teams put in Edith
Markdown that people and AI both need.
prompts
agent instructions
coding-agent specs
workflow definitions
SOPs
support playbooks
review checklists
product specs
implementation plans
policies AI tools need to follow
Workflow
How the workflow works.
01
Draft with AI.
02
Save in Edith.
03
Share a review link.
04
Collect comments and suggestions.
05
Apply accepted suggestions.
06
Save a new version.
Continue from the current Markdown through AI, the API, an export or a share link.
Why not GitHub?
GitHub is great for developers, but many AI workflow reviewers are not developers.
Why not Google Docs?
Google Docs is familiar, but it does not preserve clean Markdown as the working source.
Why Edith?
Edith keeps the Markdown clean, reviewable, versioned and ready for humans or AI tools.
Start small
Start with one AI workflow document.
Bring one prompt, agent instruction, SOP or workflow definition into Edith and collect review around the current Markdown.