ship

Automate shipping of code, artifacts, and actions in project management workflows.

Updated May 24, 2026
One-click install
npx skills add https://github.com/ChrisFmlyc/spades --skill ship-chrisfmlyc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ChrisFmlyc/spades/tree/main/plugins/spades/skills/ship
Command: npx skills add https://github.com/ChrisFmlyc/spades --skill ship-chrisfmlyc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of shipping deliverables and updating their status in project management workflows, streamlining the transition from planning to completion.

Core Features & Use Cases

  • Ship Deliverables: Automates the shipping of code, artifacts, and actions to their respective destinations (e.g., merging code into a repository, publishing an artifact, recording a completed action).
  • Status Tracking: Updates the status of deliverables from 'evaluating' to 'shipped' or 'rejected', based on the audit trail and human input.
  • Use Case: After a project plan has been evaluated and deemed passable, this Skill can be used to ship the code (if applicable), publish the artifact, or document the completion of an action.

Quick Start

To ship the deliverable from the approved plan, simply run the command: /spades:ship

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate deliverable shipping in project management workflows?

Automated deliverable shipping handles code, artifacts, and actions by sending them to their respective destinations. It merges code into repositories, publishes artifacts, and records completed actions while updating status based on human input and audit trails.

Can I track deliverable status updates automatically after project plan approval?

Deliverable status tracking updates items from 'evaluating' to 'shipped' or 'rejected' based on audit trails and human input. After a project plan is evaluated and approved, the system automatically transitions the status of code, artifacts, and actions.

Does automated shipping require access to GitHub for project management tasks?

Automated shipping requires access to project management tools like GitHub and the ability to interact with the user for additional information. This access allows the system to merge code into repositories and publish artifacts during the shipping process.

What is the best way to ship code and publish artifacts after plan evaluation?

The best way to ship code and publish artifacts is running the shipping command after a project plan has been evaluated and deemed passable. This automates merging code, publishing artifacts, and recording completed actions in your workflow.

How do I maintain an audit trail when updating project deliverable statuses?

Maintaining an audit trail during status updates involves recording the shipping of code, artifacts, and actions while transitioning deliverables from 'evaluating' to 'shipped' or 'rejected' based on human input.