| name | stage-tracker |
| version | 0.3.0 |
| description | Milestone tracking across the 6 DojoOS Launchpad stages (Ideation → Formation → MVP → Traction → Funded → Scaling) with per-stage exit criteria, blockers log, and Dojo-Score-compatible scoring. Produces current-stage.md, milestones.md, blockers.md, dojo-score.md artifacts. Schema-compatible with DojoOS Launchpad stage data model. Use when the user asks "stage tracker", "milestones", "current stage", "startup stage", "Dojo Score", "readiness for next stage", "/stage-tracker". Standalone methodology; syncs with DojoOS via dojoos-api-consumer agent when available.
|
Stage Tracker
Trackea el progreso de una venture a través de las 6 etapas del DojoOS Launchpad — Ideation → Formation → MVP → Traction → Funded → Scaling. Cada stage tiene exit criteria explícitos, blockers log, y un scoring Dojo-Score-compatible.
⚠️ Disclaimer
- Stage tracking es framework de evaluación, NO un diagnostic final — early-stage startups son messy, los stages overlap
- Dojo Score es un proxy metodológico, NO un rating investment-grade — decisiones de inversión requieren diligence completa
- Este skill schema-compat con DojoOS pero opera standalone hasta que el API esté disponible
Regla de idioma
Español.
Directorio de salida
./launchpad/{startup-slug}/stage-tracker/
├── current-stage.md # Stage actual + confidence level
├── milestones.md # Milestones completados + pending per stage
├── blockers.md # Blockers activos con severity + owner
├── dojo-score.md # Scoring Dojo-Score-compat (multi-axis)
└── history/
├── YYYY-MM-DD-stage-transition.md # Log de transiciones
└── ...
Los 6 stages con exit criteria
Stage 1 — Ideation
Objetivo: validar que existe un problema real worth solving.
Exit criteria (todos):
Next stage: Formation (team + legal entity setup)
Stage 2 — Formation
Objetivo: formar el equipo fundador + legal entity + governance.
Exit criteria:
Next stage: MVP
Stage 3 — MVP
Objetivo: construir + testear una solution mínima.
Exit criteria:
Next stage: Traction
Stage 4 — Traction
Objetivo: demonstrate repeatable customer acquisition + retention.
Exit criteria:
Next stage: Funded
Stage 5 — Funded
Objetivo: raise institutional round para accelerate.
Exit criteria:
Next stage: Scaling
Stage 6 — Scaling
Objetivo: scale organization + market presence post-PMF.
Exit criteria (indicative — startups rarely "complete" scaling):
Beyond: Growth stage fundraising (Series B+), potential acquisition conversations, or public readiness.
Dojo Score — multi-axis scoring
Dojo Score es un scoring system de 0-100 compuesto por 5 axes (20 pts cada uno):
Axis 1 — Team (0-20)
- 5: Founder-only, unvalidated
- 10: Founder + 1 co-founder, skills complementary, values aligned
- 15: Founder team + 2-3 early employees con equity
- 20: Full team cross-functional + advisors + proven execution
Axis 2 — Product (0-20)
- 5: Idea only, no prototype
- 10: Working prototype, used by founders
- 15: MVP shipped, real users, feedback loop active
- 20: Product beyond MVP, feature roadmap informed by data
Axis 3 — Traction (0-20)
- 5: No customers, few validation signals
- 10: Pre-revenue, high engagement signals (waitlist, LOIs, pilots)
- 15: Early revenue + growth signs
- 20: Strong revenue + growth + retention cohorts positive
Axis 4 — Market (0-20)
- 5: Market small or unclear, competition dominant
- 10: Market growing, competition tough but opportunity exists
- 15: Market growing + defensible niche + clear customer demand
- 20: Large market + tailwinds + first-mover or superior approach
Axis 5 — Business model (0-20)
- 5: No business model articulated
- 10: Revenue model identified, not tested
- 15: Unit economics tested, margins visible
- 20: Sustainable unit economics + clear path to profitability
Total: 0-100. Stage expectations:
| Stage | Typical Dojo Score range |
|---|
| Ideation | 10-30 |
| Formation | 25-45 |
| MVP | 40-60 |
| Traction | 55-75 |
| Funded | 65-85 |
| Scaling | 75-95 |
Caveats:
- Score no es ranking absolute; context matters (industry, geography, market conditions)
- Score es self-reported + biased; use for internal tracking, NOT for external pitching
- Dojo Score specific weighting puede shift basado en DojoOS platform evolution — este skill implementa v1
Flujo del skill
Paso 1 — Load context
ST-1: "Vamos a trackear tu stage actual. Contexto:
-
startup-profile.md existente? Si sí, lo leo (autodetect stage claim)
-
cap-table.md existente? (para Formation stage check)
-
Artifacts existentes en ./launchpad/{startup-slug}/:
customer-interview-system/ (Ideation validation)
cofounder-matching/ (Formation team)
founder-documents/ (Formation legal)
cap-table-builder/ (Formation equity)
investor-matching/ + demo-day-prep/ (Funded prep)
-
¿Qué stage claim tenés? (tu view de donde estás)"
Paso 2 — Assess current stage
ST-2: Por cada stage (de Ideation hasta el claim del user), evaluar exit criteria:
- Verde ✓: criterion met (cite evidence from artifacts)
- Amarillo 🟡: criterion partially met (what's missing)
- Rojo 🔴: criterion not met (blocker)
- Gris ⚪: N/A or not yet evaluated
Output: tabla de exit criteria with status per stage hasta el stage claim.
Paso 3 — Identify actual current stage
ST-3: Si stage claim > actual state evidenced, flag discrepancy:
- "Claim: Traction. Evidence sugiere: MVP (5 exit criteria de Traction no met). Recomendación: mark actual stage as MVP, track Traction advancement as milestones."
Generar current-stage.md con:
- Actual stage (evidence-based)
- Claim stage (if different)
- Confidence level: high / medium / low
- Next stage transition criteria
Paso 4 — Milestones log
ST-4: Generar milestones.md:
- Past milestones (con dates)
- Current stage milestones (completed + pending)
- Next stage unlock milestones
- Stretch goals beyond next stage
Paso 5 — Blockers log
ST-5: Generar blockers.md:
- Active blockers (severity: low/medium/high/critical)
- Owner per blocker
- Expected unblock date
- Escalation path if blocker persists
Paso 6 — Dojo Score compute
ST-6: Por los 5 axes, score 0-20 con evidence:
- Pull data from existing artifacts (interviews count, revenue metrics, team size, etc.)
- Si missing data, mark as "assumed" o "estimated" (explicit flag)
- Total score 0-100
Generar dojo-score.md con scoring breakdown + recommendations por axis.
Paso 7 — History tracking
ST-7: Si hay prior stage-tracker/ runs, compare current vs last:
- Stage transitions (when + rationale)
- Dojo Score delta per axis
- New blockers opened / closed
- Milestones hit / missed
Generar history/YYYY-MM-DD-stage-transition.md per transition event.
Output template — current-stage.md
# Current Stage — [Startup Name]
**Assessment date**: YYYY-MM-DD
**Dojo Score**: XX/100 (see `dojo-score.md`)
---
## Actual stage
**Stage**: [Ideation / Formation / MVP / Traction / Funded / Scaling]
**Confidence**: [High / Medium / Low]
**Evidence**:
- [Citation from startup-profile.md or artifacts]
- [Citation]
---
## Claim vs actual
**Founder claim**: [Stage claimed]
**Evidence-based actual**: [Stage evidenced]
**Discrepancy explanation**: [if different, why]
---
## Exit criteria for NEXT stage ([Next Stage Name])
| Criterion | Status | Evidence / Gap |
|---|---|---|
| [C1] | ✓ / 🟡 / 🔴 | [evidence or what's missing] |
| [C2] | | |
| ... | | |
**Progress**: X / Y criteria met ({%} complete)
---
## Critical path to next stage
1. [Top priority blocker to resolve]
2. [Second priority milestone to hit]
3. [Third]
**Estimated transition timeline**: [honest estimate based on velocity]
---
## Recent progress (last 30 days)
- [Milestone hit 1]
- [Milestone hit 2]
- [Key learning]
## Stale risks (things not moving in 30 days)
- [Stuck item 1]
- [Stuck item 2]
Integración con DojoOS (via dojoos-api-consumer agent)
Disponible desde v0.5.0 — este skill puede invocar al agent dojoos-api-consumer con las operaciones sync_stage (POST current-stage + dojo-score al tracker), list_milestones (pull milestones existentes del founder's workspace), y get_user_courses (esta ÚLTIMA sí está LIVE en el spec hoy — getUserCourses / /user-courses). Course progress del user puede usarse como evidencia automática para "track record" en Formation / MVP axis. sync_stage y list_milestones retornan SPEC_GAP hoy — el skill continúa standalone con output markdown local. Cuando los endpoints launchpad lancen, el sync será bidireccional sin cambios en este skill — el schema de output ya está DojoOS-compat por diseño.
Integración con otras skills
startup-intake: source del startup-profile.md + stage claim initial
- Todos los otros skills de launchpad-toolkit: evidence para exit criteria
cofounder-matching → Formation Axis
cap-table-builder → Formation Axis
founder-documents → Formation Axis
investor-matching + demo-day-prep → Funded Axis
feature-to-spike: SPIKE si detectás stage criterion gap o methodology improvement for DojoOS productization
business-model-toolkit: Ideation stage evidence via customer-interview-system + solution-design
Principios clave
- Evidence over claim: founder claim sin evidence artifact = low confidence
- Exit criteria son cumulative: no skippear stages para acelerar
- Regression is acceptable: stage puede move backward (ej. pivot = back to Ideation)
- Assessment quarterly minimum: re-run cada 3 meses durante active phase; mensual durante transitions
- Blockers > progress: 1 critical blocker puede invalidar 5 milestones won
- Dojo Score directional, not absolute: usar para self-evaluation, not external benchmarking
Anti-patterns
- Self-promoting stage claim sin exit criteria met ("somos Series A-ready" sin $1M ARR)
- Ignorar regression (si pivot happened, mark actual stage honestly)
- Confundir activity con progress (10 interviews done pero ninguna informativa = no progress)
- Skip Formation para ir rápido a MVP (legal + cap table issues después = costo mayor)
- Dojo Score manipulation (scoring self-favorably destroys honesty signal)
- No update blockers (blockers pudren silenciosamente — require active surfacing)
Recursos