Share specs with your team or coding agent
Hand off a published version of your product specs to people and coding agents.
Once your specs are written and published, the people and tools working from them need the same version — not a chat history they have to piece together. OriginAI gives you a few ways to share a published release, each suited to a different audience.
Choose how to share
A coding agent that can open a URL. Use the plain-text (Markdown) export from the publish result. It usually requires no login, and for agents the full text is more reliable than a rendered preview page alone.
A coding agent working in a repository already linked to OriginAI. Give it an implement prompt, or let it read the published release through the CLI. This fits teams that develop in that repository over the long term.
A person. Send the preview link. If a coding agent also needs the full depth of the specs, attach the plain-text export alongside it.
Share a published release
- Open the project's release history.
- Select the version you want to share.
- Copy the plain-text prompt, the implement prompt, or the preview link.
- Send it to your teammate or coding agent.
Whenever the product changes, publish again and share the new version rather than editing an old handoff. If a coding agent proposes the spec change, that write is a change request you apply first, then publish.
Public preview links use your username and the project's resource name (spec.getoriginai.com/<username>/<slug> for the latest public release, or add /<hash> to pin one snapshot). UUID paths still work. Change the resource name in project settings if you want a different URL.
Example: plain-text prompt
Use this when handing specs to an agent that can fetch a URL:
Please read the published product specs (plain text; usually no login required):
Full text: https://spec.getoriginai.com/<username>/<project-slug>/<version-hash>/llm-full.txt
Index: https://spec.getoriginai.com/<username>/<project-slug>/<version-hash>/llm.txt
Latest: https://spec.getoriginai.com/<username>/<project-slug>
Read them fully before discussing implementation or review.
Do not infer product behavior from chat history alone.Example: when the repository is already linked
Use this when the agent already has the project linked in its working repository:
Please read the specified (or latest) published release for the OriginAI project
linked to this repo, implement or change the code to match the specs,
then update the sync pointer following our team's practice.Sharing documentation pages with agents
Every page in this documentation has an agent-readable Markdown version. You don't need to copy-paste by hand — just append /content.md to the llms.mdx/docs/ URL path.
For example, the page at:
https://getoriginai.com/docs/en/guides/quickstartis available as Markdown at:
https://getoriginai.com/docs/llms.mdx/docs/guides/quickstart/content.mdThere are also two bulk exports for agents that want the whole documentation at once:
| URL | What it returns |
|---|---|
https://getoriginai.com/docs/llms.txt | A plain-text index of all documentation pages. |
https://getoriginai.com/docs/llms-full.txt | The full text of every page, concatenated. |
These are designed for coding agents and LLMs — they're plain text with no login required, so an agent can fetch them directly.
Troubleshooting
| Situation | What to try |
|---|---|
| The plain-text link fails | Confirm that version's export finished successfully. |
| The content looks stale | Use the new version's link, or re-read that specific version. |
| The preview looks fine but the agent misunderstands it | Prefer the full plain-text export over the preview page. |
| You need to change the specs | Edit in the workbench — or apply a change request — then publish a new release and share it again. |