FlowScript tests ordered execution for Markdown agent skills
FlowScript is a small prototype for writing in Markdown while making a separate harness enforce the execution order. Markdown ages are easy for people to write, review, and give to agents, but the actual execution can be loose. A model may skip a step, run a helper script too early, summarize before required artifacts exist, or handle failures in uneven ways.
Workflow engines can control execution, but they often move the writing experience away from Markdown . FlowScript keeps the human-readable SKILL.md file and adds a FLOWSCRIPT.md file with a flow block that the harness can read. The harness loads and checks the declared flow, then runs , validator, and steps in order.
It only follows declared branches, saves artifacts instead of depending on hidden chat state, and records a skill_agent_context for replay and inspection. If it reaches an unsupported ending or fallback path, it stops with logs and partial artifacts.
Key points
- Markdown are easy to write but can be executed inconsistently by a model.
- FlowScript keeps SKILL.md and adds FLOWSCRIPT.md for the declared flow.
- A harness runs , validator, and steps in order.
- Artifacts are saved so the run does not depend only on hidden chat state.
- Unsupported endings or fallback paths stop with logs and partial artifacts.