| name | run-exec-plan |
| description | Write, lint, grill, execute, repair, and validate one Programmers Loop ExecPlan. Use when a bounded implementation slice needs self-contained context and deterministic acceptance commands. |
Run ExecPlan
- Read
docs/contracts/exec-plan.md and the owning Assignment or Program.
- Scaffold the plan with
programmers-loop exec-plan create --owner <path>;
Program ownership resolves and records the current brief once.
- When the source is noisy, preview and run
programmers-loop exec-plan outline --input <notes.md> --output <outline.md> --execute; inspect the durable outline.
Use --session-jsonl for an exact Codex session or --handoff for a
versioned workshop handoff instead of --input; provide exactly one source.
- Write from that outline with
programmers-loop exec-plan write --path <plan.md> --outline <outline.md> --execute, or use --handoff <handoff.json>
to render and consume a versioned workshop handoff directly.
- Run
programmers-loop exec-plan lint --path <plan.md> --ready.
- Grill it with
programmers-loop exec-plan grill --path <plan.md> --execute;
stop on a real owner question.
- Preview every acceptance command with
programmers-loop exec-plan proof --path <plan.md> and resolve rejected commands before granting consent.
- Run the complete bounded loop with
programmers-loop exec-plan run --path <plan.md> --execute --proof; add --outline <outline.md> to include writing,
or call execute and validate separately when a
human checkpoint belongs between them.
- Inspect the workflow and proof receipts under
.runtime/; record durable
discoveries, decisions, outcomes, and the post-build recap in the plan.
- Mark the plan complete and move it to the matching
completed/ lane only
after deterministic proof passes.
Do not authorize Markdown command execution implicitly. Show the commands and
apply the repository's configured token-prefix allowlist, containment, timeout,
bounded-output, and receipt boundary.
