focus-planner
openbooklet.com/s/focus-planneropenbooklet.com/s/[email protected]GET /api/v1/skills/focus-plannerLocks the one focus that matters most for the next working cycle. Use when priorities are scattered or after a weekly review. Produces focus-plan.md.
The ritual you run again and again â all the way to PMF and beyond.
Diagnoses why paid acquisition efficiency is weak before more budget gets spent. Use when CAC is rising, conversion is weak, or paid traffic quality is unclear. Produces cac-diagnosis.md.
Diagnoses why users are leaving by translating timing, behavior, and feedback into one root-cause call. Use when churn is rising or retention feels mysterious. Produces churn-diagnosis.md.
Defines the first customer with enough specificity to guide product and GTM choices. Use when the founder is still speaking in broad market categories. Produces customer-profile.md.
Establishes the visual tone, typography, color, and feel of your product before a line of UI is written. Use when you're about to build your UI and need a clear aesthetic direction, or when your product looks generic and you can't articulate why. Produces a design-brief.md with specific font, color, and visual direction choices your agent can implement immediately.
Turns product and design intent into a build-ready implementation brief for UI and interaction work. Use when a founder knows what the product should feel like but the handoff to build is fuzzy. Produces design-build-brief.md.
Turns a bottleneck or hypothesis into a concrete experiment for the next cycle. Use when the founder knows what to learn next but not how to structure the test. Produces experiment-plan.md.
Prioritizes what to build in what order, given your MVP brief and tech stack. Use when you have a feature list and don't know where to start, or when you're building in the wrong order and feeling stuck. Produces a build-sequence.md with a sequenced backlog and a clear "build this first" decision.
Decides who or what to hire first by tying capacity pressure to the company's real bottleneck. Use when founder time is the limiting factor and a concrete hiring brief is needed. Produces human-hire-brief.md or agent-hire-brief.md.
Acts as a brutally honest founder collaborator by reading company state, artifacts, and recent history before naming the hard truth, the biggest bottleneck, and the next move. Use at the start of any session, when priorities feel unclear, when the founder wants to be challenged, or before any serious build decision. Produces truth-memo.md, recommended-next-step.md, and an updated founder-context.md.
Designs the strongest self-reinforcing growth loop for the product. Use when the founder wants compounding growth instead of one-off acquisition tactics. Produces growth-loop.md.
Recommends the specific third-party services to use for auth, payments, email, storage, and other common needs. Use when building a feature that requires an external service and you're unsure which tool to use or how to set it up. Produces an integrations-plan.md with specific tool choices and the order to add them.
Builds a concrete launch plan across owned, rented, and borrowed channels. Use when the product and message are defined and the founder needs a realistic launch motion. Produces launch-plan.md.
Builds the core message architecture that ties positioning, sales, SEO/GEO, and launch copy together. Use when the founder has positioning but needs a repeatable message system. Produces messaging-architecture.md.
Defines exactly what is in and out of scope for the MVP. Use when the product idea is clear but scope keeps expanding. Produces mvp-brief.md.
Defines the one metric that best captures delivered value and future company health. Use when the founder is tracking too many metrics or lacks one leading signal. Produces north-star.md.
Diagnoses pipeline weakness and identifies the highest-leverage fix in founder-led sales. Use when demos are happening but closes are weak. Produces pipeline-review.md.
Reads whether traction is real by judging retention, word of mouth, engagement, and revenue signals. Use when the founder needs an honest PMF read instead of vanity metrics. Produces pmf-assessment.md.
Crafts the clearest positioning for the product and chooses the strongest framing direction. Use when people do not quickly understand what the product is or why it matters. Produces positioning.md.
Reviews what changed after shipping and identifies the highest-leverage follow-up move. Use right after release or after a meaningful product change lands. Produces post-ship-review.md.
Auto-indexed from gvkhosla/founder-skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.