skills.rest
menkesu
menkesuCOMMUNITY
Explore all skills by this author →
GitHub

ship-decisions

Guide product teams through structured shipping decisions with scorecards and rollout plans.

389|121|Updated Jan 28, 2026
Search Tags:#ship#decision-making#technical-debt#two-way-door#one-way-door#gradual-rollout#shipping-scorecard
One-click install
npx skills add https://github.com/menkesu/awesome-pm-skills --skill ship-decisions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-decisions
Source: https://github.com/menkesu/awesome-pm-skills/tree/main/ship-decisions
Command: npx skills add https://github.com/menkesu/awesome-pm-skills --skill ship-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Shipping Decision Matrix helps product teams decide when to ship a feature versus iterate, reducing perfectionism paralysis and balancing technical debt with velocity using established decision frameworks.

Core Features & Use Cases

  • Reversible vs Irreversible Decisions (One-Way vs Two-Way Doors) guides fast learning and careful planning for high-stakes choices.
  • The Shipping Scorecard assesses readiness across core functionality, edge cases, reversibility, learning value, and risk.
  • Technical Debt vs Shipping Speed framework guides whether to ship now or refactor later based on user value and debt carrying cost.
  • Gradual Rollout Strategy provides staged deployment (internal, early adopters, broader beta, GA) with rollback plans.
  • Decision Tree templates and action checklists help teams make consistent, auditable shipping decisions.
  • Related concepts and templates (in references) for further guidance.

Quick Start

Apply the Shipping Decision Matrix to a new feature request by classifying it as a one-way or two-way door, run the scorecard, and plan a staged rollout.

Frequently Asked Questions about ship-decisions

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

FAQPage Schema
How do I decide whether to ship a feature now or keep iterating?▼

To decide whether to ship or iterate, use a structured shipping scorecard to evaluate readiness across core functionality, edge cases, reversibility, learning value, and risk. This framework reduces perfectionism paralysis by balancing velocity with safe execution.

What is the difference between a one-way door and a two-way door decision?▼

A one-way door is an irreversible decision requiring careful planning, while a two-way door is reversible, allowing fast shipping and rapid learning. Applying these frameworks helps teams choose appropriate velocity for high-stakes choices.

How do I balance technical debt with shipping speed?▼

Balance technical debt and shipping speed by evaluating user value against the debt carrying cost. This framework guides whether to ship immediately or refactor later, ensuring maintenance does not block velocity.

How do I plan a gradual rollout strategy for a new feature?▼

Plan a gradual rollout strategy by executing staged deployments across internal, early adopters, broader beta, and general availability phases. This approach includes predefined rollback plans for safe releases.

When should I avoid shipping a new feature?▼

Avoid shipping a new feature if the scorecard indicates low readiness across core functionality, high irreversibility without a rollback plan, or low learning value. High technical debt carrying costs also warrant delaying the release.

Does the ship-decisions framework work for managing technical debt tradeoffs?▼

Yes, the ship-decisions framework works for technical debt tradeoffs by applying a structured matrix to evaluate whether shipping now or refactoring later maximizes user value. It balances debt carrying cost against velocity.

Related Skills

Explore More Product & Management Skills→
ksoichiroksoichiro

game-design-decisions

Document design decisions for Chrono Dawn's respawn, portals, and progression with rationale and edge-cases.

Community
Basic
cosmixcosmix
53

code-migration

Plan staged code migrations with rollback and feature flags.

Community
Advanced
eugenelimeugenelim
15

de-risk-intent

Test a framed intent's riskiest assumption and return a survive or kill verdict.

Community
Advanced
olehsvyrydovolehsvyrydov
13

product-owner

Translate stakeholder needs into product requirements and prioritized backlog items.

Community
Basic