Author a Pack with an AI Coding Agent

If you can describe, in your own words, the process you want — what steps it goes through, who's responsible for each one, and what needs approval — an AI coding agent can turn that description into a working pack. You won't write any code. The only thing it can't do for you is the very last step: uploading the finished pack, which happens in your web browser, in Settings → Platform → Packs.

What is an AI coding agent?

An AI coding agent is an AI assistant that goes beyond a chat window — it can also read and write files, and run small programs on your computer. So instead of just replying with an answer, it can actually go and do the work: writing the pack's files, running the tools that check and build them, and fixing its own mistakes if something goes wrong. It's the same process a developer would follow by hand — you just don't have to be the one doing it.

Several tools work this way, including:

• Claude Code — Anthropic's agent, available in a terminal, IDE, desktop app, or browser.
• Cursor — a code editor with a built-in agent.
• GitHub Copilot, in VS Code's Agent mode.
• OpenAI Codex — runs in a terminal or IDE.
• Gemini CLI — Google's terminal-based agent.

Use whichever one you already have, or already trust for this kind of work — every step below works the same way regardless of which agent you pick.

Before you start

1. An AI coding agent, installed and signed in. Any of the tools listed above works — follow that tool's own setup instructions; it typically takes a few minutes.
2. Access to Scrydon's Settings → Platform → Packs, so you can do the upload at the end. You'll need admin rights on the Scrydon organization you're uploading to — if you're not sure whether you have this, ask your Scrydon administrator.

That's genuinely everything. You don't need to know how to code, and you don't need to understand any of the technical terms that show up on this page — your agent handles all of that.

Step by step

mkdir customer-onboarding-pack
cd customer-onboarding-pack
claude

Prompt template

You don't need to understand the text below — it's written for your AI coding agent, not for you, and it looks more technical than anything you'll actually have to do. Just copy the whole thing, paste it into your agent from Step 1, and replace the parts in [brackets] with your own description, in your own words.

I want to build a Scrydon Pack containing a Process Flow (and an Ontology if
one is needed) using @scrydon/sdk-authoring. I don't write code myself —
please do the implementation, run the build, and fix any validation errors
yourself. Explain what you built in plain English when you're done, before
I upload it.

Ground yourself first — fetch these docs pages before writing anything:
- https://docs.scrydon.com/sdks/authoring for the overall pack lifecycle
  (define → validate → bundle → upload).
- https://docs.scrydon.com/sdks/authoring/process-flows for the Process
  Flow SDK (stages, tasks, personas, action templates).
- If the process needs a data model, also fetch
  https://docs.scrydon.com/sdks/authoring/ontologies.
- https://docs.scrydon.com/sdks/authoring/process-flows/examples for a
  complete, working pack shape to follow.

Here is the process I want, described in plain language:

[Describe the process end to end. For example:
 "A customer-onboarding kickoff. It has three stages: Discovery, Setup,
 and Go-Live. In Discovery, the Customer Success Manager fills out a
 checklist and uploads the signed contract. Discovery moves to Setup once
 that's done. In Setup, the Customer Champion approves a rollout plan
 document — this needs a manual approval, not automatic. Once approved,
 Go-Live starts and just has one task: a final confirmation checklist
 assigned to the CSM."]

Roles involved: [e.g. "Customer Success Manager", "Customer Champion"]

When you're done:
1. Run `bunx @scrydon/sdk-authoring pack validate . --manifest-only`, then
   `bunx @scrydon/sdk-authoring pack build .`, and fix anything that fails.
2. Tell me the exact filename of the built .tar.gz.
3. Summarize the stages, tasks, and approvals you created — no code, plain
   English — so I can confirm it matches what I asked for before I upload it.

Uploading your pack

This is the one step you do yourself, in your browser — here's exactly what it looks like.

Your pack now appears in the list on the Packs page. From there, a workspace admin adds it to an environment from the Marketplace — after that, it's ready for anyone to use from Process Flows.

Updating a pack later

Wanting to change something later — add a step, tweak who's responsible for a task, fix a typo — doesn't mean starting over. Go back to your agent, in the same folder you used before, and describe the change the same way you described the process the first time.

A few things worth knowing before you do:

• Ask your agent to bump the pack's version number (for example, from 1.0.0 to 1.0.1) before it rebuilds. Scrydon tells one version of a pack apart from another by that number, not by the filename — if it doesn't change, Scrydon won't recognize the new file as an update.
• Upload the new file the same way — Settings → Platform → Packs → Upload pack, exactly like the first time.
• What happens next depends on what's in your pack:
  • If it's just a Process Flow, the new version goes live automatically the moment it's uploaded — there's nothing else to click.
  • If it also includes an Ontology (a data model) and you changed something that already existed, the pack will show as Update available in the list — click into it, then click Update pack to apply that part.

What your agent does, and what's still yours to do

• Your agent handles: writing every file, running the technical build and validation steps, and fixing its own mistakes. You never write code, never learn a file format, and never type a build command yourself.
• Still yours to do: uploading the finished file in your browser (your agent has no way to log into Scrydon), turning the template on for your workspace via the Marketplace, and — most importantly — checking that what it built actually matches what you asked for. Always read the plain-language summary from Step 4 before you upload.
• Your agent cannot touch your Scrydon account at all. It only ever works with files on your own computer and the small tools it installs there.

Where to next

These go deeper into how packs actually work — nothing here is required to get your first pack built, but they're useful if you're curious or want to fine-tune something later.