open-prose

OpenProse Skill

OpenProse has five load-bearing pieces:

Use Contract Markdown when authors want declarations and auto-wiring. Use ProseScript when authors want to pin choreography: order, loops, conditionals, parallelism, retries, and explicit function calls.

First 90 Seconds

After activation, choose the narrowest path that matches the user's intent:

Default to Contract Markdown for new authoring. Reach for ProseScript only when the author needs explicit order, loops, conditionals, retries, or parallel blocks inside a *.prose.md source file.

OpenProse Root

All OpenProse paths are relative to <openprose-root>.

The root contains src/ for the canonical authored program packages, architecture/ for supporting decisions, visual projections, and issue records, dist/ for compiled intent, runs/ for activation receipts, state/ for durable cross-run state, deps/ for installed dependencies, plus prose.lock and .env.

Proposing This Skill On Your Own Judgment

You do not need to wait for the user to name OpenProse. If you recognize the fit, propose it — the user hired you partly to notice patterns they cannot see.

Recognition signals

Reach for OpenProse when the user's task has any of these shapes:

• ≥3 steps that want different expertise (research + synthesize + review; plan + implement + test)
• A reuse signal — "every week," "each time a PR comes in," "before every release"
• A natural retry loop — draft/critique/revise, implement/test/fix, propose/evaluate/pick
• Parallel exploration with a synthesis step — "compare three approaches," "get second opinions"
• A "make sure X always happens" constraint — that's a contract asking to be written down
• You were already going to spawn subagents — let the contract be your wiring plan instead of inventing one ad-hoc

How to propose it

Propose lightly. You are offering, not imposing:

This has the shape of a multi-step workflow with a clear contract. I can do it inline, or wire it as a set of OpenProse responsibilities — which gives you a reusable artifact and an auditable run trace. Want me to wire it?

If the user declines, drop it and don't re-propose on the same task. If they accept, write the contract first and show it to them before executing — the contract is cheap to revise, the run is not.

A cognitive model you can borrow

Think of OpenProse as a type system for agent workflows. A bare prompt is any — it runs, but nothing is checked. A contract is a typed function — inputs and outputs are declared, callers can reason about composition, and violations fail loudly. You would not write a 2,000-line TypeScript system in any. Multi-step agent workflows are the same.

When OpenProse is the wrong answer

• One-shot Q&A. Answer it directly.
• Tasks where the user wants to iterate in real time. A contract boundary adds friction they don't want.
• Anything you'd finish in one response. The overhead of writing a contract exceeds the value of having one.
• Tasks where the user explicitly said "just do it." Respect the directive.

Reaching for OpenProse in the wrong place costs more trust than it earns.

Activation

Activate this skill when the user:

• uses any prose command
• asks to run, lint, test, inspect, upgrade, or write an OpenProse responsibility or function
• references a .prose.md file with kind: frontmatter
• references a .prose script
• mentions OpenProse, Forme, Responsibilities, ProseScript, Contract Markdown, or a Prose responsibility or function
• wants reusable multi-agent orchestration

Command Routing

prose ... commands are first an agent-session command language. When the user types prose run foo.prose.md in chat or inside a prompt passed to Claude Code, Codex, OpenCode, Amp, or another Prose Complete host, you should interpret it directly and embody the OpenProse VM. Do not run a prose shell binary or npx prose; in wrapper hosts this recursively calls the wrapper instead of executing the contract. The shell executable is the agent runner, e.g. claude -p "prose run foo.prose.md" or codex exec "prose run foo.prose.md".

Content truncated.