# Project Shipper

> Asegura que los productos se lancen sin dramas. Usa este skill para launch planning, release checklists, go-to-market coordination, rollback plans, y asegurar que los lanzamientos sean suaves y exitosos.

- Skill: `leandroomargarcia/project-shipper` (Agent Skill)
- Install (CLI): `npx skillmds@latest add leandroomargarcia/project-shipper`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leandroomargarcia/project-shipper/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: leandroomargarcia (https://skillmd.com/u/leandroomargarcia)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/leandroomargarcia/project-shipper

---


# Project Shipper

Especialista en llevar productos desde "casi listo" hasta "live y funcionando". Coordina todos los aspectos del lanzamiento para minimizar riesgos y maximizar impacto.

## Cuándo Usar Este Skill

- Planificar lanzamientos de productos/features
- Crear release checklists
- Coordinar go-to-market
- Manejar rollbacks y hotfixes
- Comunicar launch status
- Post-mortem de lanzamientos

## Responsabilidades Principales

### 1. Launch Planning
- Crea timelines realistas
- Identifica todas las dependencies
- Asigna owners claros
- Define success criteria
- Planifica rollback scenarios

### 2. Coordination
- Alinea engineering, marketing, support
- Manages handoffs entre equipos
- Asegura assets listos
- Coordina timing de announcements
- Tracks progress centralizado

### 3. Risk Management
- Identifica potential blockers
- Crea contingency plans
- Prepara rollback procedures
- Plans gradual rollouts
- Monitors launch metrics

### 4. Communication
- Updates stakeholders regularmente
- Escala issues temprano
- Documenta decisions
- Post-launch reporting

## Launch Timeline Template

```
T-14 DÍAS (2 semanas antes):
☐ Feature freeze
☐ QA testing begins
☐ Marketing assets in progress
☐ Support docs drafted
☐ Rollback plan documented

T-7 DÍAS (1 semana antes):
☐ QA sign-off
☐ Marketing assets approved
☐ Support docs live
☐ Staging validated
☐ Stakeholder preview

T-3 DÍAS:
☐ Final code review
☐ Load testing complete
☐ Communications scheduled
☐ Team on-call assigned
☐ Launch checklist reviewed

T-1 DÍA:
☐ Final staging check
☐ Team briefed
☐ Monitoring ready
☐ Rollback tested
☐ Go/No-go decision

T-0 (LAUNCH DAY):
☐ Deploy to production
☐ Smoke tests pass
☐ Monitoring active
☐ Communications sent
☐ Team available

T+1 DÍA:
☐ Metrics review
☐ Bug triage
☐ User feedback collected
☐ Quick fixes if needed

T+7 DÍAS:
☐ Performance review
☐ Lessons learned
☐ Documentation updated
☐ Celebration! 🎉
```

## Launch Checklist

```markdown
## Pre-Launch
### Engineering
- [ ] Code reviewed and merged
- [ ] Tests passing (unit, integration, e2e)
- [ ] Performance benchmarked
- [ ] Security review complete
- [ ] Database migrations ready
- [ ] Feature flags configured
- [ ] Monitoring/alerts set up
- [ ] Rollback procedure documented

### Product
- [ ] Acceptance criteria met
- [ ] User flows tested
- [ ] Edge cases covered
- [ ] Analytics events firing
- [ ] Success metrics defined

### Design
- [ ] All states designed (empty, loading, error)
- [ ] Responsive tested
- [ ] Accessibility checked
- [ ] Assets exported

### Marketing
- [ ] Blog post ready
- [ ] Social posts scheduled
- [ ] Email campaign queued
- [ ] Press materials (if applicable)
- [ ] Website/changelog updated

### Support
- [ ] FAQs prepared
- [ ] Macros/templates ready
- [ ] Team briefed on feature
- [ ] Escalation path clear

## Launch
- [ ] Production deploy successful
- [ ] Smoke tests passing
- [ ] Metrics being collected
- [ ] Monitoring nominal
- [ ] Communications sent

## Post-Launch
- [ ] Metrics reviewed
- [ ] Bugs triaged
- [ ] Feedback collected
- [ ] Retro scheduled
- [ ] Docs finalized
```

## Rollout Strategies

```
ESTRATEGIA        | CUÁNDO USAR
------------------|----------------------------------
Big Bang          | Low risk, simple changes
Canary            | Testing with small % first
Ring Deployment   | Internal → Beta → All users
Feature Flags     | Gradual % rollout
Geographic        | Region by region
Blue-Green        | Zero downtime required
```

## Rollback Plan Template

```markdown
## Rollback Plan: [Feature Name]

### Trigger Conditions
Rollback if any of:
- Error rate > X%
- P95 latency > Yms
- Critical bug affecting >Z% users
- [Custom condition]

### Rollback Procedure
1. [Step 1 - usually disable feature flag]
2. [Step 2 - or revert deployment]
3. [Step 3 - clear cache if needed]
4. [Step 4 - notify team]
5. [Step 5 - communicate to users if needed]

### Rollback Owner
Primary: @person
Backup: @person

### Estimated Time
Full rollback: X minutes

### Data Considerations
- Data migration: [reversible/irreversible]
- User data impact: [description]

### Communication
- Internal: [Slack channel]
- External: [if needed, how]
```

## Go/No-Go Decision

```
GO/NO-GO MEETING AGENDA:

1. Feature readiness
   - Engineering: ✅/❌
   - Product: ✅/❌
   - Design: ✅/❌

2. Support readiness
   - Docs: ✅/❌
   - Training: ✅/❌

3. Marketing readiness
   - Assets: ✅/❌
   - Timing: ✅/❌

4. Risk assessment
   - Known issues: [list]
   - Mitigations: [list]

5. Decision
   ☐ GO
   ☐ NO-GO (reason: ___)
   ☐ CONDITIONAL GO (conditions: ___)
```

## Launch Communication Template

```markdown
## [Feature] Launch Update

**Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked

**Launch Date:** [date]

### Progress
- [x] Development complete
- [x] QA passed
- [ ] Marketing ready
- [ ] Support briefed

### Key Updates
- [Update 1]
- [Update 2]

### Blockers/Risks
- [Blocker if any]
- Mitigation: [plan]

### Next Steps
- [Next milestone]
- Owner: @person
- Due: [date]
```

## Post-Launch Review

```markdown
## [Feature] Launch Review

### Summary
- Launch date: [date]
- Success: ✅ Yes / ⚠️ Partial / ❌ No

### Metrics
| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| [Metric 1] | X | Y | ✅/❌ |
| [Metric 2] | X | Y | ✅/❌ |

### What Went Well
1. [Thing 1]
2. [Thing 2]

### What Could Improve
1. [Issue 1] → [Action]
2. [Issue 2] → [Action]

### Bugs/Issues
- P1: [X] - Status: [fixed/investigating]
- P2: [X] - Status: [fixed/investigating]

### User Feedback
- Positive: [summary]
- Negative: [summary]
- Feature requests: [list]

### Action Items
| Action | Owner | Due |
|--------|-------|-----|
| [Action] | @person | [date] |
```

## Launch Metrics Dashboard

```
HEALTH:
- Error rate: [X%] (target: <0.1%)
- P95 latency: [Xms] (target: <500ms)
- Uptime: [X%] (target: >99.9%)

ADOPTION:
- Users exposed: [X]
- Users activated: [X]
- Adoption rate: [X%]

ENGAGEMENT:
- Feature usage: [X/day]
- Retention: [X%]
- NPS impact: [+/-X]
```

## Mejores Prácticas

1. **Launch is not the finish line** - Es el comienzo
2. **Gradual > Big bang** - Reduce risk siempre que puedas
3. **Have a rollback plan** - Always
4. **Communicate proactively** - No surprises
5. **Celebrate, then improve** - Retros son esenciales
6. **Document everything** - Future you will thank you

## Filosofía

> "A smooth launch isn't luck—it's preparation. Every minute spent on planning saves hours of firefighting."

El objetivo es que cada lanzamiento sea boring-ly smooth, sin drama, con impacto máximo.