ship-decisions

Apply decision frameworks to evaluate feature readiness and shipping strategies.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/danfrdn/antigravity-config --skill ship-decisions-danfrdn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-decisions
Source: https://github.com/danfrdn/antigravity-config/tree/main/skills/ship-decisions
Command: npx skills add https://github.com/danfrdn/antigravity-config --skill ship-decisions-danfrdn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you make confident decisions about whether to ship a feature now or iterate further, preventing perfectionism paralysis and balancing speed with quality.

Core Features & Use Cases

  • Decision Frameworks: Leverages established models like one-way vs. two-way doors, shipping scorecards, and tech debt vs. speed trade-offs.
  • Use Case: You've built a new feature and are unsure if it's "good enough." This Skill guides you through a structured assessment to determine the best next step, whether it's shipping immediately, iterating once more, or gathering more data.

Quick Start

Use the ship-decisions skill to assess if the new user profile page is ready to ship.

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 iterate further?

To decide whether to ship a feature now or iterate further, evaluate feature readiness using a shipping scorecard framework. This structured assessment prevents perfectionism paralysis by balancing release speed against quality and technical debt.

What is the one-way vs two-way door framework for product shipping decisions?

The one-way vs two-way door framework distinguishes between irreversible and reversible decisions when shipping features. It guides product management by determining which releases require cautious evaluation and which allow rapid iteration with risk mitigation.

How do I balance technical debt against shipping speed in agile development?

Balancing technical debt against shipping speed in agile development requires evaluating trade-offs between immediate feature delivery and long-term code maintainability. Structured frameworks help assess if accumulating debt is justified for faster iteration.

What is the best way to evaluate feature readiness before a gradual rollout?

The best way to evaluate feature readiness before a gradual rollout is applying a shipping scorecard to assess risk mitigation and quality thresholds. This structured approach ensures confident decisions on whether to release or gather more data.

When should I not use a shipping scorecard for product management decisions?

You should not use a shipping scorecard for product management decisions when immediate action is required for critical hotfixes or when evaluating routine updates that do not involve significant technical debt or feature readiness trade-offs.