ship-milestone

Orchestrate milestone shipping from gap analysis to production release.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hamzaPixl/pixl-ai --skill ship-milestone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-milestone
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/ship-milestone
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill ship-milestone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ship a body of work from analysis through implementation, testing, documentation, and release while reducing coordination overhead, missed dependencies, and fragmented commits.

Core Features & Use Cases

  • Gap analysis: Parse specs or analysis docs and produce an accurate status table (done / partial / not started / dropped).
  • Task planning & sizing: Decompose remaining work into S/M tasks, map dependencies, and assign parallel waves to maximize throughput.
  • Implementation orchestration & validation: Execute parallel waves, run tests after each wave, perform user-flow testing, update all docs, and create grouped, conventional commits for push.
  • Use Case: When asked to "ship this milestone", run a full assessment, produce a task plan, implement in waves, validate user flows, update documentation, and push a clean release.

Quick Start

Provide a spec file or a description and instruct the skill to assess gaps, produce a task plan, implement waves, run tests, update docs, and produce a shipping report.

Frequently Asked Questions about ship-milestone

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

FAQPage Schema
How do I orchestrate milestone shipping from analysis to release?▼

You can ship a milestone by providing a spec file to assess gaps, decompose remaining work into S/M tasks, execute parallel implementation waves, run tests after each wave, and generate a final shipping report.

What is the best way to plan tasks with dependencies for a software release?▼

Task planning for a software release decomposes remaining work into sized S/M tasks, maps dependencies, and assigns parallel waves to maximize throughput before running tests between implementation waves.

How do I generate a gap inventory from a spec file before implementation?▼

Generating a gap inventory involves parsing specs or analysis docs to produce a status table categorizing items as done, partial, not started, or dropped before task planning begins.

Can I run tests between parallel implementation waves during a release?▼

Yes, implementation orchestration executes parallel waves of work and runs tests after each wave to validate progress before performing user-flow testing and creating grouped commits.

Does milestone shipping work for CLI changes, documentation edits, and engine updates?▼

Yes, milestone shipping applies to software development milestones including CLI changes, engine updates, documentation edits, and user-flow testing to coordinate commits for production releases.

How do I group conventional commits for a coordinated release push?▼

Grouping conventional commits involves orchestrating implementation waves, updating all documentation, and organizing the changes into grouped commits for a clean release push.