bmod-founder

어떤 스킬인가요?

Required bmod metadata. Never invoke this skill.

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

[bmod]
code = "founder"
version = "6.13.0-next"
update_source = "github:bmad-code-org/BMAD-METHOD/skills"
skills = []
required_skills = [
  { skill = "bmad", version = "6.13.0", source = "github:bmad-code-org/BMAD-METHOD/skills" },
  { skill = "bmad-facilitate", version = "6.13.0", source = "github:bmad-code-org/BMAD-METHOD/skills" },
]
pre_install_message = ""
post_install_message = """Founder is installed.
Ask bmad-facilitate for a proposal (a grant, a bid, a funding request) or a pitch deck."""

Rate each strong, adequate, thin or broken, judged against the reader's criteria and the stakes:

1. Clear ask: what is wanted, how much, by when, stated up front.
2. Reader first: every criterion the reader named is answered where they will look.
3. Evidenced: claims carry data or sources; no invented figures; numbers match the plan.
4. Honest costs and risks: full cost and what could fail, each with how it is handled.
5. One pass: the case comes through from the opening and headings; no padding.

Then check the template's Done when.

Write review-rubric.md: a two-sentence verdict, the three fixes that matter most, then findings by dimension with severity, location and fix.

---
title: ""
template: pitch-deck
version: 1.0.0
description: "A talk or pitch with a story and slides, given by a presenter."
not_for: "An ask read without a presenter (`proposal`)."
rubric: rubric-proposal.md
status: draft
created: ""
updated: ""
view: slides
---

<!-- purpose: A story in slides that moves an audience to one decision: invest, adopt, change how they work. -->

<!-- stance: A story coach. Find the one idea first, then cut any slide that does not move the audience toward it. -->

<!-- inputs: The audience, the time slot and what they should do afterwards; the one idea; for a pitch, traction, market, team and the ask; for a talk, the speaker's experience and examples. Only the user knows these. -->

<!-- writing: Each `##` section after the table of contents is one slide unless its comment says it repeats: a bold headline stating its point as a sentence, a few short lines or one diagram, then speaker notes in a blockquote. One idea per slide. The headline is the slide's title on screen; section names never show. The notes fit the time slot. -->

<!-- done when: The headlines read in order tell the whole story, the speaker notes fill the time slot, and the last slide says what the audience should do. -->

# {title}
<!-- required. The title slide: speaker and the one idea in a sentence. -->

## Table of Contents

## Hook
<!-- include when: a talk. A question, story or fact that puts the audience in the problem. -->

## Problem
<!-- required. Whose pain, how it is handled today, and where that falls short. -->

## Why now
<!-- include when: a pitch, or timing is part of the argument. What changed to make it possible or urgent. -->

## Solution
<!-- required. The insight and what it does differently; for a talk, the one idea. -->

## How it works
<!-- optional. A demo or the mechanism in one picture. diagram: flowchart -->

## Point
<!-- include when: a talk. Repeats, one slide per supporting point, at most three, each with a story from the speaker's experience; what was tried and failed is a point too. -->

## Traction
<!-- include when: a pitch. Evidence it works: users, revenue, growth, pilots. -->

## Market and model
<!-- include when: a pitch. Who buys, how many sized from the bottom up, and how it makes money. -->

## Competition
<!-- include when: a pitch. The alternatives and why this wins. diagram: quadrant -->

## Team
<!-- include when: a pitch. Why these people win. -->

## Ask
<!-- required. For a pitch, the amount and the milestones it reaches; for a talk, the one thing to do or remember. -->

---
title: ""
template: proposal
version: 1.0.0
description: "Asking someone for money, time or approval, such as a grant or bid."
not_for: "A decision already made (`decision-record`); a talk with slides (`pitch-deck`)."
rubric: rubric-proposal.md
status: draft
created: ""
updated: ""
---

<!-- purpose: Win a yes from someone who controls money, time or approval. -->

<!-- stance: The reader decides, so before drafting ask for the call, RFP or guidelines; their scoring criteria, required headings, limits and order replace this template's. Press for a sized ask and evidence behind each claim. -->

<!-- inputs: Who decides and what they weigh; the ask and its deadline; evidence of need; the plan, team and budget. Only the user knows the real budget and what in it is negotiable, and the history with this reader. -->

<!-- writing:
  - The summary's first sentence names the ask, its size and its deadline; write it last.
  - Every figure traces to the budget.
-->

<!-- done when: The ask is explicit and sized, every criterion the reader stated is answered where a reviewer will look, and budget, plan and timeline agree. -->

# {title}

## Table of Contents

## Summary
<!-- required. The ask, what it achieves, for whom, by when. -->

## Need
<!-- required. The problem or opportunity, who has it, the evidence, why now. -->

## Goals and outcomes
<!-- required. What changes if the answer is yes, stated so it can be measured. -->

## Approach
<!-- required. The work plan and how it reaches the goals. diagram: gantt -->

## Alternatives
<!-- include when: an internal request. The options considered, including doing nothing, and why this one. -->

## Team and track record
<!-- include when: the reader must trust who does the work. Who, why they can, what earlier work produced. -->

## Evaluation
<!-- include when: the reader expects reports on results. Measures and when they are reported. -->

## Budget
<!-- required. Cost by line with justification, total, other funding; or the people and hours asked for. When a figure comes back round or unexplained, ask how it was built. -->

## Risks
<!-- required. What could stop the work and how it is handled. -->

## Sustainability
<!-- include when: the work must outlast the funding. How it continues. -->

## Deliverables and terms
<!-- include when: a bid to a client. What is delivered, when, at what price, and how acceptance works. -->

# Founder knowledge

This document covers the `founder` module: the business documents it adds, when to recommend each, and what to offer next.

## What the module is

Founder is for the business side of starting and running something: asking for money, time or approval, and pitching. It ships no skills of its own. Its templates run in `bmad-facilitate`, which coaches the user through each one, reviews the draft and polishes it.

## The templates

| id | Recommend when |
|---|---|
| `proposal` | Asking for money, time or approval: a grant, a bid, an internal request. The reader's own guidelines replace its headings. |
| `pitch-deck` | A talk or pitch that needs a story and slides, given by a presenter. It always renders as an HTML slide view unless the team turned views off. |

## Start here

- "Write a grant application", "help me with this bid", "I need a funding request" → `bmad-facilitate` with `proposal`. Ask for the funder's guidelines first; they set the headings.
- "Build me a pitch deck", "I'm giving a talk", "investor pitch" → `bmad-facilitate` with `pitch-deck`.
- Whether the idea is worth funding at all → `bmad-forge-idea` first. A business case for building a product → John (`bmad-agent-pm`), when Method is installed.

---
name: bmod-founder
description: Required bmod metadata. Never invoke this skill.
---
This folder is the Founder module's record, not something to run. Invoke the `bmad` skill with `setup founder`; it sets the module up if it never was, and otherwise reports its state. If there is no `bmad` skill, say so and offer `npx skills add bmad-code-org/BMAD-METHOD --skill bmad`.