delivery-artifacts

Manage versioned delivery artifacts and synchronize them with Linear issue tracking.

Updated Jan 10, 2026

Search Tags:#version control #Linear #agile #artifact management #workflow documentation

Ready to run

npx skills add https://github.com/Thawatchai-Petkaew/campvibe --skill delivery-artifacts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: delivery-artifacts
Source: https://github.com/Thawatchai-Petkaew/campvibe/tree/main/.claude/skills/delivery-artifacts
Command: npx skills add https://github.com/Thawatchai-Petkaew/campvibe --skill delivery-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams maintain versioned delivery outputs, keeping them in sync with Linear, ensuring traceability and up-to-date documentation for every feature, epic, and story.

Core Features & Use Cases

Versioned Files: Store every workflow output as versioned files in a structured directory.
Linear Sync: Keep files in sync with Linear for live status tracking.
Use Case: For teams using Linear to manage workflows, this Skill ensures that all artifacts, like requirements, designs, and tests, are stored and versioned correctly.

Quick Start

Use the delivery-artifacts skill to scaffold a new story with 'node scripts/linear-sync.mjs scaffold <CAM-id>'.

Frequently Asked Questions about delivery-artifacts

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

FAQPage Schema

How do I keep delivery artifacts versioned and synced with Linear issue tracking?▼

Versioned delivery artifacts are maintained by storing workflow outputs in a structured directory and synchronizing them with Linear. This ensures traceability and up-to-date documentation for every feature, epic, and story.

What is the best way to manage version control for agile story outputs?▼

Managing version control for agile outputs involves storing every workflow artifact as a versioned file. This approach ensures that requirements, designs, and tests remain correctly stored and traceable throughout the project lifecycle.

Does this artifact management approach require a specific Linear setup for epics and stories?▼

No specific Linear setup is required beyond standard issue tracking. The synchronization process directly maps feature, epic, and story outputs to your existing Linear issues to maintain live status tracking.

Can I use this workflow documentation method for teams not using Linear?▼

This workflow documentation method is specifically designed to synchronize with Linear. Teams not using Linear will not receive the live status tracking and traceability benefits provided by the Linear sync functionality.

Why does synchronizing delivery artifacts with Linear improve agile traceability?▼

Synchronizing delivery artifacts with Linear improves traceability by linking versioned files directly to live issue statuses. This ensures that documentation history remains accurate and aligned with current project workflows.