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

delivery-readiness-card

Aggregate ticket, PR, and test evidence into readiness cards with gaps and next actions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented delivery status by consolidating technical evidence into a single, human-readable readiness card that highlights exactly what remains before a feature can be safely released.

Core Features & Use Cases

  • Evidence-Linked Status: Automatically synthesizes ticket, PR, and test data into a clear readiness state.
  • Gap Identification: Explicitly maps missing evidence, dependencies, and risks to specific owners and next actions.
  • Use Case: Use this during release-candidate preparation to provide stakeholders with a transparent, evidence-backed answer to whether a feature is ready for production or what specific gaps must be closed first.

Quick Start

Use the delivery-readiness-card skill to generate a status report for the current feature delivery case and save it to the artifacts directory.

Frequently Asked Questions about delivery-readiness-card

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

FAQPage Schema
How do I generate an evidence-based delivery readiness card for release candidates?▼

To generate a delivery readiness card, aggregate ticket, PR, and test evidence into a single status report that identifies gaps and next actions. This provides stakeholders with a transparent, evidence-backed assessment of whether a feature is ready for production.

What is the best way to consolidate fragmented feature delivery status for stakeholders?▼

Consolidating fragmented delivery status involves synthesizing technical evidence from tickets, PRs, and tests into a human-readable readiness card. This explicitly maps missing dependencies and risks to specific owners for clear release governance.

How do I identify gaps and blockers before a feature can be safely released?▼

Identifying release blockers requires aggregating feature delivery evidence to map missing dependencies and risks to specific owners. This gap analysis highlights exactly what remains to be resolved before granting human release authority.

Does generating a readiness card preserve human authority over the final release decision?▼

Generating a readiness card preserves human release authority by providing transparent, evidence-backed status reports without automating the deployment. It summarizes bounded delivery states and highlights gaps so humans make the final release decision.

Can I use ticket and PR data to map missing dependencies to specific owners?▼

Yes, you can aggregate ticket and PR data to map missing dependencies and risks to specific owners. The readiness card explicitly links this technical evidence to next actions, ensuring clear ownership of identified blockers.

When do I need an evidence-linked status report for feature delivery?▼

You need an evidence-linked status report during release-candidate preparation to provide stakeholders with a transparent answer on production readiness. It synthesizes test and risk data to show exactly what gaps must be closed first.

Related Skills

Explore More Product & Management Skills→
aurora-atomsaurora-atoms

pr-to-release-summary

Generate structured release summaries from merged pull requests and validation evidence.

Community
Advanced
Markson22Markson22

reversa-paradigm-advisor

Detect legacy paradigms from specifications and generate paradigm_decision.md for migration.

Community
Advanced
thompson0012thompson0012
28

finance-audit-support

Automate SOX 404 ICFR testing workflows from scoping to deficiency reporting.

Community
Advanced
DavidsonGomesDavidsonGomes

fin-close-management

Automate month-end close planning, sequencing, and progress tracking.

Community
Advanced