skills.rest
aurora-atoms
aurora-atomsCOMMUNITY
Explore all skills by this author →
GitHub

delivery-verdict-author

Assess feature delivery readiness using validation results and evidence records.

Updated Jun 1, 2026
Search Tags:#validation#compliance#governance#evidence#delivery#verdict
One-click install
npx skills add https://github.com/aurora-atoms/lattice --skill delivery-verdict-author
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delivery-verdict-author
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/delivery-verdict-author
Command: npx skills add https://github.com/aurora-atoms/lattice --skill delivery-verdict-author

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves ambiguity in feature delivery by providing a standardized, evidence-based verdict on whether a feature is truly ready for user consumption.

Core Features & Use Cases

  • Evidence-Based Assessment: Evaluates feature specs, task packets, and validation results against defined acceptance criteria.
  • Standardized Verdicts: Outputs clear status enums like usable, not_user_usable, or requires_human_review to streamline downstream routing.
  • Use Case: Use this to automatically verify if a feature is ready for release by comparing test results and PR evidence against the original feature specification.

Quick Start

Use the delivery-verdict-author skill to assess the readiness of the current feature delivery case by providing the relevant evidence records.

Frequently Asked Questions about delivery-verdict-author

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

FAQPage Schema
How do I automate feature delivery readiness assessments using evidence?▼

Automate feature delivery readiness by synthesizing feature specifications, task packets, and validation results against acceptance criteria to output a standardized verdict like usable or requires_human_review.

What is evidence-grounded governance for software delivery?▼

Evidence-grounded governance for software delivery determines production readiness by citing specific validation records and delivery evidence, ensuring release decisions are strictly tied to documented feature specifications and test results.

How do I standardize release verdicts to route features downstream?▼

Standardize release verdicts by evaluating delivery evidence and outputting strict status enums like not_user_usable or requires_human_review, streamlining downstream routing for human intervention or automated production release.

Can I assess production readiness without manual review of every pull request?▼

You can assess production readiness automatically by comparing pull request evidence and validation results against original feature specifications, only triggering human review when the synthesized evidence fails to meet acceptance criteria.

When do I need a standardized verdict taxonomy for feature delivery?▼

You need a standardized verdict taxonomy for feature delivery when resolving ambiguity in release readiness, ensuring that automated assessments output consistent statuses like usable or requires_human_review for reliable downstream governance.

What limitations exist when validating feature delivery status using automated evidence synthesis?▼

Automated evidence synthesis for validating feature delivery status operates strictly within feature delivery cases and cannot assess readiness without explicit evidence records, task packets, and feature specifications provided as input context.

Related Skills

Explore More Software Engineering Skills→
aurora-atomsaurora-atoms

task-packet-builder

Convert feature delivery cases into structured task packets with validation commands.

Community
Advanced
jpicklykjpicklyk
200

Dependency Analysis

Analyze Task Orchestrator dependencies to identify blocked tasks and bottlenecks.

Community
Advanced
aurora-atomsaurora-atoms

silent-risk-accumulator

Detect and map interacting delivery risks from exceptions, gaps, and deferred decisions into an evidence-linked combination map.

Community
Advanced
0xmariowu0xmariowu
4

ship

Analyze git status, test results, and verification evidence to determine release readiness.

Community
Intermediate