delivery-artifact-builder

Name: delivery-artifact-builder
Availability: InStock
Author: aurora-atoms

Route Feature Delivery Cases to specialized delivery roles for auditable artifacts.

Updated Jun 1, 2026

Search Tags:#workflow #governance #evidence #delivery #artifact #specialist

Ready to run

npx skills add https://github.com/aurora-atoms/lattice --skill delivery-artifact-builder

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented or uncoordinated delivery work by routing Feature Delivery Cases to the most appropriate specialist, ensuring that every artifact is actionable, auditable, and evidence-based.

Core Features & Use Cases

Specialist Routing: Automatically selects one of seven specialized delivery roles (e.g., Ticket Ready, Implementation Plan, PR Ready) based on the current lifecycle stage.
Evidence-Linked Composition: Ensures that all generated artifacts are grounded in verified facts, citations, and explicit evidence gaps rather than assumptions.
Use Case: When a developer has a complex feature ready for review but lacks a clear implementation plan, this Skill routes the request to the implementation-plan specialist to decompose the work and identify critical path dependencies.

Quick Start

Use the delivery-artifact-builder skill to route the current feature delivery case to the appropriate specialist for the implementation-plan stage.

Frequently Asked Questions about delivery-artifact-builder

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

FAQPage Schema

How do I generate auditable delivery artifacts for software development lifecycle stages?▼

You route Feature Delivery Cases to specialized delivery roles based on explicit lifecycle state, ensuring every generated artifact is actionable, evidence-linked, and traceable for compliance throughout the software development lifecycle.

What is evidence-linked artifact composition in feature delivery?▼

Evidence-linked artifact composition grounds generated delivery outputs in verified facts, citations, and explicit evidence gaps rather than assumptions, ensuring software delivery artifacts remain auditable and compliant.

How do I route a complex feature to an implementation plan specialist?▼

You input the Feature Delivery Case with its current lifecycle stage, triggering the routing mechanism to select the implementation-plan specialist for decomposing work and identifying critical path dependencies.

Does delivery artifact generation require explicit human authority boundaries?▼

Yes, delivery artifact generation requires explicit human authority boundaries alongside lifecycle state and evidence to ensure traceability and maintain compliance when routing work to specialized delivery roles.

Can I use this routing approach for ticket preparation and release summaries?▼

Yes, you can use specialist routing for ticket preparation and release summaries. The mechanism applies to software development lifecycle stages ranging from initial ticket ready phases through final release summary generation.

What happens if my feature delivery case lacks verified evidence facts?▼

If a feature delivery case lacks verified evidence, the artifact composition explicitly identifies evidence gaps rather than making assumptions, ensuring generated outputs remain grounded in verified facts for auditability.