feature-delivery-case

Name: feature-delivery-case
Availability: InStock
Author: aurora-atoms

Maintain an evidence-linked lifecycle record for feature delivery cases.

Updated Jun 1, 2026

Search Tags:#governance #evidence #traceability #lifecycle #delivery #readiness

Ready to run

npx skills add https://github.com/aurora-atoms/lattice --skill feature-delivery-case

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) and schemas (resource) components.

What problem does it solve?

This Skill solves the fragmentation of delivery evidence by maintaining a single, durable, and traceable record that links business requirements, technical decisions, and operational readiness.

Core Features & Use Cases

Lifecycle Governance: Tracks the evolution of a feature from initial requirement through to release readiness, ensuring no evidence gaps remain.
Readiness Assessment: Provides deterministic readiness results based on explicit criteria, preventing ambiguous status updates.
Use Case: Use this to consolidate Jira tickets, PR reviews, and test results into a unified Feature Delivery Case that clearly communicates to stakeholders whether a feature is ready for its next lifecycle stage.

Quick Start

Use the feature-delivery-case skill to initialize a new delivery case record for the current feature branch using the provided requirements and evidence sources.

Frequently Asked Questions about feature-delivery-case

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

FAQPage Schema

How do I maintain traceability for feature delivery lifecycle governance?▼

Feature delivery traceability is maintained by structuring a durable lifecycle record that links business requirements, technical decisions, and operational readiness into a single evidence-backed case.

How do I consolidate Jira tickets, PR reviews, and test results into a unified delivery case?▼

Consolidating delivery artifacts is achieved by linking Jira tickets, PR reviews, and test results into a unified feature delivery case that clearly communicates stage readiness to stakeholders.

What is deterministic readiness assessment for software feature delivery?▼

Deterministic readiness assessment provides explicit release readiness results based on predefined criteria, preventing ambiguous status updates and ensuring no evidence gaps remain in the delivery lifecycle.

Do I need Python to use this feature delivery governance skill?▼

Python is a required dependency to execute the scripts that maintain the structured, evidence-linked lifecycle records for feature delivery cases.

When do I need audit-ready documentation for feature delivery?▼

Audit-ready documentation is needed when software engineering workflows require rigorous governance over scope, decisions, dependencies, and risk management to ensure traceable release readiness.

What is the best way to prevent evidence gaps during feature release readiness?▼

Preventing evidence gaps requires tracking the evolution of a feature from initial requirement through release readiness, ensuring all delivery artifacts are linked within a durable governance record.