open-prose

Execute multi-agent AI programs defined in prose files.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mistakenot/auto-stack --skill open-prose-mistakenot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-prose
Source: https://github.com/mistakenot/auto-stack/tree/main/.agents/skills/open-prose
Command: npx skills add https://github.com/mistakenot/auto-stack --skill open-prose-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenProse formalizes and operationalizes multi-agent AI sessions so you can write, validate, and run reproducible workflows instead of juggling ad-hoc prompts. It solves brittle coordination, hidden state, and replayability problems by defining a manifest-driven wiring phase and a VM-driven execution phase with durable state and clear contracts.

Core Features & Use Cases

  • Forme wiring: auto-resolves services, matches requires↔ensures, and emits an executable manifest.
  • Prose VM execution: spawns subagents, enforces shape/permissions, performs copy-on-return (workspace → bindings), and logs append-only state for resumption and auditing.
  • State backends & tooling: filesystem, in-context, SQLite, and PostgreSQL options; dependency resolution via .deps and prose.lock; runtime delegation and persistent agent memory for long-lived orchestrators.
  • Typical uses: automated research pipelines, multi-agent code review and synthesis, retrospective inspections and cost/profiler analyses, and program-improver loops that propose PRs from inspection outputs.

Quick Start

Ask the assistant to run the hello-world example by saying: prose run examples/01-hello-world.md

Frequently Asked Questions about open-prose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multi-agent AI workflows reproducibly?

Multi-agent AI workflows are orchestrated reproducibly by defining them in prose files, which a manifest-driven wiring phase resolves into an executable manifest for a VM to run with durable state and clear contracts.

What is manifest-based two-phase execution for AI agents?

Manifest-based two-phase execution separates agent workflow processing into a wiring phase that auto-resolves services and emits a manifest, followed by a VM execution phase that spawns subagents and logs append-only state for resumption and auditing.

How do I run a multi-agent program defined in a prose file?

To run a multi-agent program, you ask the assistant to execute the prose file, such as by saying 'prose run examples/01-hello-world.md', which triggers the VM to spawn subagents and manage state via copy-on-return.

Can I use SQLite or PostgreSQL for multi-agent workflow state backends?

Yes, multi-agent workflow state backends support SQLite and PostgreSQL, alongside filesystem and in-context options, allowing you to persist execution state and enable resumption for long-lived orchestrators.

Why does my multi-agent AI session lose state and fail to replay?

Multi-agent AI sessions lose state and fail to replay when lacking a durable execution model, a problem solved by using append-only state logging and dependency resolution via .deps and prose.lock to enforce reproducible runs.

What is the best way to inspect completed multi-agent runs for cost analysis?

The best way to inspect completed multi-agent runs for cost analysis is using retrospective inspection tools that analyze the append-only state logs and profiler outputs generated during the VM-driven execution phase.