jakeschincariol/founder-skill

founder-offer

Builds an offer too good to refuse.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jakeschincariol/founder-skill --skill founder-offer

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

founder-offer

Most businesses sell a product. Good ones sell an offer: the product plus everything that makes buying it an easy yes. This skill builds that, using the Offers lens in ../founder-board/lenses.md as the method (a summary of the framework in Alex Hormozi's $100M Offers; never present it as his words).

Step 1: read what is already known

  • founder/idea.md and founder/pitch.md: what is sold today.
  • founder/panel/results.md: why buyers pass, in their words. This is the raw

material: every top objection should be answered by something in the offer.

  • founder/numbers.json: what each extra costs, so the stack stays profitable.
  • founder/board.md: the board's conditions.

Step 2: the problem list

Write every obstacle between the buyer and the result they want, in the buyer's words: before buying (doubt, price, effort to switch), during (waiting, learning, inconvenience), after (does it last, what if it fails). Aim for 15 to 30. Pull from the panel objections and the competitor complaints first.

Step 3: solutions, trimmed and stacked

Turn each problem into a solution (a feature, a service, a guarantee, a format). Score each on value to the buyer (1 to 5) and cost to deliver (1 to 5, from the CFO's numbers). Keep high value, low cost. Stack what is left into:

  • The core: the thing itself, described by the outcome, not the ingredients.
  • Bonuses: two or three, each killing one specific objection.
  • The guarantee: what happens if it does not deliver. Model what it costs at a

realistic claim rate with the CFO's tool before promising it.

  • Urgency and scarcity: only if they are true (a launch week, a limited first

batch). Never fake a countdown or a "only 3 left".

  • The name: a clear, specific name for the offer, not the company.

Step 4: score it

On the value equation, before and after, 1 to 10 each: dream outcome, perceived likelihood of getting it, time to the result, effort and sacrifice. Say which element of the stack moves which score.

Step 5: re-test it

Write the new offer into founder/pitch.md (keep the old one as founder/pitch-v1.md) and run /founder-consumer --quick with the same seed. Report the buy rate before and after and which objections dropped. If nothing moved, say so: the problem may be the market or the price, not the offer.

Rules

  • Every promise must be deliverable and affordable; check costs with the CFO.
  • No fake reviews, testimonials, scarcity, discounts or "as seen on".
  • Follow the advertising and consumer-protection rules of the user's market for

guarantees and claims (health claims especially). Not legal advice.

Output

founder/offer.md (problem list, the stack, costs, the value-equation scores, the re-test result) and the updated founder/pitch.md. Next: /founder-cfo to re-run the numbers with the stack, then /founder-marketing.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
jakeschincariol
コミュニティ

founder-brand

Your brand designer. Names the business (with the trademark, domain and handle checks to run before falling in love with a name), writes the voice, a one-line promise and a tagline, and briefs the look: colours, type, logo and the first things a customer sees, so they match the positioning the marketing director chose. Use when the user says "name my business", "brand this", "logo", "brand identity", "what should it look like", "tagline", or "brand voice".

導入数
1
GitHub Stars
1647
更新日
10月7日
jakeschincariol
コミュニティ

founder-cfo

Your CFO. Builds the unit economics of a business before money is spent: what one unit earns after its direct costs, the real profit margin at the planned volume, the break-even point in units a day, year 1 month by month, the cash needed before it pays for itself, how long the startup spend takes to earn back, and what happens if the price drops, sales come in low or costs rise. Every number traces to an input the user can check. Use when the user says "find the profit margins", "do the numbers

導入数
2
GitHub Stars
1146
更新日
10月7日
jakeschincariol
コミュニティ

founder-launch

Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run sheet, and the first 30 days of what to measure and what to change. Use when the user says "how do I launch", "launch plan", "when can I open", "launch checklist", "go live", or "soft open".

導入数
2
GitHub Stars
1146
更新日
10月7日
jakeschincariol
コミュニティ

founder-marketing

Your marketing director. Turns the buyer panel and the competitor map into positioning, the channels the target customer actually uses, a 30-day launch campaign with dated posts and ads, the first ten hooks, a budget split and the numbers to watch. Every message answers an objection real or simulated buyers raised. Use when the user says "how do I market this", "marketing plan", "launch campaign", "how do I get customers", "where do I advertise", "write my ads", or "positioning".

導入数
2
GitHub Stars
1146
更新日
10月7日