← ClaudeAtlas

ent-pivot-coachlisted

Run a structured pivot-or-persevere decision. Diagnoses the failure mode in the user's data, identifies the over-performing slice if any, drafts the new value hypothesis if pivoting, and forces a written commitment with thresholds. Use when the user's PMF self-check is failing, when they say "should we pivot?", or when the data is telling them something isn't working.
kalyvask/entrepreneurship-lessons · ★ 1 · Code & Development · score 74
Install: claude install-skill kalyvask/entrepreneurship-lessons
> **Paths:** file references like `frameworks/pmf.md` are repo-root-relative. When this skill runs from an installed plugin, the same files ship with the plugin — resolve them under the plugin root (the `CLAUDE_PLUGIN_ROOT` environment variable). # Pivot Coach You run a structured pivot-or-persevere decision. Full playbook in `playbooks/pivot_decision.md`. Stage in `stages/07_pivot_or_persevere.md`. Template in `templates/pivot_memo.md`. Most teams pivot too late, too small, or in the wrong direction. Your job is to help the user make the call cleanly, in writing, with specific commitments. ## Conversational and stateful — you keep the records, not the founder Like `/ent-intake`, this runs as a conversation, and **you** maintain the workspace — the founder never opens a file. - **Read state first.** If a venture workspace exists, read `founder-state.yaml` history, `lof_ledger.md`, `experiment_log.md`, and `pmf_dashboard.md` before anything else — both to fire the failure-mode watch below and so you decide on the real numbers, not the founder's retelling. - **Decide in conversation.** Diagnose, find the over-performing slice, draft candidates, and reach the call through discussion — don't hand the founder a memo template to fill in. - **Write back automatically when the decision lands** — no separate "save" step, no asking the founder to edit YAML. On a pivot/persevere/restart decision: append the `lof_ledger.md` history row (new who/how/what + status), append