ship

Orchestrates Validate and Learn phases of AIDLC for feature readiness.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/csackrider/AI-DLC --skill ship-csackrider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/csackrider/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/ship
Command: npx skills add https://github.com/csackrider/AI-DLC --skill ship-csackrider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the Validate and Learn phases of the AIDLC to ensure features meet the Product Spec, surface learnings, and enable a clean merge.

Core Features & Use Cases

  • Validate: compare each success criterion in the Product Spec, record pass/fail with evidence, and compute an overall score (default 90% gate) to guide readiness.
  • Learn: capture ADRs for significant decisions, summarize retrospective notes, and update repository documentation as needed.
  • Outputs & Handoff: generate feature/<slug>/validate-scorecard.md, feature/<slug>/learn-notes.md, and a merge/deploy checklist; hand off with explicit assignees.

Quick Start

Run the ship skill after a Review to generate the scorecard, ADRs, and a merge-ready checklist.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I validate feature readiness against a product spec before merging?

Capture Architecture Decision Records for significant decisions by generating ADRs in an adr/ folder using a template, then summarize retrospective notes and update repository documentation to reflect those decisions.

How do I generate a merge checklist after a pull request review?

Yes, ship readiness validation applies to feature branches and PRs in the Review stage, computing an overall score from success criteria to determine if a feature meets the 90% readiness gate.

What is the process to capture ADRs and learnings during a pull request review?

Capture Architecture Decision Records for significant decisions by generating ADRs in an adr/ folder using a template, then summarize retrospective notes and update repository documentation to reflect those decisions.

Can I use a scorecard to gate pull request merges based on product spec criteria?

Yes, ship readiness validation applies to feature branches and PRs in the Review stage, computing an overall score from success criteria to determine if a feature meets the 90% readiness gate.

How do I update repository documentation with significant decisions from a feature review?

Update repository documentation by capturing ADRs for significant decisions in an adr/ folder using a template, summarizing retrospective notes, and reflecting those decisions in the repository documentation.

What files are produced when running ship readiness validation on a feature branch?

Running ship readiness validation produces feature/<slug>/validate-scorecard.md, feature/<slug>/learn-notes.md, and a merge/deploy checklist to hand off with explicit assignees.