본문으로 건너뛰기
cccskills
무료GitHub에 공개

business-plan-skill

Use when creating, adapting, or filling business-plan materials (商业计划书、BP、路演材料), pitch deck content, incubator applications (孵化器申请、创业大赛、园区申请), project introductions, founder/team sections, market and competitor analysis, business models, financial projections (财务预测、融资计划), or official application forms for a startup or new venture. This skill provides a reusable structure and placeholder-based workflow rather than project-specific facts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(21)

  • SKILL.md6.3 KB
  • .github/ISSUE_TEMPLATE/config.yml412 B
  • .github/ISSUE_TEMPLATE/new-scenario.md1.6 KB
  • .github/ISSUE_TEMPLATE/output-problem.md1.6 KB
  • .github/PULL_REQUEST_TEMPLATE.md2.4 KB
  • .github/workflows/ci.yml4.3 KB
  • .gitignore35 B
  • agents/openai.yaml290 B
  • CHANGELOG.md4.9 KB
  • CODE_OF_CONDUCT.md5.6 KB
  • CONTRIBUTING.md4.5 KB
  • examples/bp-outline.md6.2 KB
  • examples/incubator-application-summary.md1.4 KB
  • examples/pitch-deck-outline.md6.8 KB
  • examples/README.md1.3 KB
  • LICENSE1.1 KB
  • README.md11.2 KB
  • references/application-copy.md4.2 KB
  • references/business-plan-core.md16.1 KB
  • references/founder-and-advantage.md4.2 KB
  • SECURITY.md2.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Business Plan Template

Use this skill when the user asks to create, update, polish, adapt, or fill materials for a startup, business project, incubator application, or pitch process.

Scope

This skill supports:

  • 商业计划书、执行摘要、可行性报告
  • 路演 PPT 内容、页面标题、项目亮点
  • 调用 codex-ppt 将商业计划书转化为高颜值视觉版路演材料
  • 园区、孵化器、创业社区、政府项目申请材料
  • 企业(团队)介绍、核心成员简介、项目内容摘要
  • 市场背景、目标客户、竞品分析、产品定位、商业模式、竞争优势
  • 财务预测、融资计划、里程碑、资源需求
  • Word / Excel / PPT 申请模板的内容填充

Privacy And Accuracy Rules

  • Do not invent names, IDs, phone numbers, emails, addresses, company registration numbers, legal entities, awards, patents, revenue, funding, or customer names.
  • If a field requires unknown personal, legal, financial, or registration information, write 待补充 or ask the user for it.
  • For public or GitHub-ready outputs, remove private facts and replace them with placeholders.
  • For official forms, preserve template structure and fill only relevant fields.
  • For project summaries in official materials, prefer objective third-person wording and avoid 我 / 我们 unless the field asks for a personal statement.
  • When using numbers, clearly distinguish actual data, estimates, assumptions, and placeholders.

What To Read

Load only the reference needed for the task:

  • Overall business-plan structure, positioning, customer pain, market, product, roadmap, and finance assumptions: read references/business-plan-core.md.
  • Founder/team profile and competitive-advantage patterns: read references/founder-and-advantage.md.
  • Short application copy, official-form fields, and materials checklist wording: read references/application-copy.md.

For financial projections or funding plans (财务预测、融资计划), start from the Key Assumptions table in references/business-plan-core.md, derive revenue from it, and run the Financial Self-Check before delivering.

Default Workflow

  1. Identify the target audience: investor, incubator reviewer, government park, partner, customer, or internal team.

  2. Clarify the venture type, target customers, key pain point, product/service, business model, and any known metrics.

  3. If facts are missing, use placeholders rather than inventing.

  4. Structure content around:

    • pain point
    • target customer
    • solution
    • product workflow
    • market opportunity
    • competition and differentiation
    • team capability
    • business model
    • roadmap
    • financial plan
    • funding/resource request

    For AI products, also include a validation-evidence section (user interviews + small Meta ad tests) using Validation Evidence / 想法验证 in references/business-plan-core.md; if no validation has been done yet, say so honestly instead of inventing traction.

  5. Adapt tone and length to the artifact:

    • application form: concise, objective, policy-friendly
    • pitch deck: sharp claims, visual page logic, investor-friendly
    • business plan: structured, detailed, evidence-oriented
    • short text box: copy-ready and within requested character limits

Pitch Deck Visual Workflow

When the user asks for a good-looking PPT, visual pitch deck, investor deck, roadshow deck, or presentation based on the business plan, use codex-ppt when available.

Note: codex-ppt is a third-party skill by @ningzimu. Installation: https://github.com/ningzimu/codex-ppt-skill

Recommended sequence:

  1. First use this business-plan skill to lock the deck narrative:
    • cover and one-line positioning
    • market background and pain point
    • target customer and use case
    • product workflow / demo logic
    • business model
    • market size
    • competition and differentiation
    • founder/team capability
    • financial forecast
    • roadmap and funding/resource request
  2. Compress each slide into one main claim, 2-4 support points, and a suggested visual form.
  3. Call codex-ppt to generate a polished 16:9 visual deck from the approved outline.
  4. After generation, review whether the deck covers:
    • team capability
    • business model
    • competitive advantage
    • market opportunity
    • financial data
  5. If the target is an incubator or government park, make the visuals credible, concise, and application-friendly rather than overly marketing-like.

Suggested user-facing prompt:

调用商业计划书 skill 先整理路演逻辑,再调用 codex-ppt 输出一份高颜值 16:9 商业计划书 PPT,目标读者是 [投资人/园区评委/合作伙伴],重点说服他们相信 [项目名称] 的市场机会、团队能力、商业模式和落地路径。

Generic Positioning Template

Use this as a starting point, then replace placeholders:

[Project Name] is a [product/service category] for [target customer], helping them solve [specific high-pain problem] through [core technology/workflow], so they can achieve [measurable business outcome].

Chinese version:

[项目名称] 是面向 [目标客户] 的 [产品/服务类型],通过 [核心技术/工作流] 解决 [具体高痛点问题],帮助客户实现 [可衡量业务结果]。

Deliverable Behavior

  • If creating/editing DOCX, XLSX, or PPTX, use relevant document, spreadsheet, presentation, or deck-generation skills when available.
  • If the user asks for a visually polished deck, explicitly use codex-ppt when available instead of only writing slide text.
  • For official application files, list which fields remain 待补充.
  • For public templates, remove project-specific facts before finalizing.
  • For short requested copy, provide copy-ready text rather than a long explanation.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

이 스킬의 문제 신고