propose-ship-auto

Automate the Minerva propose-ship lifecycle with a 3-agent consensus panel.

Updated May 16, 2026

Search Tags:#agent orchestration #PR automation #code delivery #minerva #consensus panel #work unit lifecycle #quorum voting

Ready to run

npx skills add https://github.com/honerlaw/agent-marketplace --skill propose-ship-auto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: propose-ship-auto
Source: https://github.com/honerlaw/agent-marketplace/tree/main/plugins/minerva/skills/propose-ship-auto
Command: npx skills add https://github.com/honerlaw/agent-marketplace --skill propose-ship-auto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the need for human gating in the Minerva lifecycle by running a complete propose → work → review → promote → ship → cleanup flow using consensus decisions at every strategic/tactical point.

Core Features & Use Cases

End-to-end auto orchestration: Runs the full Minerva lifecycle, with panel-based decisions replacing user gates.
3-agent consensus panels: Uses a Proponent/Skeptic/Arbiter review-and-vote mechanism at decision points, with bounded revision rounds.
Safety guardrail for real work-in-flight: Detects potentially conflicting in-progress Minerva work units and escalates to the user before proceeding.

Quick Start

Invoke minerva:propose-ship-auto with a short description of what you want to add or improve, and let it run the full lifecycle end-to-end without asking follow-up gate questions unless consensus cannot be reached after a revision round.

Frequently Asked Questions about propose-ship-auto

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

FAQPage Schema

How do I automate PR readiness and code delivery without human gating?▼

You can automate PR readiness end-to-end by deploying a 3-agent Proponent/Skeptic/Arbiter consensus panel to handle proposal, review triage, and promotion partitioning without human gating across the work unit lifecycle.

How does agent orchestration handle consensus voting for a work unit lifecycle?▼

Agent orchestration manages consensus by applying quorum-based vote semantics with bounded revision rounds at strategic and tactical decision points, escalating to the user only if consensus cannot be reached.

What happens if my automated Minerva workflow conflicts with in-flight work?▼

If in-flight work collision detection identifies potentially conflicting in-progress Minerva work units, the automation acts as a safety guardrail and escalates to the user before proceeding.

Can I use a single seed description to run the full propose-ship lifecycle?▼

Yes, you can invoke the automation with a short seed description of what you want to add or improve, and it will run the complete propose-ship lifecycle end-to-end without asking follow-up gate questions.

Does the Minerva propose-ship automation require manual cleanup phases?▼

No, the propose-ship automation delegates operational gate completion to existing minerva:ship and minerva:cleanup phases automatically, ensuring the full work unit lifecycle is resolved without manual intervention.

When should I not use an automated consensus panel for code delivery?▼

You should avoid automated consensus panels for code delivery when you need human oversight at strategic or tactical decision points, or when in-flight work collision detection cannot guarantee safe execution.