Scripting in .md — a new paradigm

Your
Procedures,
Executable.

Agents are flexible but get it wrong. Automations work but have no flexibility or situational awareness. Storyline Director does both without compromise.

Try it now See how it works →
scroll
Live builder preview

See it run.

A real estate agent's post-showing workflow — scripted in .md, executed step by step. Checkpoints hold for your approval before anything sends.

post-showing-followup.md ↗ Live builder coming soon
Skill source · .md
# Post-Showing Follow-Up ## Context After each showing, process voice notes into a follow-up email, CRM update, and optional call flag. ## Step 1: Read voice note Transcribe and extract key details: prospect name, property, reactions, questions asked, stated timeline. ## Step 2: Pull CRM record Fetch the prospect and listing from CRM. Match by name + showing date. ## Step 3: Draft follow-up email Write a warm, personalized email. Reference specific details from notes. Mention school district if kids noted. WAIT Present draft email to agent. ASK: "Send this, edit it, or skip?" WAIT for explicit approval before sending. ## Step 4: Update CRM notes Log a structured note: reactions, questions, any objections raised. ## Step 5: Flag for follow-up call? If prospect mentioned a timeline or asked detailed financing questions — STOP and flag with reason. Else, mark as follow-up in 2 weeks.
Execution output
STEP 1 · Read voice note ✓ done
Transcribed 2m 14s of audio.
Prospect: Sarah & Tom Henderson
Property: 42 Birchwood Lane
Notes: Loved the kitchen. Asked about school districts. Tom mentioned wife starts new job in March.
STEP 2 · Pull CRM record ✓ done
Record found: Henderson, Sarah
Listing linked: 42 Birchwood Lane
Last contact: 3 days ago.
STEP 3 · Draft follow-up email ⏸ awaiting approval
To: sarah.henderson@email.com
Subject: Great meeting you at Birchwood

Hi Sarah — it was wonderful showing you 42 Birchwood today. I know you mentioned the school district matters — Birchwood feeds into Maplewood Elementary, rated 9/10...
WAIT Approval required before email sends
The paradigm shift

A new kind of automation.

01
Script It

Write your procedure in plain .md. Natural language where judgment matters. Control-flow primitives where precision does. If a step needs a decision, say so.

→ Your words. Your logic.
02
Run It

Claude is the runtime. Your markdown is the program. It handles the ambiguous parts that would break any conventional automation — and follows the structure you set where it matters.

→ Claude executes. You author.
03
You Decide

WAIT gates pause execution. ASK surfaces a decision. STOP requires your explicit go-ahead. Nothing consequential happens without your say-so.

→ Human in the loop, by design.
Real work, transformed

Who it's for.

Any professional with a repeatable process and a need for judgment at the right moments.

Recruiter
Before 12 manual steps from candidate intake to scheduled interview — copy-paste, tab-switching, easily dropped.
After One approved workflow. Candidate data pulls automatically; you approve the outreach before it sends.
12 → 1
steps to a scheduled interview
Support Lead
Before Ticket triage varies by rep. New hires handle edge cases differently. Inconsistency erodes trust.
After Your team's best judgment, codified and executable. Every ticket handled the way your best rep would handle it.
Consistent.
every rep, every ticket
Compliance Manager
Before A vendor risk review wiki that nobody follows. Evidence gathering is manual, inconsistent, and undocumented.
After An executing procedure with a built-in audit trail. Every step logged, every checkpoint signed off.
Audit-ready.
every run, automatically
Your learning curve

Start in minutes. Scale to developer-level power.

1
Visual Builder

Describe your workflow in plain language. Storyline Director structures it into a runnable skill. No syntax required.

For everyone
2
Edit the .md

Flip to source. Tune the checkpoints, tighten the instructions, add branching conditions. Plain text you can read and reason about.

For the curious
3
Full Scripting Power

Branch on context. Fan out sub-procedures. Write embedded rubrics and self-verification steps. The same format, developer-level results.

For power users