evidence-based-decision-packets

Structures evidence gathering and approval packets for gated project decisions.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills --skill evidence-based-decision-packets-military-veteran-team-lpt-realty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence-based-decision-packets
Source: https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills/tree/main/skills/evidence-based-decision-packets
Command: npx skills add https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills --skill evidence-based-decision-packets-military-veteran-team-lpt-realty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Major decisions like deployments, rollbacks, and credential changes often get approved on assumptions rather than facts, leading to reversals and outages. This Skill enforces a workflow where all evidence is gathered first and presented in one structured packet before any approval is requested. ## Core Features & Use Cases - Evidence Gathering Checklists: Domain-specific checklists for code changes, deployments, rollbacks, and credential changes covering SHAs, gate results, CI runs, and rollback paths. - Structured Decision Packet Format: A standardized Markdown template presenting proposed action, evidence table, risks, rollback steps, and the exact approval phrase required. - Approval Gate Enforcement: Blocks execution until the approver provides the exact approval phrase, and requires explicit acknowledgment when evidence is incomplete. - Use Case: Before promoting a deployment to production on Netlify, compile gate results, mirror parity, health checks, and a confirmed rollback deployment ID into a packet, then wait for the approver's exact phrase before publishing. ## Quick Start Ask the AI to prepare an evidence-based decision packet for your pending deployment, including gate results, rollback path, and risks, before requesting approval.

Frequently Asked Questions about evidence-based-decision-packets

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

FAQPage Schema
How do I present a deployment decision for approval with evidence?

Gather the source SHA, gate results with exit codes, CI run URL, mirror parity status, and a confirmed rollback deployment ID. Present them in the decision packet template with risks, rollback steps, and the exact approval phrase, then stop until approval is given.

What evidence should I collect before approving a production deployment?

Collect the deployment ID or URL, a health check returning HTTP 200 from the production URL, confirmation that environment variables are set, and DNS resolution status. Also verify the rollback target and its CI status before requesting approval.

Does this approval workflow work with Netlify instead of Vercel?

Yes, the skill notes that deployments go from GitHub to Netlify. Map Vercel concepts to Netlify equivalents: preview deployments become deploy previews, promotion becomes Publish deploy, and instant rollback means publishing a previous deploy.

What happens when evidence cannot be gathered before a decision?

Present what is known and explicitly mark unknown items, such as an unreachable repo or unavailable CI run. The packet must state the known and unknown risks, and proceeding requires explicit acknowledgment of the uncertainty from the approver.

Why is an exact approval phrase required instead of a simple yes?

Implied consent is not sufficient for irreversible actions. If the approver says yes or go ahead without the exact phrase, the workflow asks for confirmation with the exact phrase to prevent accidental authorization of significant changes.