forced-pivot-15-day
Skill1 starsChanged 29 days agoBSD-3-ClauseView on GitHub
Sequences a 1 to 3 week pivot forced by an external constraint so it ships before the launch is killed. Use when an App Store guideline change, RevenueCat policy, regulatory deadline or paywall rejection forces a pivot. Based on Emil Nilimaa (Minglify), whose 15-day rewrite followed Apple guideline 1.2.
In this repository52 other files it gives its agents.
- academic-research-assistantSkill
- answer-sheetSkill
- app-graphicsSkill
- app-landing-pageSkill
- app-screenshotsSkill
- break-uiSkill
- consumer-app-from-behaviorSkill
- cross-language-safetySkill
- dart-tool-scriptsSkill
- decision-sweepSkill
- engineering-diarySkill
- figma-review-loopSkill
- flutter-app-size-auditSkill
- flutter-async-at-the-edgeSkill
- flutter-async-cubit-safetySkill
- flutter-bloc-clean-architectureSkill
- flutter-clean-architecture-tddSkill
- flutter-cubit-smart-cachingSkill
- flutter-error-logging-conventionsSkill
- flutter-observability-instrumentationSkill
- flutter-paywall-and-review-timingSkill
- flutter-precommit-cleanupSkill
- flutter-router-decisionSkill
- flutter-runtime-safetySkill
- flutter-shorebird-otaSkill
- flutter-stream-architectureSkill
- flutter-strict-analysisSkill
- flutter-web-first-paintSkill
- gplay-consoleSkill
- ios-distribution-feature-flagsSkill
- launch-readinessSkill
- launch-watchSkill
- locale-expert-reviewSkill
- market-pulseSkill
- mobile-ui-referenceSkill
- moscow-prioritizationSkill
- orchestrate-agentic-engineeringSkill
- parallel-agent-inboxSkill
- paywall-conversion-flowSkill
- paywall-transparencySkill
- proactive-crash-repair-loopSkill
- promise-auditSkill
- pr-preview-shippingSkill
- ship-first-dollar-appSkill
- slim-ios-simulator-fleetSkill
- spec-sql-harnessSkill
- store-launch-mastermindSkill
- sync-contextSkill
- task-blitzSkill
- techdebtSkill
- vendor-decisionSkill
- web-interface-reviewSkill
The file
Files
Forced Pivot — 15-Day Sprint
Trigger
External event with hard deadline that breaks current monetization or distribution.
Sequence
| Day | Phase | Output |
| 0 | Triage | Single doc: what broke, what changes, what stays |
| 1 | Cut surface | Remove offending feature behind a flag |
| 2-3 | Rebuild monetization | New paywall + ASO drafted |
| 4-7 | Onboarding rewrite | Replacement feature for top-of-funnel |
| 8-10 | A/B variants | 2 variants live; promo/screenshots updated |
| 11-13 | Submit + iterate | Submit, fix rejections same-day |
| 14-15 | Buffer | Reserved for unknown rejection |
Heuristics
- Patch the wound; rewrite later.
- Monetization first, polish last.
- One A/B test at a time during a pivot.
- Cap overtime. A pivot sprint is not a reason to burn out.
When NOT to use
- Speculative pivot. Use only with external clock.
- Pre-traction products.
Source
- urn:li:activity:7437905259609624576 (Emil Nilimaa)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

