Asset Delivery
The Asset Delivery skill is Phase 5 (final phase) of the Omni Architect pipeline. It consolidates all outputs from previous phases into a structured delivery package with comprehensive documentation, logs, and handoff materials ready for development teams.Purpose
Creates a complete, organized deliverable package containing:- Parsed PRD in structured JSON format
- Mermaid Diagrams with source code and rendered images
- Validation Reports with scores and quality metrics
- Figma Asset Links with direct URLs and previews
- Orchestration Logs with complete pipeline timeline and metrics
- Design Handoff Documentation for developers
Inputs
The structured PRD from Phase 1 (PRD Parser). Contains features, entities, stories, flows, and requirements.
Array of generated and validated diagrams from Phase 2 (Mermaid Generator). Includes Mermaid source code and metadata.
Validation analysis from Phase 3 (Logic Validator). Contains scores, status, breakdown, warnings, and suggestions.
Array of Figma assets created in Phase 4 (Figma Generator). Includes node IDs, URLs, and preview links.
Outputs
Complete delivery package with all artifacts and documentation.Structure:
Generated Artifacts
The delivery package creates the following file structure:Artifact Details
| Artifact | Format | Location | Description |
|---|---|---|---|
| PRD Parseado | JSON | output/parsed-prd.json | Structured PRD with features, entities, stories, flows |
| Diagramas Mermaid | .mmd + .svg + .png | output/diagrams/ | Source code + vector + raster renderings |
| Índice de Diagramas | JSON | output/diagrams/index.json | Metadata for all diagrams |
| Relatório de Validação | JSON + Markdown | output/validation/ | Scores, breakdown, warnings, suggestions |
| Figma Assets | JSON | output/figma-assets.json | Links, previews, node IDs for all Figma assets |
| Orchestration Log | JSON | output/orchestration-log.json | Complete pipeline execution log with metrics |
| Design Handoff Doc | Markdown | output/HANDOFF.md | Developer-ready documentation |
Sanitization & Security
All sensitive information is automatically removed from logs:Redacted Fields
Safe to Commit
After sanitization, all files inoutput/ are safe to commit to version control.
Orchestration Log Structure
Theorchestration-log.json provides complete pipeline visibility:
Design Handoff Document
TheHANDOFF.md provides developer-ready documentation:
Metrics Tracking
The delivery package includes comprehensive metrics:Quality Metrics
Performance Metrics
Volume Metrics
Example Delivery Package
Best Practices
Review the Handoff Document First
TheHANDOFF.md is designed for quick developer onboarding. Start there before diving into raw JSON files.
Commit Delivery Package to Git
All files are sanitized and safe to version control. Tag releases:Share Figma Links with Team
Extract Figma URLs fromfigma-assets.json and share in:
- Project documentation
- Jira/Linear tickets
- Slack/Teams channels
Use Metrics for Retrospectives
Track metrics across sprints:- Validation scores trending up = better PRD quality
- Generation times trending down = pipeline optimization
Archive Old Deliveries
Create timestamped directories:Error Handling
| Scenario | Behavior |
|---|---|
| Output directory exists | Prompts for overwrite confirmation (or —force flag) |
| Disk space insufficient | Error with required space calculation |
| File write permissions | Error with permission requirements |
| Mermaid render fails | Includes .mmd source, skips .svg/.png with warning |
| Missing input artifacts | Partial package with clear status in delivery_package.issues |
Integration
Asset Delivery runs automatically as Phase 5 (final):./output/ with all artifacts ready for handoff.