shipping-products

Guides product teams through launch planning and shipping velocity decisions using frameworks from product leaders.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill shipping-products-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-products
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/shipping-products
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill shipping-products-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often stall before launch due to over-polishing, unclear quality bars, organizational friction, or fear of shipping imperfect products. This Skill provides structured guidance drawn from 47 product leaders to diagnose shipping blockers and accelerate release cycles without sacrificing appropriate quality. ## Core Features & Use Cases - Blocker Diagnosis: Walks through scope, quality, dependency, and organizational friction questions to identify what actually prevents shipping. - Shipping Principles Library: Applies ten core principles such as 'ship to get feedback', '99% done is 0% done', and 'speed and stability move together', backed by 55 cited insights in references/guest-insights.md. - Quality Tradeoff Guidance: Helps define Product Quality List (PQL) checklists and decide what must be polished pre-launch versus post-launch. - Use Case: A PM is three weeks late on a feature launch and unsure whether to cut scope or delay. The Skill asks forcing questions like 'What would it take to ship this tomorrow?' to expose the critical path and recommend a minimal shippable version. ## Quick Start Ask the Skill to help you figure out what is blocking your product launch and what the smallest shippable version would be.

Frequently Asked Questions about shipping-products

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

FAQPage Schema
How do I decide what to cut before a product launch?

Use the 'maximally accelerated' forcing question: ask what it would take to ship tomorrow, which exposes the true critical path versus non-essential blockers. Then define the smallest version that lets you learn from real users and cut everything else.

How to balance shipping speed with product quality?

Create a Product Quality List (PQL) checklist defining the standards that must be met before release, and iterate on it when bugs slip through. For mission-critical products like email or finance, prioritize reliability; for emergent products like AI, ship raw and polish based on real usage.

When should I not ship early and iterate?

Avoid the 'launch early' approach for mission-critical products where reliability drives user trust, such as email or financial tools. Also avoid premature PR and marketing pushes before validating that customers actually want the product, to prevent sunk-cost traps.

Why do feature flags cause problems at launch?

Excessive feature flags create technical debt and hidden failure points during launches. The guidance recommends limiting active flags at ship time, treating them as temporary shims that must be removed to prevent long-term instability.

Does shipping faster hurt system stability?

No. Speed and stability move together because faster shipping means smaller, more frequent changes with a smaller blast radius. Smaller changes reduce complexity and make failures easier to debug and mitigate.