jakeschincariol/founder-skill

founder-board

Your board of directors.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jakeschincariol/founder-skill --skill founder-board

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

founder-board

The first meeting. Before anyone builds a website or signs a lease, three board members tear the idea apart, each from a different angle, and vote.

What the user typed after /founder-board: $ARGUMENTS. If that is blank, take the idea from the conversation.

The rule about the three names

The lenses are summaries of published frameworks, nothing more. The board members are not those people, never speak as them, never quote them, never claim they would endorse anything. Write "the Offers lens", never "Alex Hormozi says". If the user asks what one of them really thinks, say you can only apply their public frameworks.

Step 0: the idea file

Everything in the founder pack reads founder/idea.md in the user's project. If it does not exist, write it now from the conversation:

markdown
# <business name, or a working name>

- What it is: one sentence.
- Who it is for: the target customer, as specific as the user can make it.
- What it sells, at what price: the core product and its price.
- Where and how: city or online, how customers find it, how it is delivered.
- Budget and constraints: money, time, skills, anything already decided.

If the name, the customer, the product or the price is missing, ask for those (at most three questions in one message), then write the file. Do not invent a budget, a market size or a competitor.

Step 1: brief the board

Write founder/board/brief.md: the idea file plus anything else the user said that a stranger would need. Sub-agents cannot see this conversation, so the brief must stand on its own. Do not add your own opinion of the idea to it.

Step 2: convene

Launch three sub-agents in ONE message (Agent tool, subagent_type: general-purpose, one per member), each told: Read founder/board/brief.md and founder-board's lenses.md (path below), apply ONLY the <lens> lens, and write your memo to founder/board/<lens>.md. The lens file is lenses.md in this skill's folder (${CLAUDE_SKILL_DIR}/lenses.md; if that path is not expanded, use the base directory Claude Code printed for this skill).

Each memo, in this shape:

markdown
# <Lens> lens
Score: <1-10> | Vote: FUND / FUND IF / PASS
## What is strong
## What would kill it (the top 3, most dangerous first)
## The questions I would ask the founder
## If FUND IF: the conditions

Step 3: the chair's summary

Read the three memos (they are short) and write founder/board.md:

  1. The vote, e.g. "2 fund if, 1 pass", and the average score.
  2. The risks more than one member raised: these go first.
  3. Every condition, merged, as a checklist the rest of the pack can tick off

(the CFO, the consumer panel and pricing will test most of them).

  1. One paragraph: the strongest version of this business the board can see.

It may differ from what the user pitched; say so plainly.

Keep the members' disagreements. A board that agrees on everything was not doing its job.

Rules

  • Score the business, not the founder.
  • No made-up facts. If a lens needs a number nobody has yet (market size, cost of

acquiring a customer), name it as an open question and say which skill answers it (/founder-competitors, /founder-consumer, /founder-cfo).

  • A PASS is a result, not a failure. Say it plainly.

Output

founder/idea.md, founder/board/ (brief and three memos), founder/board.md. Then say the vote in one line and suggest the next step: /founder-competitors to see who is already there, or /founder-consumer to put it in front of 100 simulated buyers.

Where the pack goes next

board -> competitors -> consumer -> pricing -> offer -> cfo -> marketing -> brand -> ops -> launch -> plan

Every skill can also run on its own; each reads whatever is already in founder/.

같은 저장소의 Skills

더 많은 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시간 설치 수
2
GitHub Stars
4.5천
업데이트
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

1시간 설치 수
2
GitHub Stars
4.5천
업데이트
10월 7일
jakeschincariol
커뮤니티

founder-competitors

Maps every competitor and the gap they leave. Finds the direct competitors, indirect ones and the substitutes a buyer would use instead, from public sources only, and records what each sells, at what price, how they position themselves and what their customers complain about in public reviews, every fact with a link. Ends with a positioning map and the gap the new business can own. Use when the user says "who are my competitors", "is this market crowded", "what else is out there", "competitor an

1시간 설치 수
2
GitHub Stars
4.5천
업데이트
10월 7일
jakeschincariol
커뮤니티

founder-consumer

The consumer panel. Spins up a swarm of buyer sub-agents (default 100, --quick for 20) trained on the user's target customer, each with a different income, age, buying behaviour and objection, shows every one the same pitch, and runs the business through 100 buyer scenarios to see who buys, who doesn't, and why. Tallies the answers into buy rates by segment, the reasons people pass in their own words, what would flip a no, and price answers for founder-pricing. Use when the user says "would peop

1시간 설치 수
2
GitHub Stars
4.5천
업데이트
10월 7일