delivery-judgment-playbook

Name: delivery-judgment-playbook
Availability: InStock
Author: aurora-atoms

Generate structured, versioned playbooks from feature delivery case evidence.

Updated Jun 1, 2026

Search Tags:#playbook #compliance #governance #evidence #delivery #decision-making

Ready to run

npx skills add https://github.com/aurora-atoms/lattice --skill delivery-judgment-playbook

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: delivery-judgment-playbook
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/delivery-judgment-playbook
Command: npx skills add https://github.com/aurora-atoms/lattice --skill delivery-judgment-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of inconsistent decision-making in delivery teams by capturing repeatable judgments into structured, evidence-backed playbooks that define clear criteria and accountability.

Core Features & Use Cases

Evidence-Based Playbook Generation: Transforms historical delivery cases, incidents, and outcomes into versioned, actionable playbooks.
Governance Guardrails: Establishes mandatory steps, failure signals, and exception paths to ensure compliance without removing human authority.
Use Case: A team frequently struggles with whether to trigger a security review for specific feature types. Use this Skill to analyze past successful and failed delivery cases to generate a standardized playbook that dictates exactly when a review is required and who must approve it.

Quick Start

Use the delivery-judgment-playbook skill to analyze the provided feature delivery cases and generate a candidate playbook for our release approval process.

Frequently Asked Questions about delivery-judgment-playbook

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

FAQPage Schema

How do I standardize delivery decisions for consistent governance across multiple teams?▼

Evidence-based playbook generation transforms historical delivery cases and outcomes into versioned, actionable playbooks. It extracts repeatable judgments from past incidents to define clear criteria and accountability for future feature delivery.

What is the best way to create a release approval playbook from past feature delivery cases?▼

Creating a release approval playbook requires analyzing bounded input sets of past delivery decisions, outcomes, and accountable roles. The Skill synthesizes this historical evidence to generate reviewable playbook candidates with mandatory steps and failure signals.

Do I need historical delivery data to generate a governance playbook?▼

Yes, generating valid playbook candidates requires bounded input sets of historical delivery decisions, outcomes, and accountable roles. Without past feature delivery cases and incidents, the Skill cannot synthesize evidence-backed governance guardrails.

How do compliance playbooks handle exception paths and human authority in risk management?▼

Compliance playbooks establish governance guardrails with mandatory steps, failure signals, and exception paths. They ensure consistent risk management without removing human authority by defining when reviews are required and who must approve exceptions.

Can I version and review operational playbooks as delivery team processes evolve?▼

Yes, generated playbooks are structured and versioned, allowing teams to review and update operational workflows as delivery processes evolve. This ensures governance criteria and accountability remain aligned with current risk management requirements.