envelope

Author, approve, and export execution envelopes for AFK work slices as validated bundles.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill envelope-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: envelope
Source: https://github.com/sandsower/beislid/tree/main/skills/envelope
Command: npx skills add https://github.com/sandsower/beislid --skill envelope-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning approved plans into work that a separate, cheaper agent session can execute unattended requires packaging every slice with self-contained prompts, autonomy boundaries, proof requirements, and dependencies. Doing this by hand is error-prone and produces bundles that fail at runtime. ## Core Features & Use Cases - Envelope authoring: Drafts one execution-envelope-v0 per AFK-candidate slice with autonomy allow/ask/deny lists, proof requirements, pause conditions, dependencies, and a self-contained runner prompt. - AFK eligibility rubric: Judges every slice against a versioned rubric (bounded scope, probed gate commands, resolved dependencies, mechanical success criteria, no design decisions, git-reversibility) and demotes unverifiable slices to human-in-the-loop. - Approval and export: Collects explicit per-envelope human verdicts, then writes, validates (beislid export validate), checkpoints, and commits an approved-slice-plan-export-v0 bundle under .beislid/exports/ for rondo run-once to execute. - Revision mode: Rewrites an existing bundle in place as version N+1 with a supersedes hash chain and delta-only re-approval when delivery feedback arrives. - Use Case: After breaking a multi-ticket feature into slices, run /envelope in a strong-model session to produce a validated, repo-committed bundle that a cheaper runner session executes later with zero additional context. ## Quick Start Invoke /envelope with a ticket id, an approved Work Contract or spec file path, or a batch of tickets to author and export execution envelopes.

Frequently Asked Questions about envelope

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

FAQPage Schema
How do I export approved work slices for unattended agent execution?▼

Invoke /envelope with a ticket id, approved Work Contract, or batch of tickets. The skill drafts one execution envelope per AFK-eligible slice, collects explicit per-envelope approvals, then validates and commits the bundle under .beislid/exports/ for rondo run-once to execute.

What makes a work slice eligible for AFK execution?▼

A slice must pass every criterion in the versioned AFK rubric: bounded explored file scope, probed gate commands, resolved dependencies, mechanically verifiable success criteria, no remaining design decisions, and git-reversible effects. Any unverifiable evidence demotes the slice to human-in-the-loop.

Can I revise an already exported envelope bundle?▼

Yes. Passing an exported manifest with delivery feedback triggers revision mode, which rewrites the same bundle directory as version N+1 with a supersedes hash of the prior bundle. Only changed or new envelopes require re-approval; unchanged approved envelopes carry their original approval metadata forward.

Does the envelope skill execute the work it packages?▼

No. The skill only plans, packages, validates, and exports envelopes; execution is handled by an external runner such as rondo run-once. It also never auto-routes from other skills and requires explicit user invocation.

What happens if no envelopes are approved during a run?▼

The run fails closed: no bundle is written, no checkpoint is recorded, and no commit is made. The skill prints a verdict summary and recommends running demoted slices interactively through the kickoff skill instead.